Hi!
nRF52. S132, SDK13.
I try to use ble_dfu_send_hex example.
- what shoul I do first? via nrf gostudio load SD. correct?
Which SD? from this folder (dfu_test_softdevice_s132) Or usual SD (s132_nrf52_4.0.2_softdevice)
- what should I do next?
Hi!
nRF52. S132, SDK13.
I try to use ble_dfu_send_hex example.
Which SD? from this folder (dfu_test_softdevice_s132) Or usual SD (s132_nrf52_4.0.2_softdevice)
I need to know how familiar you are with the SDK to know how detail the instruction should be.
You understanding about micro ecc library was correct. Also, you don't have to do anything with your application if you don't plan to do buttonless DFU. If you want to do buttonless DFU you need to follow Appendix 2 in the blog.
What exactly the issue you are having now ?
About known SDK. somthing ofcourse I know. I used some examples for make my application. Try to explain for middle level. If I not understand You, I'll ask. First- let's start usual DFU with button. In the bootloader code I find place where I check pressed button:
if (1) //(nrf_dfu_enter_check())
{
NRF_LOG_DEBUG("Application sent bootloader request\n");
enter_bootloader_mode = 1;
}
and type if(1) therefore I suppose should advertise with DFUTarg? I can't understand- if I just flash SD and that bootloader- without any app- should DFUTarg service advertise? Or need app mandatory?
If you don't have any application flashed, the bootloader will detect that and will enter bootloader mode and wait for DFU update. Still could you describe what the problem you have now when following my guide ? Please try to test without any modification, the device should advertise as DFUTarg, you can check it using nRFConnect app on the phone or PC.
Hi! I don't have any advertise. I folow all steps till D1. I flashed only SD and bootloader. No advertise. I have nrf connect app. Additional- I use custom board. This board doesn't have cristall. We use RC. I mean
ble_stack_init()
nrf_clock_lf_cfg_t clock_lf_cfg = { .source = NRF_CLOCK_LF_SRC_RC,
.rc_ctiv = 16,
.rc_temp_ctiv = 2,
};
Maybe you should turn on Logging and check what is in the log. You can switch the log on in the SDK_config.h.
Also you can add breakpoint inside the bootloader to check what goes wrong. You may need to set optimization level to 0 to debug.