OM15080-JN5189 Dongle Communication Problem

[Parth_911]

Hello,

I am currently working with OM15080-JN5189 USB dongle. I have tried to use the zigbee_coordinator_bm code from the wireless examples in MCUXpresso IDE but it is not even getting built, so then I tried to use the IEEE 802.15.4 protocol but in that code the data is not getting transmitted. My priority is to establish communication between the 2 OM15080-JN5189 dongles.

Can you please help me to resolve this problem? Any source for zigbee / IEEE comunication protocol which can help me solve this problem.

[mihai_ignat]

Hello.

Can you please give more details regarding what SDK version you are using and what tool are you using to flash the image to the board?

Thanks.

BR,

Mihai

[Parth_911]

I am using MCUXpresso IDE 24.12.148 on Linux Operating System, and using dk6prog for flashing the code and picocom for viewing debugging messages.

[mihai_ignat]

Thank you for the information.
I am also looking for the JN5189 SDK version, the package downloaded from MCUXpresso SDK builder website. It should be something like 2.6.x. Latest version is 2.6.16 released in November 2024, if I remember correctly. Can you please share your SDK version?
Thanks.
Mihai

[Parth_911]

Yes, the SDK version is SDK_2.6.16_JN5189. The download link is as follows:
https://mcuxpresso.nxp.com/download/c92a15504c3c619ff1accdba3c729d2b

[mihai_ignat]

Hello, @Parth_911 .

I had a quick look at the example from 2.6.16 JN5189 SDK. For reference, from the release notes, the recommended IDE is MCUXpresso 11.10.0, but I've checked also on v24.12 [Build 148] [2025-01-10] and I can build and flash the binary fine.

Because of limited availability of JN5189 USB dongle, I'm using a JN5189 on a DK6 v3 EVK, see attached image:

I've checked the schematic and I can confirm that the UART is routed on the same pins for the DK6 and for the USB (PIO8 and PIO9), so the binary is compatible. Attaching the used binary.

I've checked with dk6prog on Windows and I can paste the output:

C:\Users\user>dk6prog listdev

This is an experimental utility. Use with caution!

List of available devices:
DEVICE ID: 0, VID: N/A, PID: N/A, Serial number: b'DN038ZGD', Description: b'DK6 Carrier Board', Address: 67330069, Backend: Backend.FTD2xx

C:\Users\user>dk6prog -d 0 info

This is an experimental utility. Use with caution!

Chip ID: 0x88888888
ROM Version: 0x0
MAC Address: 82:76:A7:04:00:8D:15:00

Detected DEVICE: JN5189

  Memory   Memory ID   Base Address   Length    Sector Size   Memory Type   Access
----------------------------------------------------------------------------------------------
  FLASH    0           0x0            0x9de00   0x200         FLASH         All is available
  PSECT    1           0x0            0x1e0     0x10          FLASH         All is available
  pFLASH   2           0x0            0x1e0     0x10          FLASH         All is available
  Config   3           0x9fc00        0x200     0x200         FLASH         All is available
  EFUSE    4           0x0            0x80      0x2           EFUSE (OTP)   Write Enabled
  ROM      5           0x3000000      0x20000   0x1           ROM           Write Enabled
  RAM0     6           0x4000000      0x16000   0x1           RAM           Write Enabled
  RAM1     7           0x4020000      0x10000   0x1           RAM           Write Enabled

C:\Users\user>
C:\Users\user>dk6prog -d 0 erase 0 0x9de00

This is an experimental utility. Use with caution!

Erasing memory  [####################################]  100%

C:\Users\user>dk6prog -d 0 write 0 C:\Users\user\Documents\MCUXpressoIDE_24.12.148\workspace\jn5189dk6_zigbee_coordinator_bm\Debug\jn5189dk6_zigbee_coordinator_bm.bin

This is an experimental utility. Use with caution!

Writing memory  [####################################]  100%
Written 197152 bytes to memory ID 0 at address 0x0

C:\Users\user>

After this procedure, I can open a serial terminal like MobaXterm and I can see the output:

Unkown serial command
Commands Supported
******************
toggle - sends on\off toggle command
steer  - opens permit join window
form   - forms the network
find   - makes a binding on a target which is identifying
factory reset  - clears all data and starts afresh
soft reset  - retains network configuration but resets the node
Unkown serial command
Commands Supported
******************
toggle - sends on\off toggle command
steer  - opens permit join window
form   - forms the network
find   - makes a binding on a target which is identifying
factory reset  - clears all data and starts afresh
soft reset  - retains network configuration but resets the node
Unkown serial command
Commands Supported
******************
toggle - sends on\off toggle command
steer  - opens permit join window
form   - forms the network
find   - makes a binding on a target which is identifying
factory reset  - clears all data and starts afresh
soft reset  - retains network configuration but resets the node

Can you please check on your side with the commands and the binary I provided?

BR,

Mihai

[Parth_911]

hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP); // ToDo - Clarify apduZCL is defined in application scope; how to link the name in BDB (independent of application)

The above code is in <project_name>/zigbee/BDB/Source/NwkSteering/bdb_ns.c

How to solve this , it seems like that error occurs here when we try to build the example code without any modifications.

[mihai_ignat · Accepted solution]

Hello.

I did import the project without any modifications and I haven't seen this build issue. Can you please provide the full build log? And please double check if you have any modifications on your side.

Also, I know from experience that Zigbee MCUXpresso builds require some python modules to be installed like lxml, so you need to install in terminal/cmd with "pip install lxml". The full build log should point out something like "no module for lxml found".

BR,

Mihai

[Parth_911]

hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP); // ToDo - Clarify apduZCL is defined in application scope; how to link the name in BDB (independent of application)

This is the line in bdb_ns.c file.
Below is the error generated:

../zigbee/BDB/Source/NwkSteering/bdb_ns.c: In function 'vNsSendPermitJoin':
../zigbee/BDB/Source/NwkSteering/bdb_ns.c:783:48: error: 'apduZDP' undeclared (first use in this function)
783 | hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP); // ToDo - Clarify apduZCL is defined in application scope; how to link the name in BDB (independent of application)
| ^~~~~~~
../zigbee/BDB/Source/NwkSteering/bdb_ns.c:783:48: note: each undeclared identifier is reported only once for each function it appears in
../zigbee/BDB/Source/NwkSteering/bdb_ns.c: In function 'vNsTclkSendNodeDescReq':
../zigbee/BDB/Source/NwkSteering/bdb_ns.c:845:48: error: 'apduZDP' undeclared (first use in this function)
845 | hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP);
| ^~~~~~~
make[1]: *** [zigbee/BDB/Source/NwkSteering/subdir.mk:20: zigbee/BDB/Source/NwkSteering/bdb_ns.o] Error 1
make[1]: *** Waiting for unfinished jobs....
../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c: In function 'vFbSendIeeeAddrReq':
../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c:504:48: error: 'apduZDP' undeclared (first use in this function)
504 | hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP);
| ^~~~~~~
../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c:504:48: note: each undeclared identifier is reported only once for each function it appears in
../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c: In function 'vFbSendSimpleDescReq':
../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c:555:48: error: 'apduZDP' undeclared (first use in this function)
555 | hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP);
| ^~~~~~~


But it is solved now, i ran it with "pip install lxml" command and it worked. Thanks for the help

[mihai_ignat]

Thank you.
We will look into and come back with feedback.
Have a good day.
Mihai