Hi,
我已经成功地部署需求方固件to DA14580. My iOS app can successfully connect to it (I can discover the services and three characteristics), but I do not see any change in DA14580 P0.3 (UART RTS). During development, I could see a LOW signal every ~100ms before connection and every ~25ms after connection. Have you guys seen anything similar to this behavior?
A few things that I think may be the cause:
1. In my project, I have #undef CFG_BOOT_FROM_OTP instead of #define CFG_BOOT_FROM_OTP.
2. I only burn OTP image and OTP Header. I did not burn NVDS.
3. My DMA length was not set to 001FC0. It was set to 000000
I can understand there's something I did wrong when burning OTP, but what I don't understand is how come part of the project is still functional (advertising, connection, etc).
I can upload my OTP image and OTP header content upon request, but it's very similar to what's described in:
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-da...
If you also have no clue, I will try it on another board by copying all the steps described in the post mentioned. But I'd really appreciate it if you could provide the hex files for OTP image and OTP header. It will really save me a lot of time. Thanks in advance for your help!
Regards,
Michael
Hi chanmi168,
I am not aware of such an issue and i dont see any possible reasons for causing that just by burning the image in the OTP, if you haven't changed the DSPS example at all. Also i suppose that if you are using sleep and have enabled flow control and you aren't able to see the RTS toggling i dont see how the device is operating. Regarding providing .hex files, just take the DSPS source and compile it and regarding the OTP header just burn the application flags in order to boot from the OTP, i dont think that any of the things that you ve mentioned above will cause the RTS not to be functional.
Thanks MT_dialog