why can cause this problem! I'm not familiar with NCS OTA
why can cause this problem! I'm not familiar with NCS OTA
app_update.zipthis is the .bin
app_update.zipthis is the .bin
Hi,
This bin looks good in this regard. Are you sure you get the "Invalid header magic number" error with this file? Or is it so that you get another error when you changed to (what looks like) the correct file?
Note that you can refer to the SMP Server Sample to see a working DFU example. I would recommend that you use that as a reference, and perhaps also test that sample first to check that your procedure is correct. Then, you can copy-paste configurations and a few things from main.c and bluetooth.c into your application in order to use it there.
it is new problem
As mentioned above,Migration steps inNCS2.0.0 is ok what different with NCS1.5.1
spring.liu said:it is new problem
Good to know. This is important information.
spring.liu said:As mentioned above,Migration steps inNCS2.0.0 is ok what different with NCS1.5.1
There has been a lot of changes between these (they are 5 releases apart, ignoring bug-fix release), but the fundamentals remain mostly the same. For details, you should refer to the SMP SVR sample for the release you are using.
spring.liu said:Add DFU support to your application - Software - nRF Connect SDK guides - Nordic DevZone (nordicsemi.com) it is ok ? where is SMP Server Sample path?
The principles are OK, but there are minor differences. The sample path is: <SDK>/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/
Do not work ! if you have the OTA example in ncs1.5.1 ,you can send to me
We do, that is the example I referred to under <SDK>/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/. See documentation here: SMP Server Sample. This sample works out of the box. You use it in the exact same way as you do with 2.0.0, just remember to use the configuration overlay file for Bluetooth when you build it.