Bootloader debug message cuts off

RE: Bootloader debug message cuts off

Einar Thorsrud — Tue, 10 Nov 2015 07:03:29 GMT

I'm glad to hear it fixed your problem, judepinto24. If you are satisfied with he answer I would be happy if you could accept it (by clicking on the check mark below the voting buttons).

RE: Bootloader debug message cuts off

JudePinto — Mon, 09 Nov 2015 20:39:41 GMT

Thanks Einar, increaseing the buffer size worked perfectly. All the messages are coming out now.

RE: Bootloader debug message cuts off

Einar Thorsrud — Mon, 09 Nov 2015 12:49:34 GMT

It seems like the UART TX buffer size can be too small. The DeviceManager sometimes pushes a lot of debug printouts, and the 1024 bytes that are used in many examples is not always enough. Can you try to increase it to e.g. 2048?

RE: Bootloader debug message cuts off

JudePinto — Fri, 06 Nov 2015 20:03:24 GMT

I will look into that. Do you know if the app_trace.c file is required for debugging with RTT?

RE: Bootloader debug message cuts off

JudePinto — Fri, 06 Nov 2015 20:01:39 GMT

I am not resetting the device myself, either in software or hardware. And the device is advertising after the "[DM]:eb" line comes out, so i dont think there is a reset happening.

There does seem to be alot of white spaces before the"[DM]:eb", not sure if it is missing a carriage return. Might just be alot of white space.

RE: Bootloader debug message cuts off

syntroniks — Fri, 06 Nov 2015 18:33:46 GMT

I experienced difficulties with debugging lots of uart data. It turns out that the UART is significantly less capable than the RTT utility. I strongly recommend moving over to RTT.

RE: Bootloader debug message cuts off

Einar Thorsrud — Fri, 06 Nov 2015 12:28:15 GMT

Is the device being reset while writing the line staring with "[DM]:[0x05]"? And is the next line where we see ("[DM]:eb" proceeded by a lot of white spaces or missing carriage return) written after the reset?