[Milkymist-devel] about LM32 onchip debug

[Sébastien Bourdeauducq]

Hi,

On Wednesday 16 September 2009 01:05:34 Jose Ignacio Villar wrote:
> I have a doubt, if there is no debug interface, how do you develope
> software? Is there any other way than "try and error" until the cause of
>  the bugs are found?

Not really. That's why a proper debugger would be appreciable :)
 
> I've been following milkymist devel mailing list for a while, and I have
> seen that Takeshi and you were able to run ucLinux and some busybox tools.
> Did you make whole the ucLinux port?

It is based on Theobroma's version that we debugged, and we added the missing 
drivers.

> I was very surprised because it seems
> that theobroma's port is not very up to date and there are missing drivers
> for wb_timer, wb_uart and other free peripherals cores... I would like to
> know what is the status of your uclinux port and hardware support

The port is working, even though it has only a bare-bone kernel and Busybox 
for now. But Florian is working on porting OpenWrt.
The UART (for console), the timer and the CF card are supported, and Takeshi 
is working on the framebuffer device.

> and if
> there's any way I can build it on my boards.

Definitely, Takeshi even posted binaries (see list archives) to make that job 
easier.
http://www.sfc.wide.ad.jp/~macchan/milkymist_linux_0910.tgz

> Is there any repo with the
> patches? I've been digging and couldn't find them on github.

It's here:
http://github.com/lekernel/milkymist-linux

> If I can manage to make it run on my board

What boards are you using? If you need some help, just ask on this mailing 
list...

> I'd like to help you with this
> project. I've some experience with or1200 debug system, specially with the
> new debug implementation from Nathan Yawn. Hope it can give LM32 support
>  for most popular debugging cables through standalone jtag or xilinx
>  bscans.

That would be cool!

Sébastien