Encountering Problems Loading Image on DA16600 Custom Board

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!

Top Replies

Parents
  • Hi There,

    Thank you for posting your question online.

    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.0
    I 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.


    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 COEX

    How can I do 1-pin COEX in SDK? With that is it still necessary to connect A8 and A9 as per your recommendation?

Reply Children