Lpc2000

Been asked to ask a question
(by some guys I've done some work for in the past)

Does either keil u-link or IAR Jlink
work with insight or gdb for debugging ?

Especially on linux or osx or bsd?

Also Leon did you ever try that Chameleon pod
that Amontec offered you ?

Any comments ?

Has anyone built a homemade usb jtag yet ?

The wonderful disappearing parallel port
strikes again.

Thanks

Alex Gibson

----- Original Message ----- 

From: "Alex Gibson" <alxx@...>
To: <lpc2100@yahoogroups.com>
Sent: Sunday, February 15, 2004 12:56 PM
Subject: [lpc2100] jtag debuggers


> Been asked to ask a question
> (by some guys I've done some work for in the past)
>
> Does either keil u-link or IAR Jlink
> work with insight or gdb for debugging ?
>
> Especially on linux or osx or bsd?
>
> Also Leon did you ever try that Chameleon pod
> that Amontec offered you ?

I've got it, but it won't work with WinME, the driver is only for
Win2000/XP. I'll have to wait until I can can get the use of a suitable
machine. They did tell me that they someone has tried it with the LPC2100
and it worked OK for him.


>
> Any comments ?
>
> Has anyone built a homemade usb jtag yet ?

It should be quite easy with a suitable USB controller like the Cygnal or
Cypress chips. The Cypress AN2131SC is easy to get hold of (RS stocks them,
about 8 GBP) so I might design one: the hardware is quite trivial, software
probably somewhat less so.

Leon
--
Leon Heller, G1HSM
Email: aqzf13@...
My low-cost Philips LPC210x ARM development system:
http://www.geocities.com/leon_heller/lpc2104.html

I've had the Chameleon JTAG pod working with the Nohau TESTER board in
both RAVEN and WIGGLER modes.  I'm runnig XP on a fast notebook, so
the speed setting had to be set to 2 or 3 to slow things down a bit.
Also, just this morning got the RAVEN mode talking with my own LPC2214
board.  So far "Hello World" is operational.

Regards
-Bill Knight
R O SoftWare

what are the best ways for avoiding  the buffer overflow and intertask

interference in coperative scheduler........

thanx,

pc2129



---------------------------------
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online

> what are the best ways for avoiding  the buffer overflow and intertask
> interference in coperative scheduler........

Generally speaking, any problem can be easily avoided if application is
designed more carefully.

Using intertask communication by calling Operating System functions is the
best way to avoid any problem with intertask interference. Also, if you have
shared resources (e.g. COM port) you should use some semaphore that tells
you if resource is already taken by some of tasks. Careful assignement of
priorities to tasks is also good way of avoiding problems. Having
cooperative scheduling yields even more carefull application design since
even tasks with higher priority will have to wait some low priority task to
release CPU. So, it's all about application design.

About your cooperative scheduler... is it some standard piece of software or
something that you wrote? I'm asking this because I'm working on my own
version of embedded ultra-low-footprint (approx. 1.5kB) cooperative OS for
LPC MCU's so we might share ideas on this? Thing is that I have this stupid
neural network that I'm supposed to run with many other things in parallel
and it takes up to 10MIPS for neuro code so I really need to use each
micro-second of CPU time. That's where OS fits as perfect solution.

Regards,
Igor