<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Wireless MCUのトピックRe: OM15080-JN5189 Dongle Communication Problem</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2102765#M19713</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/250638"&gt;@Parth_911&lt;/a&gt;&amp;nbsp;.&lt;/P&gt;
&lt;P&gt;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&amp;nbsp;11.10.0, but I've checked also on&amp;nbsp;&lt;SPAN&gt;v24.12 [Build 148] [2025-01-10] and I can build and flash the binary fine.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Because of limited availability of JN5189 USB dongle, I'm using a JN5189 on a DK6 v3 EVK, see attached image:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mihai_ignat_0-1747919091145.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/339266i6EDE1CFC0B2668A2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mihai_ignat_0-1747919091145.png" alt="mihai_ignat_0-1747919091145.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;I've checked with dk6prog on Windows and I can paste the output:&lt;/P&gt;
&lt;LI-CODE lang="ruby"&gt;C:\Users\user&amp;gt;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&amp;gt;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&amp;gt;
C:\Users\user&amp;gt;dk6prog -d 0 erase 0 0x9de00

This is an experimental utility. Use with caution!

Erasing memory  [####################################]  100%

C:\Users\user&amp;gt;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&amp;gt;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After this procedure, I can open a serial terminal like MobaXterm and I can see the output:&lt;/P&gt;
&lt;LI-CODE lang="ruby"&gt;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&lt;/LI-CODE&gt;
&lt;P&gt;Can you please check on your side with the commands and the binary I provided?&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Mihai&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 May 2025 13:24:35 GMT</pubDate>
    <dc:creator>mihai_ignat</dc:creator>
    <dc:date>2025-05-22T13:24:35Z</dc:date>
    <item>
      <title>OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2099798#M19706</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am currently working with&amp;nbsp;&lt;SPAN&gt;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&amp;nbsp;OM15080-JN5189 dongles.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can you please help me to resolve this problem? Any source for zigbee / IEEE comunication protocol which can help me solve this problem.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2025 10:14:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2099798#M19706</guid>
      <dc:creator>Parth_911</dc:creator>
      <dc:date>2025-05-19T10:14:46Z</dc:date>
    </item>
    <item>
      <title>Re: OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101615#M19707</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;
&lt;P&gt;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?&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Mihai&lt;/P&gt;</description>
      <pubDate>Wed, 21 May 2025 12:16:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101615#M19707</guid>
      <dc:creator>mihai_ignat</dc:creator>
      <dc:date>2025-05-21T12:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101622#M19708</link>
      <description>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.&lt;BR /&gt;</description>
      <pubDate>Wed, 21 May 2025 12:30:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101622#M19708</guid>
      <dc:creator>Parth_911</dc:creator>
      <dc:date>2025-05-21T12:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101625#M19709</link>
      <description>Thank you for the information.&lt;BR /&gt;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?&lt;BR /&gt;Thanks.&lt;BR /&gt;Mihai</description>
      <pubDate>Wed, 21 May 2025 12:35:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101625#M19709</guid>
      <dc:creator>mihai_ignat</dc:creator>
      <dc:date>2025-05-21T12:35:03Z</dc:date>
    </item>
    <item>
      <title>Re: OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101632#M19710</link>
      <description>Yes, the SDK version is SDK_2.6.16_JN5189. The download link is as follows:&lt;BR /&gt;&lt;A href="https://mcuxpresso.nxp.com/download/c92a15504c3c619ff1accdba3c729d2b" target="_blank"&gt;https://mcuxpresso.nxp.com/download/c92a15504c3c619ff1accdba3c729d2b&lt;/A&gt;</description>
      <pubDate>Wed, 21 May 2025 12:43:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101632#M19710</guid>
      <dc:creator>Parth_911</dc:creator>
      <dc:date>2025-05-21T12:43:28Z</dc:date>
    </item>
    <item>
      <title>Re: OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101638#M19711</link>
      <description>Thank you.&lt;BR /&gt;We will look into and come back with feedback.&lt;BR /&gt;Have a good day.&lt;BR /&gt;Mihai</description>
      <pubDate>Wed, 21 May 2025 12:47:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2101638#M19711</guid>
      <dc:creator>mihai_ignat</dc:creator>
      <dc:date>2025-05-21T12:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2102765#M19713</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/250638"&gt;@Parth_911&lt;/a&gt;&amp;nbsp;.&lt;/P&gt;
&lt;P&gt;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&amp;nbsp;11.10.0, but I've checked also on&amp;nbsp;&lt;SPAN&gt;v24.12 [Build 148] [2025-01-10] and I can build and flash the binary fine.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Because of limited availability of JN5189 USB dongle, I'm using a JN5189 on a DK6 v3 EVK, see attached image:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mihai_ignat_0-1747919091145.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/339266i6EDE1CFC0B2668A2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mihai_ignat_0-1747919091145.png" alt="mihai_ignat_0-1747919091145.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;I've checked with dk6prog on Windows and I can paste the output:&lt;/P&gt;
&lt;LI-CODE lang="ruby"&gt;C:\Users\user&amp;gt;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&amp;gt;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&amp;gt;
C:\Users\user&amp;gt;dk6prog -d 0 erase 0 0x9de00

This is an experimental utility. Use with caution!

Erasing memory  [####################################]  100%

C:\Users\user&amp;gt;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&amp;gt;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After this procedure, I can open a serial terminal like MobaXterm and I can see the output:&lt;/P&gt;
&lt;LI-CODE lang="ruby"&gt;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&lt;/LI-CODE&gt;
&lt;P&gt;Can you please check on your side with the commands and the binary I provided?&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Mihai&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 13:24:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2102765#M19713</guid>
      <dc:creator>mihai_ignat</dc:creator>
      <dc:date>2025-05-22T13:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2103200#M19714</link>
      <description>&lt;P&gt;hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP); // ToDo - Clarify apduZCL is defined in application scope; how to link the name in BDB (independent of application)&lt;/P&gt;&lt;P&gt;The above code is in &amp;lt;project_name&amp;gt;/zigbee/BDB/Source/NwkSteering/bdb_ns.c&lt;BR /&gt;&lt;BR /&gt;How to solve this , it seems like that error occurs here when we try to build the example code without any modifications.&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 06:24:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2103200#M19714</guid>
      <dc:creator>Parth_911</dc:creator>
      <dc:date>2025-05-23T06:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2103234#M19715</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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".&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Mihai&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 06:57:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2103234#M19715</guid>
      <dc:creator>mihai_ignat</dc:creator>
      <dc:date>2025-05-23T06:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: OM15080-JN5189 Dongle Communication Problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2103355#M19716</link>
      <description>hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP); // ToDo - Clarify apduZCL is defined in application scope; how to link the name in BDB (independent of application)&lt;BR /&gt;&lt;BR /&gt;This is the line in bdb_ns.c file.&lt;BR /&gt;Below is the error generated:&lt;BR /&gt;&lt;BR /&gt;../zigbee/BDB/Source/NwkSteering/bdb_ns.c: In function 'vNsSendPermitJoin':&lt;BR /&gt;../zigbee/BDB/Source/NwkSteering/bdb_ns.c:783:48: error: 'apduZDP' undeclared (first use in this function)&lt;BR /&gt;783 | hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP); // ToDo - Clarify apduZCL is defined in application scope; how to link the name in BDB (independent of application)&lt;BR /&gt;| ^~~~~~~&lt;BR /&gt;../zigbee/BDB/Source/NwkSteering/bdb_ns.c:783:48: note: each undeclared identifier is reported only once for each function it appears in&lt;BR /&gt;../zigbee/BDB/Source/NwkSteering/bdb_ns.c: In function 'vNsTclkSendNodeDescReq':&lt;BR /&gt;../zigbee/BDB/Source/NwkSteering/bdb_ns.c:845:48: error: 'apduZDP' undeclared (first use in this function)&lt;BR /&gt;845 | hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP);&lt;BR /&gt;| ^~~~~~~&lt;BR /&gt;make[1]: *** [zigbee/BDB/Source/NwkSteering/subdir.mk:20: zigbee/BDB/Source/NwkSteering/bdb_ns.o] Error 1&lt;BR /&gt;make[1]: *** Waiting for unfinished jobs....&lt;BR /&gt;../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c: In function 'vFbSendIeeeAddrReq':&lt;BR /&gt;../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c:504:48: error: 'apduZDP' undeclared (first use in this function)&lt;BR /&gt;504 | hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP);&lt;BR /&gt;| ^~~~~~~&lt;BR /&gt;../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c:504:48: note: each undeclared identifier is reported only once for each function it appears in&lt;BR /&gt;../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c: In function 'vFbSendSimpleDescReq':&lt;BR /&gt;../zigbee/BDB/Source/FindAndBind/bdb_fb_initiator.c:555:48: error: 'apduZDP' undeclared (first use in this function)&lt;BR /&gt;555 | hAPduInst = PDUM_hAPduAllocateAPduInstance(apduZDP);&lt;BR /&gt;| ^~~~~~~&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;But it is solved now, i ran it with "pip install lxml" command and it worked. Thanks for the help</description>
      <pubDate>Fri, 23 May 2025 08:29:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/OM15080-JN5189-Dongle-Communication-Problem/m-p/2103355#M19716</guid>
      <dc:creator>Parth_911</dc:creator>
      <dc:date>2025-05-23T08:29:41Z</dc:date>
    </item>
  </channel>
</rss>

