OTP标题对广告的影响

你好，

Thanks for your answer!

What I have is a secondary bootloader which looks for data over the UART and goes into deep sleep after a while if none received. So the application is copied into SysRam once downloaded exactly like in the secondary bootloader example. And of course I've got a micro into which I put a binary file as an array and which transfer the application over the UART.

总结：

da14580-01 (bootloader) <-----UART-----> Micro (reporter app)

- Bootloader从Retention RAM开始并运行
- bootloader receive the reporter app via the UART and copies it to Sysram
- Bootloader触发软复位
- reporter app starts

有关调试目的，我完成了以下所有过程：

- Micro waits for the bootlader
- 使用JTAG将引导加载程序复制到DA14580-01中
- 引导加载程序启动，复制报告器应用程序并触发软复位
- 广告框架正常

To do so I had to modify the bootloader scatter file in such a way:

lr_irom1 0x20000000 0x00008000 {;加载区域size_region.
ER_IROM1 0x20000000 0x00002000 { ; load address = execution address
*.o (RESET, +First)
*（Inroot $$部分）
startup_cmsdk_cm0.o.
system_cmsdk.o.
}

ER_IROM2 0x80000 0x2000 {
.ANY (+RO)
.ANY (+RW +ZI)
.any（堆栈）
}
}

然后我回到正常的分散文件：

LR_IROM1 0x00000000 0x00008000 { ; load region size_region
ER_IROM1 0x00000000 0x00002000 {;加载地址=执行地址
*.o (RESET, +First)
*（Inroot $$部分）
startup_cmsdk_cm0.o.
system_cmsdk.o.
}

ER_IROM2 0x80000 0x2000 {
.ANY (+RO)
.ANY (+RW +ZI)
.any（堆栈）
}
}

并如前一篇文章中所述刻录OTP中的引导加载程序。

最终我得到了：

- Micro waits for the bootlader
- 引导加载程序启动，复制报告器应用程序并触发软复位
- 广告框架Ko但消费好

I tried to see if there was any RF output but I need to be plugged into the RF analyzer to see it as the burst seems to be too short and not powerful enough to appear via the antenna. I'll try to add a connector on the board. As is said I'm sure the reporter application is running but it's like RF or advertising is broken.

What I found related to RF and avertising in the OTP is:

- Device unique ID (not burnt, advertising adress wrong?)
- 石英修剪（从芯片读取并烧伤，错误的频率？）

但是我不明白为什么会有差别eeing that I'm using the same reporter application as before burning the OTP which I believe is not reading any information from the OTP header anyway (let's hope I'm wrong here...).

希望它澄清整个问题。我会在星期一回答RF产出问题。

Thanks again for your help.

我检查了，根本没有RF输出。

评论以下行：

#define CFG_NVDS in da14580_config.h

in the reporter application was the answer. I guess I was indeed waking up on time but once in the app_adv_func function nothing was going on. Could you please further explain how this is related to the OTP though? I didn't burn this header but perhaps I should have?

Thanks for your help.

谢谢你的解释，这是有道理的！我不明白的最后一件事就是在使用JTAG时，应用程序正在运行的原因，因为CFG_NVDS仍然在时间定义？

问候

Well if you take the default reporter example and load it into a dev kit daughter board, it does work fine! CFG_NVDS is defined and OTP is not burnt.

If you can explain to me why this works then that's good enough :-).

Thanks