Lpc2000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I noticed that quite a lot of people are working on JTAG tools
for debugging on the LPC, but (as far as I know) there is still
no-one that has written an open-source gdb stub for the LPC family.
On sourceforge, there are a couple of gdb JTAG projects for arm
processors, but none seem to support the ARM7TDMI-S.

Existing closed-source software like OCDRemote and OCDCommandor
does not work well with my olimex wiggler clone and there's nothing
I can do to fix it.

Myself, I played around a bit with the sources from
http://gdb-jtag-arm.sourceforge.net/ ,
probably re-inventing the wheel but it was fun nevertheless.
So far, my progress is:
* updated parallel port access code to use libieee1284. This makes
the tool portable between windows/cygwin and linux.
* made it work with a cheap wiggler clone from olimex.
* can read JTAG idcode
* can read and write ICE registers
* can stop the processor
* read the CPU registers (not reliably yet and in wrong order)

Can we perhaps combine forces and write an open-source gdb stub?

Kind regards,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDoejJETD6mlrWxPURAuwIAJ4i09WzZk4ZdnqoCOsCET8u4NXl9gCcDKjo
wZ+5axE3KS07+G+BQhzpUlM=
=5uz1
-----END PGP SIGNATURE-----

I'm currently working on such debugger (10% done).

Features:
- USB connection / next release on Ethernet (with TCP/IP server)
- fully compatible with gdb remote protocol (no server like ocdremote
needed)
- SW/HW breakpoints
- Full EmbeddedICE/JTAG debugging or with LPC integrated Realmonitor

Schematics and firmware (PIC18/ezUSB) will be available on my website.

I'm waiting my DIL LPC2106 for the prototype.

> Hi all,
> 
> I noticed that quite a lot of people are working on JTAG tools
> for debugging on the LPC, but (as far as I know) there is still
> no-one that has written an open-source gdb stub for the LPC family.
> On sourceforge, there are a couple of gdb JTAG projects for arm
> processors, but none seem to support the ARM7TDMI-S.
> 
> Existing closed-source software like OCDRemote and OCDCommandor
> does not work well with my olimex wiggler clone and there's nothing
> I can do to fix it.
> 
> Myself, I played around a bit with the sources from
> http://gdb-jtag-arm.sourceforge.net/ ,
> probably re-inventing the wheel but it was fun nevertheless.
> So far, my progress is:
> * updated parallel port access code to use libieee1284. This makes
> the tool portable between windows/cygwin and linux.
> * made it work with a cheap wiggler clone from olimex.
> * can read JTAG idcode
> * can read and write ICE registers
> * can stop the processor
> * read the CPU registers (not reliably yet and in wrong order)
> 
> Can we perhaps combine forces and write an open-source gdb stub?

Hi Bertrik,

I am wondering if you have seen this:
http://openwince.sourceforge.net/jtag/

It appears to support wiggler.
Maybe all that is needed is some tweaks for ARM7.
Some people have used this on x-scale.

   -- Doug



Bertrik Sikken wrote:

> probably re-inventing the wheel but it was fun nevertheless.
> So far, my progress is:
> * updated parallel port access code to use libieee1284. This makes
> the tool portable between windows/cygwin and linux.
> * made it work with a cheap wiggler clone from olimex.
> * can read JTAG idcode
> * can read and write ICE registers
> * can stop the processor
> * read the CPU registers (not reliably yet and in wrong order)
> 
> Can we perhaps combine forces and write an open-source gdb stub?
> 
> Kind regards,
> Bertrik
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFDoejJETD6mlrWxPURAuwIAJ4i09WzZk4ZdnqoCOsCET8u4NXl9gCcDKjo
> wZ+5axE3KS07+G+BQhzpUlM=
> =5uz1
> -----END PGP SIGNATURE-----
> 
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
> 
>

Bertrik Sikken wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi all,
>
>I noticed that quite a lot of people are working on JTAG tools
>for debugging on the LPC, but (as far as I know) there is still
>no-one that has written an open-source gdb stub for the LPC family.
>  
>
Well, there is openOCD from Dominic Rath. He created an "On-Chip Debug 
solution for embedded target systems based on the ARM7 and ARM9 family".
His Diploma Thesis is a great piece of documentation with lots of 
information on JTAG and ARM7/9 debugging.
The code even has support for the FT2232 from FTDI and schematics for 
the hardware are given in the thesis.

Look at: http://openocd.berlios.de/web/ It's worth it!

Rob

Hello Doug,

the openwince jtag tools use the boundary scan chain around all device pins. 
This gives them access to the data and address bus, and allows them to 
read/write the flash. This doesn't include any debugging support. LPC doesn't 
have a boundary scan chain at all (none that I've found?).

Regards,

Dominic

On Friday 16 December 2005 03:56, Doug Sutherland wrote:
> Hi Bertrik,
>
> I am wondering if you have seen this:
> http://openwince.sourceforge.net/jtag/
>
> It appears to support wiggler.
> Maybe all that is needed is some tweaks for ARM7.
> Some people have used this on x-scale.
>
>    -- Doug
>

Hi Dominic,

Thanks for the info, and also thanks for sharing your work. I suppose
there are are things that most people are looking for:

Ability to program internal flash
Ability to program external flash
Debugging support, especially GDB
Boundary scan to test new boards

Some of these may not be applicable to a typical LPC2000 application,
but I find myself requiring other vendors' ARM chips also. In particular
I'm interested in STR7 for peripheral support (4 UARTS), Cirrus Logic
and Sharp for audio and MMU support (ARM720T), and also basically the
same on ARM920T (looks like Atmel might be good here with AT91RM9200).

I haven't had a chance to try your code yet but I will try it in the
next few weeks.

   -- Doug


Dominic Rath wrote:

> the openwince jtag tools use the boundary scan chain around all device pins. 
> This gives them access to the data and address bus, and allows them to 
> read/write the flash. This doesn't include any debugging support. LPC doesn't 
> have a boundary scan chain at all (none that I've found?).

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rob Jansen wrote:
> Bertrik Sikken wrote:
> 
>>I noticed that quite a lot of people are working on JTAG tools
>>for debugging on the LPC, but (as far as I know) there is still
>>no-one that has written an open-source gdb stub for the LPC family.
>> 
>>
> Well, there is openOCD from Dominic Rath. He created an "On-Chip Debug
> solution for embedded target systems based on the ARM7 and ARM9 family".
> His Diploma Thesis is a great piece of documentation with lots of
> information on JTAG and ARM7/9 debugging.
> The code even has support for the FT2232 from FTDI and schematics for
> the hardware are given in the thesis.
> 
> Look at: http://openocd.berlios.de/web/ It's worth it!

Yes, I saw it.
It does not support ARM7TDMI-S yet, only ARM7TDMI, right?

What would it take to add support for the ARM7TDMI-S / LPC family
to openocd?

Which existing project do you guys see as the best candidate for
extension with ARM7TDMI-S support?

I won't mind helping with writing the code or testing it.
So far I see the following differences to be handled:
* debug control ICE register (different bits)
* DCC control ICE register (different length)
* data bus scan chain size

Kind regards,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDoyLsETD6mlrWxPURAprIAKC79x0NmsWGUf3tsR2RVrAALYeC5QCghvFp
STKDtSOSbT84m6qCPJhqUIk=
=xEqg
-----END PGP SIGNATURE-----

Bertrik Sikken wrote:
> It does not support ARM7TDMI-S yet, only ARM7TDMI, right?
> What would it take to add support for the ARM7TDMI-S / LPC family
> to openocd?

The differences between ARM7TDMI and ARM7TDMI-S are listed in
Appendix B of the ARM7TDMI-S technical manual.

http://www.arm.com/support/faqip/3686.html

Perhaps that info would be useful.

    -- Doug

Hello,

>
> Yes, I saw it.
> It does not support ARM7TDMI-S yet, only ARM7TDMI, right?

Yes, the code available at berlios is from july, and doesn't support -S cores. 
Besides, it has some nasty bugs, so I decided to rewrite most of it.

> What would it take to add support for the ARM7TDMI-S / LPC family
> to openocd?

My new code I'm working on supports ARM7TDMI-S, specifically LPCs. I have one 
LPC2294 here to test with, which is why I've subscribed to this list.

> Which existing project do you guys see as the best candidate for
> extension with ARM7TDMI-S support?

I wont comment on this one ;)

> I won't mind helping with writing the code or testing it.
> So far I see the following differences to be handled:
> * debug control ICE register (different bits)
> * DCC control ICE register (different length)
> * data bus scan chain size

The differences are actually very subtle, and not much of a problem, if the 
code is written with -S cores in mind.

If you want a snapshot of my current development tree mail me, I can give you 
access to my private CVS or a tarball. I didn't release this new code yet as 
it's not really usable at the moment.

>
> Kind regards,
> Bertrik
>

Best regards,

Dominic

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Doug Sutherland wrote:
> Bertrik Sikken wrote:
>> It does not support ARM7TDMI-S yet, only ARM7TDMI, right?
>> What would it take to add support for the ARM7TDMI-S / LPC family
>> to openocd?
> 
> The differences between ARM7TDMI and ARM7TDMI-S are listed in
> Appendix B of the ARM7TDMI-S technical manual.
> 
> http://www.arm.com/support/faqip/3686.html
> 
> Perhaps that info would be useful.

It appears to be incomplete. None of the differences I've seen
so far is even mentioned in appendix B.

Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDoypdETD6mlrWxPURAvc3AJ9oDLyuPuf36Oug70c3fxbtOZbk5QCfTF+8
/cV7wEzU6Jsp+o7SX7zGjvs=
=O/+c
-----END PGP SIGNATURE-----

Bertrik Sikken wrote:

> It appears to be incomplete. None of the differences I've seen
>
>so far is even mentioned in appendix B.
>  
>
The differences are not as big as you describe.
I used an ARM7 TDMI debugger pod on the TDMI-S, it works but sometimes 
it just hangs.
The biggest difference is the removal of the scan chain around the core 
(which is not used by the debugger) and the addition of the Return Clock.
Adding the return clock is an easy task - but you'll have to add a bit 
to the I/O configuration.

I think the OpenOCD is a good start for a debugger. It's well 
documented, very recent and Dominic is still working on it (most other 
projects are old zombies wadering around the internet ...)

Regards,

    Rob

--- In lpc2000@yahoogroups.com, Doug Sutherland <doug@p...> wrote:

> I am wondering if you have seen this:
> http://openwince.sourceforge.net/jtag/

This one is also interesting:

http://jtager.sourceforge.net/

Yes it is interesting, but for Arm9 only.

Cheers
Michael

>From: "Eric Engler" <englere.geo@...>
>Reply-To: lpc2000@yahoogroups.com
>To: lpc2000@yahoogroups.com
>Subject: [lpc2000] Re: Combining forces on open-source gdb stub
>Date: Sat, 17 Dec 2005 02:21:51 -0000
>
>--- In lpc2000@yahoogroups.com, Doug Sutherland <doug@p...> wrote:
>
> > I am wondering if you have seen this:
> > http://openwince.sourceforge.net/jtag/
>
>This one is also interesting:
>
>http://jtager.sourceforge.net/
>
>
>

Hello forum,

 

                             Can someone tell me whether µVision3 from Keil
(ARM) runs on AMD X86-64 architecture ?

 

Thanks,

 

Michel

 



[Non-text portions of this message have been removed]

I expect that the 64 bit windows runs all Win32 applications, but you 
probably need a 64 bit driver for the ulink jtag adaptor which I have 
not seen yet. I don't have an AMD64 system, so I cannot tell you anymore.

Richard.


Gazelle wrote:

> Hello forum,
>
>
>
>                              Can someone tell me whether \ufffdVision3 from 
> Keil
> (ARM) runs on AMD X86-64 architecture ?
>
>
>
> Thanks,
>
>
>
> Michel
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
>     *  Visit your group "lpc2000
>       <http://groups.yahoo.com/group/lpc2000>" on the web.
>        
>     *  To unsubscribe from this group, send an email to:
>        lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     *  Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>

--- In lpc2000@yahoogroups.com, "Michael Rubitschka" <rubitschka@h...>
wrote:
>
> Yes it is interesting, but for Arm9 only.

I haven't looked into this myself, but the manual says it supports
both Arm7 and ARM9, and the history says that ARM7TDMI was supported
first, before Arm9.

http://jtager.sourceforge.net/

I am not implying that this is the best starting point, but only that
there may be some value in looking at it.

Dominic Rath's work seems like the best starting point, and I agree
with the reasons posted by someone here recently (can't remember who):
best documented, and the only work of relevance that is still
undergoing development. Either one of these reasons alone would make
it a no-brainer.

Eric

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

Dominic Rath wrote:
>> I won't mind helping with writing the code or testing it. So far I
>> see the following differences to be handled: * debug control ICE
>> register (different bits) * DCC control ICE register (different
>> length) * data bus scan chain size
> 
> The differences are actually very subtle, and not much of a problem,
> if the code is written with -S cores in mind.
> 
> If you want a snapshot of my current development tree mail me, I can 
> give you access to my private CVS or a tarball. I didn't release this
> new code yet as it's not really usable at the moment.

Dominic released a preview version of the openocd package
(check out the svn archive for the very latest version)!

I created a wiki page with some basic instructions on how to get
started with it for anyone interested:
http://wiki.sikken.nl/index.php?title=ArmDebug

All the best,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDqarZETD6mlrWxPURAgVZAKC831cPdX/DuYEqMhHzbHk4kfbz1wCeNH/n
pgF4zzBQrLrrJ/euiNsgo5c=
=4fuM
-----END PGP SIGNATURE-----