Post Go back to editing

How do I resolve “Error: Error connecting DP: cannot read IDR”?

Category: Software
Product Number: MAXREFDES106#
Software Version: MAXREFDES106 Host Firmware V1.0.0

hello?

I purchased MAXREFDES106# (Health Sensor Platform 4.0) and am following the User Guide (MAXREFDES106_HSP4.0_User_Guide_Rev0_9).

However I cannot resolve the error that occurred during the first step, “Updating the MAX32666 HOST MCU Firmware.”


I proceeded as follows according to the procedure.

1. I connected the Micro-USB to the MAXDAP-TYPE-C programmer and connected the USB end of the cable to the PC.
And I connected MAXREFDES106# to the USB-C port of the MAXDAP-TYPE-C programmer.

2. I pressed the MAXREFDES106# button for more than 5 seconds while the MAXDAP-TYPE-C Programmer, MAXREFDES106#, and PC were connected.
This will turn the blue LED on MAXREFDES106# off and then on again.

3. I confirmed that there is an openocd folder and a load_fw.bat file in the MAXREFDES106-MAX32666-Host-FW-Package-1.0.0\MRD106_Update folder.
And I placed MDR106_HOST Firmware (MRD106_HOST_1_0_0.bin) in the MRD106_Update folder.

4. I opened the command prompt in this folder.

5. I typed load_fw.bat MRD106_HOST_1_0_0.bin in the command prompt.
>> D:\wearable\MRD106_Update>load_fw.bat MRD106_HOST_1_0_0.bin

Up to this point, I followed the procedure in the User Guide and proceeded without any problems.

However, the following error occurs:

Does anyone have any ideas?

Thanks

  • Were you able to resolve this? I am having the same issue.

  • I haven't been able to resolve the issue with the error.

    I gave up on “Updating the MAX32666 HOST MCU Firmware.” from “MAXREFDES106_HSP4.0_User_Guide_Rev0_9”.

    And I did "Updating the MAX32674C Algo Hub Microcontroller Coprocessor Firmware" and
    "Installing the MAXREFDES106# Health Sensor Platform PC GUI".

    Then, I was able to run MAXREFDES106Gui and then measure the ECG using MAXREFDES106.

    But I don't know if this is completely problem-free.

  • Although I have a custom board with the Max32666 part, I was able (yesterday) to resolve this issue by preventing VREGO_A from powering up VDDDIO/H before the microcontroller's VCOREA/B is up.  I am only able to do this because I have a jumper between VREGO_A/B/C/D to VDDDIO/H, VCORE_B/A and can individually control the order in which the I/O and core power turns on.  I just sent a support ticket to see if there is anyway to control the order in which the VREGO_A/B/C/D comes up since this is the output from the internal SIMO and the VREGO registers are not useful.  Doing this seems to consistently work for me so it appears to be a power sequencing issue.  

    If you are able to probe, see what order these voltage rails come up.  It appears the VCOREA/B (power to Microcontroller's Core)  just needs to come up before VDDIO/H's (power to Microcontroller's I/O). (Note: I also played around with the processor reset and it did not help with this error.)

    Good luck!