• State Verified Answer
  • Locked Locked
  • Replies 11 replies
  • Subscribers 25 subscribers
  • Views 354 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 288564
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Multi-NUS-Master forwards gibberish from Peripherals

user68828

After several months of attempts, I was finally able to load, build, and flash the code from multi-NUS-master.zip using the VS version of nRF Connect, onto the nRF52840 DevKit. The code appears to run, and it connects to multiple Peripherals via the NUS service. When a peripheral sends data via NUS, the master tries to forward it via the Interface MCU to the USB serial port. However, the data is gibberish. I have looked at the data being received, on the serial TxD line (P0.06) between the nRF52840 and the Interface MCU. It should be pure printable ASCII text, but the first few bytes are 0x00, 0x1D, 0x00, 0x20, 0x03. The over-the-air BLE data is fine, because I can view that with a single-connection version of the uart-c example running on another board. So I am suspecting that somewhere in the multi-NUS-master code a buffer is not being allocated correctly, a pointer is corrupted, etc. I furhter suspect the underlying problem is that I missed configuring something important in the nRF Connect or VS installation. Can anybody give me some pointers? (pun intended)

Parents
  • 0

    If I load the standard uart_c app (single channel) on an nRF52832 DK it works just fine.

    Thank you for the pointers. That should get me enough to dig down into the code and find where it's going astray. But in the meantime, is there anything I would have been likely to miss, either in configuring nRF Connect and VS, or in the project configuration? Something relating to memory allocation would be suspicious.

Reply
  • 0

    If I load the standard uart_c app (single channel) on an nRF52832 DK it works just fine.

    Thank you for the pointers. That should get me enough to dig down into the code and find where it's going astray. But in the meantime, is there anything I would have been likely to miss, either in configuring nRF Connect and VS, or in the project configuration? Something relating to memory allocation would be suspicious.

Children
No Data
Related
Terms of service