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

Softdevice not working

Hello I'm a beginner using NRF51882, I do not have enough money to buy NDK51 Development or NRF Dongle, the solution I changed STLINK STM32 to JLINK by following tutorial on youtube www.youtube.com/watch and Development KIT BLE400 From waveshare, i tried all instances of program/example codes can not work except GPIO for example LED Blink or UART Communication, btw i'm using KEIL, -The question is whether to flashing softdevice must use JLINK Original from SEGGER? -Or should I use softdevice with certain version?

I hope friends can help, Thanks

Parents
  • I hope you see that $40 for nRF5x DK would solve all your troubles but anyway: flashing Soft Device has nothing to do with flasher. Just make sure you either are able to flash SD and app separately (meaning you can sector erase flash only where needed before flashing particular HEX) or simply merge them into one and flash to completely erased chip (that's quite easy and fail safe method).

    Your question about which SD version you should use worries me more: your application binary is more or less tight to particular SD version during compile time because you use corresponding API and set NVM (ROM) + RAM limits accordingly. So it you don't know which version to flash it's very likely that you are using wrong one and that simply makes you app not working. Please do step back and make sure which app binary (HEX) is using SD and what exact "flavor" (S110 vs. S120 vs. 130) and version you need. The everything should work well (assuming your application is written with your PCB/chip variant in mind - memory limits, HF/LF clock sources, LDO/DCDC convertor etc.)

Reply
  • I hope you see that $40 for nRF5x DK would solve all your troubles but anyway: flashing Soft Device has nothing to do with flasher. Just make sure you either are able to flash SD and app separately (meaning you can sector erase flash only where needed before flashing particular HEX) or simply merge them into one and flash to completely erased chip (that's quite easy and fail safe method).

    Your question about which SD version you should use worries me more: your application binary is more or less tight to particular SD version during compile time because you use corresponding API and set NVM (ROM) + RAM limits accordingly. So it you don't know which version to flash it's very likely that you are using wrong one and that simply makes you app not working. Please do step back and make sure which app binary (HEX) is using SD and what exact "flavor" (S110 vs. S120 vs. 130) and version you need. The everything should work well (assuming your application is written with your PCB/chip variant in mind - memory limits, HF/LF clock sources, LDO/DCDC convertor etc.)

Children
Related