Download firmware to ADuCM355

Hi Analog,

I have just received a PCB I have designed with the ADuCM355 on it. I am attempting to flash the chip for the first time, using the mIDAS-Link that was provided with the EVAL-ADuCM355 kit. 

However, when attempting to download the program, the mIDAS-Link flashes green/red (orange-ish) and IAR prints "Failed to get CPU status after 4 retries. Retry?

The debug log is this:

Thu Apr 25, 2019 19:43:36: IAR Embedded Workbench 8.22.2 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0\arm\bin\armproc.dll)
Thu Apr 25, 2019 19:43:38: JLINK command: ProjectFile = M355_Biased_EIS_Debug.jlink, return = 0
Thu Apr 25, 2019 19:43:38: Device "ADUCM355" selected.
Thu Apr 25, 2019 19:43:38: Selecting SWD as current target interface.
Thu Apr 25, 2019 19:43:38: JTAG speed is initially set to: 1000 kHz
Thu Apr 25, 2019 19:43:38: Hardware reset with strategy 7 was performed
Thu Apr 25, 2019 19:43:38: Initial reset was performed
Thu Apr 25, 2019 19:44:49: IAR Embedded Workbench 8.22.2 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0\arm\bin\armproc.dll)

While this issue could be hardware related, I wanted to know if there is anything I need to be aware of when downloading to a clean ADuCM355 for the first time, or if you know what the color/flashing error code on the mIDAS-Link means. I've looked at p. 111 in the JLink Manual but it does not cover the mIDAS-Link LED indicator.

Thanks!

Andreas

Parents
  • Hi Andy,

    I suggest you try to mass erase the user flash as described in the last section of the user guide manual:

    https://www.analog.com/media/en/technical-documentation/user-guides/EVAL-ADuCM355QSPZ-UG-1308.pdf

    if this fails, you likely have a hardware issue on your board as you suggest above.

    Another good tool is the JLINK Commander tool provided by Segger - this is likely installed on your PC - see where to find it in the attached picture.

    Exit IAR debug mode for this and power cycle your board before running it.

    The commands are simple:

    "connect"

    "SWD"

    "ADuCM355"

    default SWD speed

    If the JLINK detects a Cortex-M3 core - this is good - if it doesn't, you will need to perform basic checks on the part to ensure it is properly powered and the reset pin is controlled correctly.

    Regards,

    Mikel

Reply
  • Hi Andy,

    I suggest you try to mass erase the user flash as described in the last section of the user guide manual:

    https://www.analog.com/media/en/technical-documentation/user-guides/EVAL-ADuCM355QSPZ-UG-1308.pdf

    if this fails, you likely have a hardware issue on your board as you suggest above.

    Another good tool is the JLINK Commander tool provided by Segger - this is likely installed on your PC - see where to find it in the attached picture.

    Exit IAR debug mode for this and power cycle your board before running it.

    The commands are simple:

    "connect"

    "SWD"

    "ADuCM355"

    default SWD speed

    If the JLINK detects a Cortex-M3 core - this is good - if it doesn't, you will need to perform basic checks on the part to ensure it is properly powered and the reset pin is controlled correctly.

    Regards,

    Mikel

Children