Re: BusBlaster V3c for MIPS?

> Do you actually want to debug YAMON
> because something does not work as expected?
> Or what do you want to achieve?

two goals
1) debug an existing version of YaMon, as it integrates a gdb-stub
which doesn't work as expected.
2) reprogram a second board, as its ROM doesn't contain YaMon but a
rather custom firmware (probably related to VxWorks but I am not sure)

>  NB Atlas is weird, the Philips STB chip is a quirky PITA
> which is why we dropped support for this system from Linux long ago.

I see negative comments on the MIPS wiki against the Atlas board.
I never owned an Atlas board, yesterday I retrieved two boards
(different revisions) from an industrial dumpster, but when I was a
student, we had an Atlas board in our universitary laboratory.

I don't have any bad memories about it: around 2009, we didn't run
GNU/linux on the board (kernel 2.4? 2.6?), we programmed in assembly
(GNU/AS + GNU/LD) on our host computers (i586 GNU/Linux) and loaded
the elf binary via ethernet into the board.

We wrote some metal-bare application, compiled static with a simple
lib-c and a super simple crt0.S, things that used nothing but the CPU,
the small alphanumeric display on the mobo, the serial and the timer;
in some lab exercises we also used COP0 for CPU exceptions, and may be
limited use, but I don't remember anything that wasn't described by
the book "See MIPS run".

What's the problem with Atlas?