Hello,
about two years ago we have made a Device basked on SDK 13 with S132 4.0.2 on it.
Now we had to build a newer version for our application and for this we have taken the SDK 16 with S132 7.0.1.
Now it looke like the new Application is not compatible with the old boodloader and SD. Because after update the new application to an existing Tag the Tag/Device does not work.
So we think we have to update also the SD and the BL. For this I have build also the DFU Booloader from SDK 16 and I want to have a *.ziü file for the dfu with SD+BL+APP
I have genereated the *. zip file with the following tow way's:
nrfutil pkg generate --hw-version 1 --key-file C:\Entwicklung\BeverageMetrics\Firmware\BevMetTag\key\private.pem --application-version 1 --application ble_app_BevMetTag.hex --sd-req 0x98,0xCA --softdevice s132_nrf52_7.0.1_softdevice.hex --sd-id 0xCA --bootloader secure_bootloader_ble_s132_pca10040.hex --bootloader-version 1 BevMetTag_package.zip
nrfutil pkg generate --debug-mode --key-file C:\Entwicklung\BeverageMetrics\Firmware\BevMetTag\key\private.pem --application ble_app_BevMetTag.hex --sd-req 0x98,0xCA --softdevice s132_nrf52_7.0.1_softdevice.hex --sd-id 0xCA --bootloader secure_bootloader_ble_s132_pca10040.hex BevMetTag_package_debug.zip
But every time I want to update an existing Tag with the NRF Connect I got a Timeout after the SD+BL was tranfered to the Device. And at the moment I realy don't know what I should do to be able to update my devices with this new *.zip file!
regards
markus
