ARM-USB-OCD with Rowley

After mistakenly buying the ARM-USB-OCD to use with Rowley I was quite disappointed to find out it only worked with the open source platforms.

I found out though that it will be supported in Rowley crossworks V1.7. V1.x users can get the V1.7beta from their web site.

I’m in the process of testing it out right now. For those who try make sure you set your target settings on the jtag clock to 3X otherwise it won’t recognize the target.

I’ve just bought the new Rowley USB CrossConnect for ARM. It works very well.

Leon

Yes but it is $199 US and the ARM-USB-OCD is $89 and also powers the target.

OK after a lot of futzing around this is what it takes to run the ARM=USB-OCD with Rowley (V1.7 beta). I’ve tested this on the OLIMEX P2138 and H2138 boards so far

JTAG Target Setting:

YES (Default)

JTAG Clock divider >= 4 (Default = 1)

nTRST = NO (Default = YES).

Once I got these I can download and debug. JTAG = 3 will allow target identification but download/verify fails. nTRST for some reason defaults to YES. No is reuqired

Hi,

I’m also playing with Rowley and ARM-USB-OCD. I tried your settings, and I still get “Loader Verify failed

Any thoughts?

~Kam (^8*

Kam,

What board are you using?

Try increasing the JTAG clock divider even more. I needed 4 before mine would work. Try 5 or 6?

Are you sure nTRST = NO? The default setting was YES. (I’d try both ways.)

I’m using the Olimex’s at91sam7s256 board.

I tried changing the value from 5 ~ 20. It worked ONCE, but that was it. Same error, “Loader Verify Failed”

Grumpf!

~Kam (^8*

Hunh, that’s weird.

Have you gotten the board to work with something else such as a wiggler? (trying to eliminate a bad board as the culprit). It is encouraging if you got it to work once as you said? It means it is probably possible.

In addition to the JTAG clock, try turning off the IDENTIFY target.

I haven’t used that board or any of ATMELs ARMs but a quick glance at the olimex schematic indicates the JTAG interface is slightly different. The ATMEL doesn’t have an RTCK or TRST pin. So on the interface the RTCK is shorted (through a 0 ohm resister) to TCLK and TRST is just pulled up.

I don’t believe the RTCK matters, but I think the lack of TRST might mean that you might need to manually reset the CPU since the JTAG interface can’t do it for you. So try connecting to the target. Manually reset the target. Then try the download.

It might just be that Rowley doesn’t have the Olimex USB Jtag working with ATmel processors. You might put in a ticket with Rowley. I’m sure can tell you if they’ve been succesful with the Olimex USB and ATMEL board combo.

Good luck,

Steve

Hi Everybody!

Just have a Question to Crossworks 1.7 beta …

Is this Version “public” available or have I to own a real Crossworks Licence ? I’m actually trying the Evulation of Crossworks 1.6 and have also a ARM-USB- OCD from Olimex right there.

I’ve wrote to Rowley about support for such devices and the Version 1.7 of Crossworks, but they seems to be not responding within last Days :frowning:

thanks in advance

I think that whatever license you have will work the same with any 1.x version.

So: if you have an evaluation license (or a perminate license) for 1.6 version, it should work for 1.7beta as well.

I believe that the reason that 1.7 is still a beta is that there are performance issues with the ARM-USB-OCD (it is really slow downloading) with 1.7 and they are reluctant to claim they support it.

In general I use the ARM-USB-OCD with 1.7 sometimes as well as the wiggler clone. The wiggler however is about an order of magnitude faster.

first, thank you for the reply.

But the Problem I’m encounter is, there is no download-link within the rowley-page at all for Crossworks 1.7 Beta. Or did I overseen them? That was the Reason I asked if it’s some kind of “public”.

Because if I have to enter a Activation Key on installing this Version, it should be ok to get the 1.7beta.

Can you eventually provide me with such a downloadlink ?

Did you get the link I sent you via PM?

Hello!

It’s a pretty old thread, but does someone have a solution? I have the same problem with the Olimex SAM9260-EK using Crossworks 1.7. Everything works fine with a LPC2136, but with the ARM9 I either get a “debug handler verify error” or the uploaded data is corrupted (“Verifier has found errors”. All bytes on offsets +0 +4 +8… are 0xff). I tried several values for the JTAG clock divider but nothing seems to help :frowning:

Thanks

Th.