Same Code working on nrf51442 and not working on nrf51882

[soumil]

Hi,

I faced a strange kind of issue while i was burning the same code on nrf51442 and nrf51882 chip. The code is running fine on the nrf51442 chip but the code wasn't running on the nrf51882 chip even after changing the RAM and ROM address. I debugged the code and it came out to be the custom service i created that was creating a problem. When i removed the custom service file from my project, the code ran on the nrf51882.

After this i created a new project, and then added all my files into it and created a new service file. Created a hex file and then burned the program and the same code started to work on the nrf51882 chip as well as nrf51442 chip.

I am still not able to figure out why such a behavior would come up. Its the same code but with different project files. I dont think there is any settings in Keil that i am missing since in both the projects, i have kept the same settings except for the RAM and ROM address.

Also should I create two separate project files for nrf51882 and nrf51442. Any help on this would be appreciated.

[Stefan Birnir Sverrisson]

Hi

nRF51822 and nRF51422 are the same IC, nRF51822 just does not accept ANT softdevices, see this thread.

Checklist:

• Check in the nRF51 compatibility matrix if the ICs are the same nRF51 revision?
• Do the two ICs have different RAM sizes? Perhaps the nRF51822 has run out of RAM since it stops working when adding a service. [1] [2] [3]

[Stefan Birnir Sverrisson]

You should monitor how much RAM you are using when you compile your code. Usually the RAM is allocated statically, so it is not like you are running unexpectedly out of RAM when running your application. Heap and RAM is reserved at startup, and so is the RAM space for the BLE services. So if your application does not run because of RAM shortage, put your program on a RAM diet, and then try to run the application again.