I used bootloader V5.4 and i dont see the prints

[Hadar]

 Hi,

i use NRF52832

I used bootloader V5.4 and I don't see the prints I used SEGGER workspace 

 in sdk the settings set #define NRF_LOG_DEFAULT_LEVEL 4

what can I do to see the prints in rtt viewer 

and more question 

in DFU mode how can i know that the BL SW received all the BLE package 

the BL not return success or fail 

if the crc in the flash and the crc of Bluetooth not match what can I do to fix it

Thanks Hadar

[Edvin]

Hello,

I used bootloader V5.4

What is that? Where did you find it? I am not familiar with this version number/format.

Are you using the nRF5 SDK? Are you using the secure_bootloader?

in DFU mode how can i know that the BL SW received all the BLE package 

What do you mean?

the BL not return success or fail 

What does that mean?

if the crc in the flash and the crc of Bluetooth not match what can I do to fix it

I guess you need to update the FW again.

I am sorry, but I don't think I understand your questions. Can you please try to explain a bit more? Perhaps a screenshot showing what you are seeing is helpful.

Best regards,

Edvin

[Hadar]

Hi 

I used Secure_Bootloader 

and I have 3 questions

1. I cant see the prints in RTT viewer I need it for debug the SW (which settings I need to change for it?).

2. when I burned the SW how can I know that the package transfer completely?

there is not CRC for each package.

3. I want to reduce the burning time do you have any suggestions for me?

thanks,

Hadar

[Edvin]

Ah, the v5.40 refers to your version of Segger Embedded Studio. That is fine. 

What SDK version are you using?

The "secure_bootloader" project doesn't have any RTT logging. If you want RTT logging in your bootloader, you must use the _debug version of the bootloader. I don't know what sort of bootloader, but if you are using the UART bootloader, you must use the pca10040_uart_debug. If you are using the BLE bootloader, you must use the pca10040_s132_ble_debug. These projects are already set up with RTT logging.

2: What do you mean by "burn the SW"? Do you mean flash the bootloader using Segger Embedded Studio? Or do you mean transfer the application image?

3: That depends on what you mean by "burning". Do you mean programming the bootloader or transferring the new application image?

BR,
Edvin

[Hadar]

Hi ,

thanks for your fast answer,

1. where I found the debug version? its the same version like the SW I used?

2,3. i mean to burning new application.

[Edvin]

Do you have a folder containing the SDK on your computer? If so, what do you see inside the folder:

SDK\examples\dfu\secure_bootloader\ ?

2,3: Using the bootloader to transfer the appliaction image that you generated using nrfutil, or using a programmer to program the application's .hex file directly?

[Hadar]

this is what in my SDK 17.2 folder

2,3 i used nrfutil to the bootloader ttranferation 

[Edvin]

We do not have a SDK17.2 release.

Our latest nRF5 SDK release is SDK17.1.0:

Also, I see that you don't have the "examples" folder. Where is your bootloader project located? 

2,3:

So you mean transferring an application image, using the bootloader then. I assume you are using a BLE bootloader, since you said "how can i know that the BL SW received all the BLE package" in your original post. The BLE stack will handle retransmissions, so you don't need to worry about that.

How do you transfer the image? Do you use nRF Connect for Desktop -> Bluetooth Low Energy? Or do you use nRF Connect for Android/BLE? Or do you use nrfutil directly?

BR,
Edvin