ADuc7128 evaluation JTAG issue

When I reach step 6c in the ADuC7128 GetStarted Guide (REV0.1) and attempt to setup the provided mIDAS-Link emulator, I get the following errors as popup dialogs after selecting the mIDASLinkRDI.dll:

1) mIDAS-Link RDI Error: Firmware update requires reboot !

Please close this application

Disconnect J-Link

Reconnect J-Link

Restart the application

2) J-Link ARM Warning:

Supply voltage too high (3.3 Volt is maximum, Measured: 57.8 Volt). Operating at this voltage may damage the J-Link ARM hardware.  Please use the J-Link ARM 5V adapter offered by SEGGER.

3) mIDAS-Link RDI Error:

USB communication timed out: Writing 1 bytes, requesting 8 bytes, received 0 bytes ! Could not find a device on JTAG chain

4)mIDAS-Link RDI Error:

Could not read unit serial number!

5) AgdiRDI:

J-Link - RDI-Error 242: RDIError_SoftInitialiseError

I was counting on the emulator for my development effort and am stuck.  Please let me know what is going on - I haven't modified the eval board from its initial configuration.

  • 0
    •  Analog Employees 
    on Nov 18, 2010 2:52 PM

    Hi Paul,

    I suggest you download the latest version of MDK form Keil and install it.
    Installation of mIDAS-Link is slightly different, as Keil comes now along with

    a embedded driver for J-Link - please select this one for programming and debugging.

    Keil Download

  • Stephen,

    Answers to your questions:

    - I am referring to section 2.3 / 6c in the quick start guide, Rev0.1.

    - My mIDAS-LINK says version 7.0, date code 08-34.

    - I installed the KEIL tools from the quick start disc Rev0.1, and the KEIL tools version are:

    µVision3 V3.30h
    Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2006

    License Information:

    Tool Version Numbers:
    Toolchain Path:    BIN30\
    C Compiler:         ARMCC.Exe
    Assembler:          ARMASM.Exe
    Linker/Locator:     ARMLINK.Exe
    Librarian:          ARMAR.Exe
    Hex Converter:      FROMELF.Exe
    CPU DLL:            SARM.DLL       V1.52c
    Dialog DLL:         DARMAD.DLL       V1.06
    Target DLL:         BIN\AGDIRDI.DLL       V1.05a
    Dialog DLL:         TARMAD.DLL       V1.06

    - Yes, it really says 57.8V.

    - No, I have not used this mIDAS-Link before - we only have an eval kit, and it is our first kit for the ARM based ADuCs.

    - Yes, my serial number starts with 77 (full SN is 77000240)

    - We have tried the mIDAS-Link on two different computers, with two different engineers going through the quick start guide, with the same result. We do not have a second mIDAS-Link to try, if you were to send us a second one I would be happy to try it.

    I should point out that I have discovered I get the same error messages if the midas-link is not connected to the eval board.  Also, I can use the serial programming cable and successfully downloaded the blink.hex file to the eval board.

    I have not yet tried updating the drivers and re-installing.



  • 0
    •  Analog Employees 
    on Nov 26, 2010 4:06 PM

    This evaluation CD has been updated recently; the version you are using is old and contains a version of Keil uVision from 2006.

    It seems that there is an incompatibility between the software from 2006 and the mIDASLink hardware from 2008.

    I also see this error when I try the combination that you describe.

    Rest assured, there is no damage done to your hardware. Just use a newer version of Keil uVision either from the Keil website or from the updated Evaluation CD which you can download from the Analog Devices website.

  • Stephen, MMA, and Patrick,

    I am finally returning to this issue and think I am able to emulate properly.  I did have to update the J-Link driver from Segger (driver version, installed with the J-Link ARM V4.20o installation package from the Segger website), as well as the Keil ARM tools (see info below).

    Keil Info:

    µVision V4.03q
    Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. IL, An ARM(R) Company

    License Information:
    Patrick Cobler
    Vtech Engineering Corporation

    Tool Version Numbers:
    Toolchain:        RealView MDK-ARM  Version: 4.11
    Toolchain Path:    BIN40\
    C Compiler:         Armcc.Exe       V4.0.0.728 [Evaluation]
    Assembler:          Armasm.Exe       V4.0.0.728 [Evaluation]
    Linker/Locator:     ArmLink.Exe       V4.0.0.728 [Evaluation]
    Librarian:             ArmAr.Exe       V4.0.0.728 [Evaluation]
    Hex Converter:      FromElf.Exe       V4.0.0.728 [Evaluation]
    CPU DLL:               SARM.DLL       V4.11
    Dialog DLL:         DARMAD.DLL       V1.14
    Target DLL:             Segger\JLTAgdi.dll       V1.43
    Dialog DLL:         TARMAD.DLL       V1.13

    I can now poll the midas-link from the debug tab of the project options, as well as the aduc7128 on the eval board.  I was also able to configure the Utilities tab to program the flash using the midas-link, and that too appears to be working.

    However, when I follow the steps to create the sample project from the getting started guide using the pot.c demo file and start a debug session, the emulator expects the program counter to be at 0x80000 but it actually starts at 0.  I receive the following in the build output window:

    ***JLink Warning: PC of target system has unexpected value of 0x00080254 after reset.

    At this point, the PC in the register window appears to have reset to 0 (mirrored program memory location?) and be running the code from pot.c properly, but the emulator expects the PC to be reset to 0x80000.

    I have found through experimentation that the linker tap starts off with the following switches:

    --cpu ARM7TDMI *.o --ro-base 0x00080000 --entry 0x00080000 --rw-base 0x00040000 --strict --autoat --summary_stderr --info summarysizes --map --xref --callgraph --symbols
    --info sizes --info totals --info unused --info veneers

    and if I check the "use memory layout from target dialog" setting, the switches change to the following:

    --cpu ARM7TDMI *.o --strict --scatter "test2.sct"
    --autoat --summary_stderr --info summarysizes --map --xref --callgraph --symbols

    where "test2" is my project file name, and I assume test2.sct is an automatically generated file.

    At this point, unchecking the 'use memory layout from target dialog" setting does not revert the tool switches, and the emulator and PC register appear to be in sync.  I do still get the ***JLink Warning message in the build output window.

    What exactly is going on when I check the "use memory layout from target dialog" option, and why does it not appear to be reversible?



  • 0
    •  Analog Employees 
    on Mar 2, 2011 9:50 AM

    Hi Paul,

    What exactly is going on when I check the "use memory layout from target dialog" option, and why does it not appear to be reversible?

    I tried this with the latest version of Keil uVision4 from the Keil Website (v414) and also see what you are seeing.

    However, you should take this point up with Keil support as that is their product, I am not sure what the expected operation is here but suspect – as you do – that there is some issue here.

    ***JLink Warning: PC of target system has unexpected value of 0x00080254 after reset.

    This might be related to the reset type the tool is performing.

    I interpret this particular error message as “I performed a reset but the part was not at the reset vector after it”.

    What Reset Strategy have you selected, the recommended one is “Software, for Analog Device ADuC7xxx MCUs”.