[WooreeINFO] NXP LPCXpresso54608 with your ECOM-COMM example

Dear MicroEJ,

i have ported your ECOM-COMM example(http://developer.microej.com/4.1/ivy/artifacts/ej/api/ecom-comm/1.1.4/) into the Simple Background Application, an example in your user guide, and tried to run it on top of the NXP LPCXpresso54608 board(FMW-BLUE-OM13092-PQ9Y4-1.6.1) without a successful serial communication yet.

The debug window showed an exception as:

com.microej.wadapps.kf.abstractfeatureapplicationstorage INFO: Start MySandboxedApp
MyBackgroundCode: Hello Serial: comm:com9
Exception in thread “ej.wadapps.app.default” java.io.IOException: ECOM-COMM:E=3
at java.lang.System.@M:0x1004c348:0x1004c358@
at java.lang.Throwable.@M:0x10054e1c:0x10054e32@
at java.lang.Throwable.@M:0x10059274:0x10059297@
at java.lang.Exception.@M:0x1006ce9c:0x1006ceae@
at java.io.IOException.@M:0x10055d40:0x10055d52@
at ej.ecom.connection.comm.CommConnectionCreator.@M:0x1004e380:0x1004e5e0@
at ej.ecom.connection.comm.ConnectionFactory.@M:0x1005fc54:0x1005fc70@
at ej.ecom.io.Connector.@M:0x1005ae98:0x1005af60@
at ej.ecom.io.Connector.@M:0x1005b388:0x1005b3a4@
at appEntry.MyBackgroundCode.@F:3a8961576a010000d37548f1e20224d0b875cb968936fb41:0xa00878f0@@M:0xa00884a0:0xa00884b0@
at appEntry.MyBackgroundCode.@F:3a8961576a010000d37548f1e20224d0b875cb968936fb41:0xa00878f0@@M:0xa00885cc:0xa00885de@
at appEntry.MyBackgroundCode.@F:3a8961576a010000d37548f1e20224d0b875cb968936fb41:0xa00878f0@@M:0xa0088744:0xa008878e@
at Exception in thread “ej.wadapps.app.default” java/io/IOException: ECOM-COMM:E=3
at java/lang/System.@M:0x1004C348:0x1004C358@
at java/lang/Throwable.@M:0x10054E1C:0x10054E32@
at java/lang/Throwable.@M:0x10059274:0x10059297@
at java/lang/Exception.@M:0x1006CE9C:0x1006CEAE@
at java/io/IOException.@M:0x10055D40:0x10055D52@
at ej/ecom/connection/comm/CommConnectionCreator.@M:0x1004E380:0x1004E5E0@
at ej/ecom/connection/comm/ConnectionFactory.@M:0x1005FC54:0x1005FC70@
at ej/ecom/io/Connector.@M:0x1005AE98:0x1005AF60@
at ej/ecom/io/Connector.@M:0x1005B388:0x1005B3A4@
at appEntry/MyBackgroundCode.@F:3a8961576a010000d37548f1e20224d0b875cb968936fb41:0xA00878F0@@M:0xA00884A0:0xA00884B0@
at appEntry/MyBackgroundCode.@F:3a8961576a010000d37548f1e20224d0b875cb968936fb41:0xA00878F0@@M:0xA00885CC:0xA00885DE@
at appEntry/MyBackgroundCode.@F:3a8961576a010000d37548f1e20224d0b875cb968936fb41:0xA00878F0@@M:0xA0088744:0xA008878E@
at ej/wadapps/app/BackgroundServiceProxy.@F:c30134e26801000073783c876987b55b8e3aaa8e1d407fd1:0x10106110@@M:0x10109DE0:0x10109DED@
at com/microej/wadapps/management/util/BackgroundsManager.@F:c30134e26801000073783c876987b55b8e3aaa8e1d407fd1:0x10106110@@M:0x1010A244:0x1010A256@
at com/microej/wadapps/management/util/BackgroundsManager.@F:c30134e26801000073783c876987b55b8e3aaa8e1d407fd1:0x10106110@@M:0x1010A888:0x1010A8C6@
at ej/observable/Observable.@F:c30134e26801000073783c876987b55b8e3aaa8e1d407fd1:0x10106110@@M:0x1010BB08:0x1010BB38@
at com/microej/wadapps/management/util/BackgroundServicesListImpl.@F:c30134e26801000073783c876987b55b8e3aaa8e1d407fd1:0x10106110@@M:0x1010C2A4:0x1010C2D4@
at ej/wadapps/management/BackgroundServicesListProxy.@F:3a8961576a010000d37548f1e20224d0b875cb968936fb41:0xA00878F0@@M:0xA0088384:0xA0088392@
at MySandboxedApp/generated/MySandboxedAppActivator.@F:3a8961576a010000d37548f1e20224d0b875cb968936fb41:0xA00878F0@@M:0xA00887D0:0xA00887FE@
at ej/components/registry/impl/AbstractRegistry.@M:0x10061660:0x1006168C@
at ej/components/registry/util/BundleRegistryHelper.@M:0x10069BFC:0x10069C16@
at MySandboxedApp/generated/MySandboxedAppEntryPoint.@F:3a8961576a010000d37548f1e20224d0b875cb968936fb41:0xA00878F0@@M:0xA0088694:0xA00886BE@
at ej/kf/Kernel$2.@M:0x1003A598:0x1003A5D4@
at java/lang/Thread.@M:0x10071924:0x1007193C@
at java/lang/Thread.@M:0x1007186C:0x10071878@
at java/lang/Thread.@M:0x100718DC:0x100718E7@

In addition there was no use when i tried with a different serial port of ‘com0’ through ‘com9’.

Do you think i can test a serial(RS-232) communication with the java application, on top of this board and your firmware(FMW-BLUE-OM13092-PQ9Y4-1.6.1)?

These are additional findings of mine regarding to this.

When i tried with ‘P4’ on the board, the terminal showed the same outputs to J8(Debug Link).
When i tried with ‘J13/D1, J13/D0, J10/GND’ on the board, the terminal showed nothing.

Thanks much in advance for your feedback.

Regards
YH Kwon

Hello @kwonyh

As stated in the Device Developer Guide [1] the ECOM-COM error 3 is The connection description is invalid. The connection cannot be opened.. Could you provide the connection string you are using in the Connector.open() method?

Regards,
Gaëtan for MicroEJ

[1] https://developer.microej.com/packages/devdevguide-4.1-A/TLT-0784-MAN-DeviceDevGuide-1.1.0.pdf section 24.4.1

Dear Gaëtan,

i’d like to appreciate you for the quick feedback first of all and my comments are in the below.

The connection string must be in the same form to the one in the ECOM-COMM example, which is as:

/**
 * Comm connection string: used to open the comm connection
 */
private final String CONNECTION_STRING = "comm:com9"; // $NON-NLS-1$

Where i tried with com port changes from com0 through com9.

Just for your better information, please find the test code in the attachment(MyBackgroundCode.java).

Thanks
YH Kwon
MyBackgroundCode.jar (1.2 KB)

Hello @kwonyh,
unless I’m mistaken, the platform of the ‘FMW-BLUE-OM13092-PQ9Y4-1.6.1’ firmware does not provide any serial connection.
If you want use any board UARTs, you need to create your own platform by changing, for example, our reference implementation for OM13092.

Best regards,

Jerome S. for MicroEJ