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

ble_app_hids_mouse could not run

Hi  all ; 

         I  am the new guy of using the nordic ble . Now I met some problems when I create the project:

sdk :nRF5_SDK_12.3.0_d7731ad

chip :nRF51822

1.  Using the nRF5_SDK_12.3.0_d7731ad\examples\ble_peripheral\ble_app_hids_mouse\pca10028\s130\arm4\ble_app_hids_mouse_pca10028_s130.uvproj create the project is ok , but I notice that project select target is nrf51422_xxac , could it  run on the 51822 chip ? I found all the example projects without  nrf51822 as the select target .

2. According to the document , it need to program the softdevice , so I download s130_nrf51_1.0.0_softdevice.hex from the website , but after program the softdevice it cannot program the application software. In this case I guess it is the softedevice do not match the application , so I use  the project  nRF5_SDK_12.3.0_d7731ad\examples\ble_peripheral\ble_app_hids_mouse\pca10028\s130\arm4\ble_app_hids_mouse_pca10028_s130.uvproj  to select target as flash_s130_nrf51_2.0.1_softdevice to build the softdevice , after solve all the missing file at the end it also has a error:

linking...
..\..\..\..\..\..\components\softdevice\s130\hex\s130_nrf51_2.0.1_softdevice.sct(7): error: L6236E: No section matches selector - no section to be FIRST/LAST.
Not enough information to list image symbols.
Not enough information to list the image map.
Finished: 2 information, 0 warning and 1 error messages.
"..\..\..\..\..\..\components\softdevice\s130\hex\s130_nrf51_2.0.1_softdevice.hex" - 1 Error(s), 0 Warning(s).
Target not created.
Build Time Elapsed: 00:00:05

It seems a long way to create a sample for me and make me crazy .  Someone can help ?????

Parents
  • This is quite a normal mistake to make. You should in general always use the softdevice that comes with the sdk version you are using (check the folder: nRF5_SDK_12.3.0_d7731ad\components\softdevice\s130\hex). You never want to compile the softdevice. 

    If you go back to the softdevice hex file folder, you notice that the softdevice hex file has become a Windows Script component now. Delete all the files that were created in that folder, download the correct softdevice hex file & put it back in that folder.

    Here is a link to the correct softdevice needed:

    s130_nrf51_2.0.1_softdevice.hex

    Once you have done this, erase the nrf51 chip, program the chip with the softdevice hex file (Flash -> Download tab or press F8 instead of F7) & then go back to the application & flash the program to the nrf51.

Reply
  • This is quite a normal mistake to make. You should in general always use the softdevice that comes with the sdk version you are using (check the folder: nRF5_SDK_12.3.0_d7731ad\components\softdevice\s130\hex). You never want to compile the softdevice. 

    If you go back to the softdevice hex file folder, you notice that the softdevice hex file has become a Windows Script component now. Delete all the files that were created in that folder, download the correct softdevice hex file & put it back in that folder.

    Here is a link to the correct softdevice needed:

    s130_nrf51_2.0.1_softdevice.hex

    Once you have done this, erase the nrf51 chip, program the chip with the softdevice hex file (Flash -> Download tab or press F8 instead of F7) & then go back to the application & flash the program to the nrf51.

Children
No Data
Related