Device Name shows as "N/A" after changing bootloader

[Brook Gebremedhin]

Hello,

my application hex used to work fine before i change my bootloader and softdevice now after falshing all the hex including the application , it is advertising as N/A i can connect to it and am still getting my service.

Q1)All work fine except it is advertising as N/A. This same hex used to advertise fine before boot loader change ?

Q2) when i change the bootloader i have used boot loader_setting .hex that was mentioned in other forum to skip the validation (crc check). do i have to do this everytime , even though my application is valid ?

Looking forward to your Answer

[Hung Bui]

Hi Brook, Which tool/app did you use to scan and read the advertising packet ? Have you try to cross check on other scanner ?

Q1. Are you sure you have jumped to the application or it is still in bootloader ? I'm suspecting it could be the issue on the scanner. You can also use the sniffer to track packets over the air. You mentioned you updated the softdevice, have you modified your application so that it's compatible with the new softdevice ? Could you give me more information about the version of the softdevice you replaced and the new one ?

Q2. If you don't write anything to the CRC value in the bootloader setting the CRC check will be skipped. By default our bootloader doesn't write CRC value in.

[Hung Bui]

Hi Brook,

I don't think softdevice on SDK v10 and SDK v11 would work with S110 v7.1.0. SDK v10 is compatible with S110 v8.0 and SDK v11 doesn't support S110.

You mentioned you still see the services, but does it operate normally ? Can you still read/write the characteristic ? I suspecting that it's simply the catched ATT table that the phone stored.

I would suggest you to follow what we have on the gcc bootloader on SDK v8 or later and apply that for SDK v7.x.

You can also think of using mbed FOTA provided here.