Bootloader Logging for BLE Fails

[joer55]

Hello:

We are developing a DFU bootloader for an NRF52 product that supports USB and BLE upload methods (they are 2 separate bootloaders from a common source).  Both work as expected (able to boot the device and download firmware applications correctly). With the USB bootloader we can enable logging in the sdk_config.h file and see output logging on our serial debug port.  When logging is enabled with BLE  bootloader, we see logging but the BLE connection either disconnects or the Firmware update does load correctly (and never launches) or we get dropped log errors (and the firmware does not load correctly).  The BLE bootloader works fine if we disable logging but we cannot debug it without printouts.  What can we do to enable BLE logging in our bootloader and still have it upload our firmware correctly?

Thanks

[joer55]

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

[Hung Bui]

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.