Hello everyone,
I'm currently working on a project involving a custom board based on the DA16600 chip, and I've encountered an issue while trying to load an image onto it. I've attached a screenshot below for reference.
Additionally, I've included the circuit diagram of my custom board to provide more context.
The problem arises when I attempt to load the image onto the board. Despite following the usual procedures, I'm facing difficulties in getting it to work properly. I've double-checked the connections and configurations, but the issue persists.
I would greatly appreciate any insights or suggestions on what might be causing this problem and how I can resolve it. Has anyone else encountered similar challenges with the DA16600 chip or similar custom boards? Any advice or guidance would be immensely helpful.
Thank you in advance for your assistance!
Hi There,Thank you for posting your question online.
Trainyinfi said:I'm currently working on a project involving a custom board based on the DA16600 chip, and I've encountered an issue while trying to load an image onto it. I've attached a screenshot below for reference.
I was not able to replicate this issue with the DA16600 EVK v9.0I suppose that COM17 is related to the UART0 (Debug Console Interface) which is needed to download the FW. You should connect UART0 (Pin15,16) to a USB to Serial module in order to connect and download your images.Did the DA16600MOD have any Image flashed from before? If yes, did that image have DPM enabled by default?One reason why the DA16600MOD is not responding could be the fact that it is in Sleep mode. Please try to access UART0 and see if there is any FW loaded and make sure you disable DPM, by issuing "dpm off".If you are still facing issues with the Multi-Download Tool, we would need you to probe a logic analyzer on the UART0 lines so we can see the exchanges between the Muti-Download Tool and the DA16600MOD.
Trainyinfi said:Additionally, I've included the circuit diagram of my custom board to provide more context.
Overall I do not see anything that could be related with the issue you have reported.However, please check the comments below:
- VDD_IO1/2: No need for bypass capacitor- RTC_PWR_KEY: Recommended to be controlled by the Host MCU. I do not see any Host MCU on your schematic.- RTC_WAKE_UP2: C54 can be removed. Can be connected directly to GND if not in use- GPIOA8, P0_5: BT- WiFi COEX: WiFi_ACT, need to connect externally- GPIOA9, P0_6: BT- WiFi COEX: BT_ACT need to connect externally (internally connected to SPDT)- GPIOA10, P0_7: BT- WIFi COEX: BT_PRIO need to connect externally, GPIOA_10 can be assigned to BT_ACT when 1-pin COEX.- GPIOA6~A7: Need to disable WPS/factory_reset functions on SDK or add pull-up resistors to remove leakage current- GPIOA11: is set as interrupt for MCU wake-up by default when AT-CMD function is enabled. Not connected on your design.
Best Regards,OV_Renesas
- GPIOA10, P0_7: BT- WIFi COEX: BT_PRIO need to connect externally, GPIOA_10 can be assigned to BT_ACT when 1-pin COEXHow can I do 1-pin COEX in SDK? With that is it still necessary to connect A8 and A9 as per your recommendation?
Hi There,Thank you for the reply.
kashyap.gada said:How can I do 1-pin COEX in SDK?
Please refer on UM-WI-046, on section 16.13 Bluetooth_LE_Coexistence, page: 300
kashyap.gada said:With that is it still necessary to connect A8 and A9 as per your recommendation?
Please refer on the same document, same page:If you use 1-Pin Coexistence, then you do not need the GPIOA8 and GPIOA9 connected.Best Regards,OV_Renesas
As per the schematic shared in this post, after setting 1-pin Coex mode and being able to write the firmware in the dialog DA16600 part, I am facing the original issue of wdt timeout even after applying patches mentioned in https://community.renesas.com/wireles-connectivity/f/wi-fi/32935/watchdog-timer-expired-in-da16600 and https://community.renesas.com/wireles-connectivity/f/wi-fi/32933/we-flash-img-file-in-da16600-module-once-flashing-completed-but-it-s-getting-error-watch-dog-timer-its-come-lopping-same-error-getting-i-attach-error-log-also-i-need-solution-asap-i-need-full-information-with-documentation-al/118266?focus=trueI have not made any other changes which you have mentioned. So those will have to be done before we can come to some conclusion?
Hi There,Thank you for the reply.I am not aware if you are a colleague of Trainyinfy, which created this thread. So I am a bit confused on your issue. You have the exact same schematic as shared in the original post? You have applied the WatchDog Patch on SDK v3.2.8.1, compiled and downloaded which project? Please create a new thread with all the information gathered there. Schematic, SDK version, UART0 logs, etc.Best Regards,OV_Renesas
We are colleagues. I have applied this patch/cfs-file/__key/communityserver-discussions-components-files/295/DA16600_5F00_ble_5F00_sw_5F00_reset_5F00_fix.patchand
/cfs-file/__key/communityserver-discussions-components-files/295/DA16600_5F00_watchdog_5F00_repeated_5F00_log_5F00_fix.patchfrom this post on the forum. https://community.renesas.com/wireles-connectivity/f/wi-fi/32933/we-flash-img-file-in-da16600-module-once-flashing-completed-but-it-s-getting-error-watch-dog-timer-its-come-lopping-same-error-getting-i-attach-error-log-also-i-need-solution-asap-i-need-full-information-with-documentation-al/118266?focus=true
Also image which was given on that post has been used which gave the same issue. I will share the output if required.
On the SDK I have enabled Coex 1 pin as suggested by you. Results same. WDT reset.
Lets not create another thread for this issue.
Regards
Hi There,Thank you for the reply and the clarifications.Could you please share the Images you have flashed so I can try to replicate the issue on my side?Could you please also share the full schematic and layout files so I could submit them for a review?With the Watchdog patch I provided on the other thread, I cannot reproduce this issue with DA16600 EVK v9.0.Best Regards,OV_Renesas
Please share your email id so I could send those files to you.
Hi There,Thank you for the reply.Please create a private ticket for this inquiry. Dashboard | Renesas Customer HubYou will have to login and type on Submit a Ticket!Best Regards,OV_Renesas