Bootloader Logging for BLE Fails

RE: Bootloader Logging for BLE Fails

Hung Bui — Mon, 20 Jul 2020 10:22:36 GMT

Hi Joe,
If you configure the chip flash's size according to the actual flash size of the chip you should receive an error when trying to build the application if the memory exceed the actual flash size on the chip.

The start address of the bootloader and the flash size is configured in the project configuration, depends on which IDE you use.

RE: Bootloader Logging for BLE Fails

joer55 — Mon, 20 Jul 2020 04:44:45 GMT

Thanks Turbo 1 for the information. Do you know how much I would need to lower the bootloader start address (or should I do this by trial and error)? Also, I assume I do this thru the sdk_config.h file - is that true?

Thanks

RE: Bootloader Logging for BLE Fails

Turbo J — Fri, 17 Jul 2020 16:55:06 GMT

Enabling NRF logging substantially increases the flash memory footprint.

You will most likely need to lower the start address for the bootloader to be able to run.

RE: Bootloader Logging for BLE Fails

joer55 — Fri, 17 Jul 2020 15:39:16 GMT

Hi Hung:

Thanks for your quick reply. Some more details about our setup:

- Yes these are 2 separate bootloaders and do not run on the device at the same time. We reflash the device to load one or the other.

- We are not comparing the behavior of the 2. The USB bootloader is for development, the BLE bootloader is our customer facing bootloader. Both are needed.

- We did base these 2 bootloaders on the SDK bootloader example code in SDK 15.0.0.0

- Yes, the Serial Debug port is the UART we have connected to our device.

- I'll try to capture the UART output from the failures and get the information to you.

RE: Bootloader Logging for BLE Fails

Hung Bui — Fri, 17 Jul 2020 13:50:39 GMT

Hi Joe,

I just want to clarify that you have 2 separate bootloaders and they are not running on the same device, correct ? You just want to compare the behavior between the two ? Could you give more information about the bootloaders ? Did you base the bootloader on our bootloader example ? which SDK was that ?

When you mentioned "serial debug port" you meant UART ?

We will need to look into the reason for disconnection and/or image failed to transfer/launch. Please provide more debug information bout any disconnect reason, DFU terminate reason, etc. We need to look into why printing log in UART affect DFU process.
A sniffer trace of the DFU process would also be useful.