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

How to download Project ‘usbd_ble_uart_pca10056_s140’ in nrf52 dongle

I am converting the the Project ‘usbd_ble_uart_pca10056_s140’ to pca10059, to download it in the nrf52840 dongle. I followed the steps in the nRF52840 Dongle Programming Tutorial and changed the processor and linker attributes. But an error is occurring when linking or creating the new pca10059 hex file. Is there any one how has ever done this conversion with a large software code ? I am new to these things and do not know how to set the parameters inside the linker.  

These are the the changes as descried in the nRF52840 Dongle Programming Tutorial 

  

This is the error is popping up, after I do the changes and build the project.

Thanks

Parents
  • Hi,

    Sorry for the late reply. Since this example uses SoftDevice the only thing you need to do is to update the Preprocessor Definitions by removing BOARD_PCA10056 and inserting BOARD_PCA10059 and you should be able to build the example. You don't need to adjust the linker configuration.

    Did you check if you were able to build the example out of the box? It could be that your working directory is in a too deep level (i.e. long path name). This is a problem related to Windows path limitation, and is a known issue when the names get too long. You can try to move the SDK folder to level that is not that deep.

    Best regards,

    Marjeris

  • Hi, I tried your approach, it builds but I am encountering another problem related to the nrf connect app when programing the dongle.

    The problem is related to the SoftDevices. When writing the new hex file I chose 0XAE (s140_nrf52_6.1.0) for the sdk15.3.0.  I also chose 0XA9 (s140_nrf52_6.0.0) and all the rest just to try. But still I did not fix the issue.

    Is there something I am missing to do ?

Reply
  • Hi, I tried your approach, it builds but I am encountering another problem related to the nrf connect app when programing the dongle.

    The problem is related to the SoftDevices. When writing the new hex file I chose 0XAE (s140_nrf52_6.1.0) for the sdk15.3.0.  I also chose 0XA9 (s140_nrf52_6.0.0) and all the rest just to try. But still I did not fix the issue.

    Is there something I am missing to do ?

Children
Related