This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

UART Program not working with custom board

Hello,

   I designed custom board using nRF52832. BLE Blinky code is working after uploading. I can able to see my ble with NORDIC BLINKY app and I can control LED. But while uploading UART code I didn't see BLE in UART APP of nordic. Please help me regarding. Thanks.

Parents
  • Hi, 

    After further evaluation, I've decided re-open this ticket and close all other tickets that you have created on this issue. Keep any information regarding this issue to this ticket.

    Regarding your issue. 

    I would assume that the HW is correct, if other BLE examples work such as the BLE Blinky and you can see that it advertises. Is the ble_app_uart example completely unmodified? Did you change the board file?

    Which UART app are you using? nRF UART or the UART console in the nRF Toolbox? 

    regards

    Jared 

  • Hi,
     I didn't change any board file. The custom board we recently designed work well with BLE Blinky. Only BLE UART is not working. I tried using nRF UART and nRF Toolbox app. In both BLE is not showing.

  • Hi,

    So you're getting an assert in the UART event handler, which would explain why don't see the board advertising. Are you sending any data? Could you try setting a breakpoint in the handler and see exactly what function call that causes it to assert? 

    My guess is that it asserts here:

    Could you verify it by setting a breakpoint there and see what the error code is. 

    DD_ said:
    I didn't change any board file.

     You have to change the board file to a custom board file so that pins are mapped correctly. 

    regards

    Jared 

  • Hi,
     I don't know why breakpoint is coming. I didn't send any data. I am only trying to advertise Bluetooth with BLE UART code. I am using reference design from NRF52 series. Then I need to change custom board file. I am attaching schematic too. Please help us regarding. Thanks.

  • Hi,

    DD_ said:
     I don't know why breakpoint is coming

     What does this mean? Does the program stop at the breakpoint I suggested in my previous reply?

    The unmodified example uses pins 5-8 for the UART. These pins are not connected to anything in your custom board. You would therefore have to change the board file so that they are mapped appropriately. Or change the pins in the application. 

    Also, your schematic is mostly ok. Only concern is that you're using the pins on the upper side for I2C. The pins on the upper and right side of the IC is marked as low frequency/low drive, using these pins for serial communication might cause interference with the radio signal. However, I don't think your current problem is related to this. 

    regards

    Jared 

  • Dear Jared,

      After debug I got following error. I am attaching image. Please check. kindly help us regarding.Error in 561.


  • Hi.

    Seems like the issue is still somewhere in the uart_event_handle(). Try setting breakpoints in the various cases in the switch case and see where the application stops.

    Did you make a board file? The easiest is just to copy the PCA10040 board file and then adjust it to your board. 

    Note: Debugging Softdevice applications requires that you restart the application each time the application starts. The application will assert otherwise i.e if you try to resume the application after it has stopped at a breakpoint. This makes it not possible to step through code step-by-step in  a SD application. See this and this thread for more info.

    regards

    Jared  

Reply
  • Hi.

    Seems like the issue is still somewhere in the uart_event_handle(). Try setting breakpoints in the various cases in the switch case and see where the application stops.

    Did you make a board file? The easiest is just to copy the PCA10040 board file and then adjust it to your board. 

    Note: Debugging Softdevice applications requires that you restart the application each time the application starts. The application will assert otherwise i.e if you try to resume the application after it has stopped at a breakpoint. This makes it not possible to step through code step-by-step in  a SD application. See this and this thread for more info.

    regards

    Jared  

Children
No Data
Related