BLE dfu/I2C EEPROM update

RE: BLE dfu/I2C EEPROM update

Hung Bui — Mon, 14 Dec 2015 12:51:16 GMT

Hi BT, I afraid we won't be able to provide the source code of the nrf.exe tool. But you can create the zip file without using the nrf.exe.

The instruction to generate the init data without using nrf.exe is described here.

The manifest.json file can be edited using notepad, and since you have control over the smartphone app you should be able to add the support for the EEPROM update beside application, bootloader, and softdevice update.

RE: BLE dfu/I2C EEPROM update

Andreas — Mon, 14 Dec 2015 08:58:44 GMT

Hi Hung Bui, thanks for your idea. But if I would implement it like this, the user must do the update procedure in two steps. First uploading the .zip package for the EEPROM and second uploading the .zip package for the application itself. Am I right? This would not be really comfortable for the end user. Do you see any chance to update the nrf.exe tool to get an additional EEPROM.hex file into the .zip archive (is the source code for the nrf.exe tool available?) ? Of course, also the Smartphone App and the Bootlader must be able to handle this... Regards!

RE: BLE dfu/I2C EEPROM update

Hung Bui — Fri, 11 Dec 2015 10:00:28 GMT

Hi BT,

I'm thinking of an easier way that you don't have to modify the app and the zip file is that you can re-use application DFU to update the external EEPROM.

Basically, in the bootloader, after you have copied the new app image into the swap bank (the original app has not been erased yet), you can check if there is a flag (at address 0x00 for example) with first 6 bytes = "EEPROM". Then you know it's not the app image but the external EEPROM image. Then you can start writing to I2C with this image, instead of swapping with bank 0.

By doing that you still can keep the app, CRC checking, init packet generator. You only have to modify the bootloader.