NRF51822 Steps for Upload Bootloader,Softdevice,Application

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Vidar Berg — Mon, 19 Mar 2018 12:40:50 GMT

Changing the device type will reset the linker configuration to the default range for that device type. That is, use all available flash and ram. But it should have worked after you updated the settings to the correct values. For some reason, the ram allocation does not seem reflect the changes you made.

51822_xxAC and 51422_xxAC are identical except that the latter is licensed for use with the ANT protocol stacks (s2xx and s3xx). Suggest to try again with a clean SDK copy without making any changes to the configuration (you may add your own key set). Then verify that the initial stack pointer is >0x20002C00

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Mon, 19 Mar 2018 11:49:56 GMT

Hello vidar thanks,now what to do?

i'm not able to understand that you said"I see the device type has been changed from xxAC (default) to xxAA, which will reset the project configuration".

if i changed it AA so what happen by this change change .and should i change it to default ?

one other thing i used same AA for application so it's working. so is it right or wrong?

by default it comes with nrf51422..xxAC i'm using nrf51822 that's why i changed

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Mon, 19 Mar 2018 10:15:47 GMT

one other thing i observed that when i upload application + softdevice ,than application working fine,but after when upload dfu..application stop working and when i again upload application again than also application not working .i must have to upload softdevice .once again if i uploaded dfu . it means dfu may overwrite softdevice or something like that or not. i'm not sure

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Vidar Berg — Mon, 19 Mar 2018 10:15:21 GMT

I see the device type has been changed from xxAC (default) to xxAA, which will reset the project configuration. The linker settings appear to be correct, but the .hex file you sent does not correspond with the configuration shown in the screenshot.

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Mon, 19 Mar 2018 10:08:31 GMT

Hello Vidar , Currently i have not written any project code. my first goal is to make possible to enable DFU service than after i will write code and upload via DFU.so for now we can use any example as i gave you notification example. so i need your help for upload DFU and make it working...

i already changedand compiled DFU settings as you gave earlier. i attached pic you can see it.and also sent you application settings

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Vidar Berg — Mon, 19 Mar 2018 09:45:39 GMT

The initial stack pointer for your bootloader is set to 0x20001418, which is in the softdevice's reserved memory. It's expected to be closer to 0x20003C00 with the default linker settings that I provided earlier.

Memory readout from the bootloader hex you sent:

Also noticed that the bootloader settings page at 0x3F000 is filled with invalid data.

I'm not sure what I have happened here. Could you share your project (remember to include necessary dependencies) ?

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Mon, 19 Mar 2018 08:20:46 GMT

Hello Vidar,i sent you all three files that i want to upload on device.please check it and give me updates.

Thank You.

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Mon, 19 Mar 2018 08:11:15 GMT

Hello Vidar,devzone.nordicsemi.com/.../DFU.hex devzone.nordicsemi.com/.../App_5F00_notification.hex devzone.nordicsemi.com/.../6675.s130_5F00_nrf51_5F00_2.0.1_5F00_softdevice.hex

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Vidar Berg — Fri, 16 Mar 2018 14:03:21 GMT

Could you share the hex files (bootloader + application) from your builds so I can try to run them here?

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Fri, 16 Mar 2018 13:14:11 GMT

when i flash app and softdevice.than app works

but when i flash app,softdevice and dfu than don't work

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Fri, 16 Mar 2018 13:12:39 GMT

i flashed one by one application,softdevice,dfu.

it doesn't work

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Fri, 16 Mar 2018 12:51:46 GMT

hello Vidar ,i flashed it.now what

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Fri, 16 Mar 2018 12:48:47 GMT

what i have to do now for this ..i mean have flash this one only..and what after that

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Vidar Berg — Fri, 16 Mar 2018 12:46:48 GMT

Ok thanks, here are the default linker settings:

If this doesn't help, are you able to debug the bootloader from Keil to see where it may become stuck/reset?

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Fri, 16 Mar 2018 12:39:22 GMT

Onboard chip: nRF51822
Communication distance (open outdoor@1M data rate): 30m
Frequency range: 2.4GHz
Operating voltage: 2.0V ~ 3.6V
ARM® CortexTM-M0 32 bit processor, 128 bit AES HW encryption, 256kB flash & 32kB RAM,

and using ST-LINK V2 for Programming

sdk version is SDK 12.3

i'm able to flash programming using Keil and Opencd but don't know steps to solve this problem

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Vidar Berg — Fri, 16 Mar 2018 12:30:28 GMT

Please let me know the SDK version, softdevice version, and the chip variant you are using. Correct linker configuration depends on the setup.

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Mannu — Fri, 16 Mar 2018 04:23:50 GMT

i didn't change anything i used dfu bootloader example as it is and sent you screenshot of it's rom location..so tell me what ROM configuration i should do.and for what i mean bootloader, softdevice and application.and make change in softdevice because i have only hex file for it.

when i upload flash using opencd like following

flash write_image softdevice.hex 0

than loaded ....than after i load application

flash write_image application.hex 0

also loaded than i give

reset run

after this command device running and advertising service...it's works fine

but when after this i upload dfu bootloader ..by keil uvision

bootloader get uploaded but device stop to running and doesn;'t advertsing

so what is the problem ..is dfu overwrite or something like that.

i can't understand

RE: NRF51822 Steps for Upload Bootloader,Softdevice,Application

Vidar Berg — Thu, 15 Mar 2018 13:52:46 GMT

Hi,

The linker settings shown in you screen-dump is incorrect, the first section of flash is actually reserved for the softdevice (memory layout). Recommend that you get a clean copy of the SDK, and use the default bootloader example as reference.