Olimex arm-usb-tiny verify failed

Comments

7 comments

  • Avatar
    Jon Elliott

    What project are you using?

    If you've not done so already, try the examples we ship in the AT91SAM7S-EK board support package.

    Regards,

    Jon Elliott

    0
    Comment actions Permalink
  • Avatar
    Thomas Strand

    The prototype is on an Olimex SAM7-P256, forgot to mention that, sorry.

    But I tried one example for the SAM7-P64 board (changed the target processor to AT91SAM7S256), with the exact same result (verify failed).

    Which loader file type should I choose? The example used Comms Channel Loader.

    0
    Comment actions Permalink
  • Avatar
    Jon Elliott

    You shouldn't need to modify anything - I've just done the following:

    1. Installed CrossWorks for ARM 2.0.3
    2. Clicked Tools > Package Manager, selected Olimex SAM7-P64 Board Support Package, right clicked and selected Install Selected Package followed by Next, Next, Finish to install the latest SAM7-P64 board support package and Atmel AT91SAM7 CPU support package.
    3. Clicked Tools > Show Installed Packages, selected Olimex SAM7-P64 Board Support Package followed by SAM7-P64 Samples Solution to load the examples project.
    4. Right clicked on the debugio project in the project explorer and selected Set as Active Project.
    5. Right clicked on Olimex ARM-USB-TINY in the targets window and selected Connect to connect the target interface.
    6. Clicked the Debug > Go menu option to download the program and start debugging.

    The program downloaded correctly with no problems and the debugger stopped at main. This was with an SAM7-P64 board, but I'd expect them to behave the same.

    Can you verify you're doing the same?

    Also, what is the exact error? Is the verify failing downloading the loader or downloading the program into FLASH?

    Regards,

    Jon Elliott

    0
    Comment actions Permalink
  • Avatar
    Thomas Strand

    I tried the procedure you described, and then I right-clicked in the output window >Copy All and pasted it here:

    Checking “debugio” in configuration “ARM Flash Debug”
    Preparing target for download
      Loading target script file AT91SAM7_Target.js
      Executing reset script FLASHReset()
    Downloading “Loader.elf” to Olimex ARM-USB-TINY
      Programming completed in 94 ms — 56,978 bytes/sec
        Programming 5.2 KB of addresses 00200000 — 002014eb
    Verifying completed in 94 ms — 10 bytes/sec
      Verifying completed in 94 ms — 56,978 bytes/sec
        Verifying 5.2 KB of addresses 00200000 — 002014eb
    Verify failed

     

    Smells like a hardware issue, but it still works in Yagarto, which is a bit strange. Yagarto (openOCD) is a lot slower though, maybe I should try slowing things down a bit.

    0
    Comment actions Permalink
  • Avatar
    Jon Elliott

    It is obvious I know, but check you are powering your board correctly. You'd not believe how often this turns out to be the cause of this sort of problem.

    One other thing, the speed of the JTAG clock frequency when targeting the AT91SAM7 is controlled by the TargetInterface.setMaximumJTAGFrequency() calls in the reset script not the JTAG clock divider. So if you want to slow the download you'll need to change the the TargetInterface.setMaximumJTAGFrequency(10000000); call to something smaller.

    Regards,

    Jon Elliott

     

    0
    Comment actions Permalink
  • Avatar
    Thomas Strand

    It works!

    I edited the file "AT91SAM7_Target.js", line 31. Changed the number from 10000000 to 4000000, and that did it.

    Thanks a lot for your assistance, that was really helpful. Now I'll soon be ready to move my project to Crossworks!

    0
    Comment actions Permalink
  • Avatar
    Thomas Strand

    Update:

    It works, but painfully slow.

    Uploading loader to ARM: ~56 kB/second

    Uploading application to ARM: ~1630 bytes/second

    Similar results when loading samples from the SAM7-P64 solution.

    Is the Olimex stuff known to be so slow? Should I get a new JTAG unit?

    0
    Comment actions Permalink

Please sign in to leave a comment.