buttenlesss dfu interactive command and secure dfu uart

RE: buttenlesss dfu interactive command and secure dfu uart

Edvin — Fri, 19 Mar 2021 11:16:18 GMT

So no BLE in the bootloader at all, then?

In that case, you need to remove the ret_val = nrf_dfu_set_adv_name_init(); in ble_dfu_buttonless_async_svci_init() in ble_dfu_unbonded.c.

But really, it doesn't make much sense to use a buttonless dfu service if you are only using a bootloader that only supports UART. If you intend to have a bootloader that supports both uart and BLE, then you can put the nrf_dfu_set_adv_name_init() when you have included the BLE transport in the bootloader.

Best regards,

Edvin

RE: buttenlesss dfu interactive command and secure dfu uart

yu1998 — Fri, 19 Mar 2021 01:27:26 GMT

i use the sdk 17.0.2 dfu_uart_bootloader

RE: buttenlesss dfu interactive command and secure dfu uart

Edvin — Thu, 18 Mar 2021 10:27:41 GMT

Ok, I think the CLI is interacting with the RTT log in some way. I am not sure why I can't see any log on the RTT, but the error log appears on the CLI window.

Either way.

Your application requires a bootloader, so I flashed a bootloader and some bootloader settings.

But if I understand you correctly, the issues appear when you try to add UART to the bootloader? If so, I think I would need your bootloader as well.

Is your application main reached at all? Please note that to debug while a bootloader is present, you need to generate and program bootloader settings, and in SES, you need to program the application using nrfjprog, and then in segger embedded studio, use the Target -> Attach debugger:

Additionally, your application's main.c file has:

ret_code_t err_code;

APP_ERROR_CHECK(err_code) // two times, actually.

So you check the err_code that is not set to a value. Ideally, it will be 0 by default, but if the RAM has been used for something else, then it may contain some random value. Either remove the APP_ERROR_CHECK() or set the err_code = NRF_SUCCESS in main.c

RE: buttenlesss dfu interactive command and secure dfu uart

yu1998 — Thu, 18 Mar 2021 01:19:58 GMT

Edvin

s140_nrf52_7.2.0_softdevice

sdk 17.0.2

nrf52840

using segger embedded studio

RE: buttenlesss dfu interactive command and secure dfu uart

Edvin — Wed, 17 Mar 2021 11:49:09 GMT

Can I replicate this on a DK? If so, can you upload the project that I need to do so?

RE: buttenlesss dfu interactive command and secure dfu uart

yu1998 — Wed, 17 Mar 2021 08:26:00 GMT

the entire application stops and also Edvin

nothing shows

RE: buttenlesss dfu interactive command and secure dfu uart

Edvin — Wed, 17 Mar 2021 08:17:27 GMT

Try setting NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED to 0 in your sdk_config.h if you want to see the log output in the debug session in Segger Embedded Studio.

[quote user="yu1998"]i found out the code stuck in [/quote]

By stuck, do you mean that one of the function calls doesn't return, or is it one of the function calls that returns something other than 0 (NRF_SUCCESS)? which then is picked up by the VERIFY_SUCCESS and passed onto an APP_ERROR_CHECK()?

RE: buttenlesss dfu interactive command and secure dfu uart

yu1998 — Wed, 17 Mar 2021 02:20:43 GMT

devzone.nordicsemi.com/.../6445.sdk_5F00_config.hsdk_config

i found out the code stuck in

uint32_t ble_dfu_buttonless_async_svci_init(void)
{
    uint32_t ret_val;

    ret_val = nrf_dfu_svci_vector_table_set();
    VERIFY_SUCCESS(ret_val);

    ret_val = nrf_dfu_set_adv_name_init();
    VERIFY_SUCCESS(ret_val);

    ret_val = nrf_dfu_svci_vector_table_unset();

    return ret_val;
}

which is in ble_dfu_unbonded.c

RE: buttenlesss dfu interactive command and secure dfu uart

yu1998 — Wed, 17 Mar 2021 02:15:12 GMT

Edvin I use rtt client to see if there is any error but it did not show anything

main.c : devzone.nordicsemi.com/.../050217.main.c

RE: buttenlesss dfu interactive command and secure dfu uart

yu1998 — Wed, 17 Mar 2021 01:46:21 GMT

im using segger embedded studio

RE: buttenlesss dfu interactive command and secure dfu uart

Edvin — Tue, 16 Mar 2021 13:27:38 GMT

Hello,

[quote user=""]

now im trying dfu uart upload but strange thing happened using same application to upload with dfu_uart

but the application caanot work does anyone know why(no error showing)

knowing error because the interactive command does not wort

[/quote]

Have you tried debugging? It is not clear to me whether your application is starting or not. Try logging something in the start of your application and see if it shows. Try using another log backend than the uart, if your application is using UART for CLI or something. Use the RTT log backend, and disable deferred logging (set it to 0 in sdk_config.h).

Please note that if you have programmed a bootloader, you can't program the application directly with a programmer without also programming the bootloader settings. And if you want to run a debug session, make sure that the IDE is not programming the application, as this will probably not match the bootloader settings. Test this with an application that you know is working before you try it on the application you are not sure of. If you are not sure how to do this, please let me know what IDE you are using.

Best regards,

Edvin