Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

So I was working on developing a multicast serial driver. Since I was developing the serial driver, I had to take... over... communication... from the copied-from-ROM driver.

And since there was only 1 working communication port, how did I debug? How did I even run a test?

The board I was developing on was amazing. It had 1 (one) LED.

Blink.

Blink.

Blink (fast).



You should have just taped a photoresistor over the LED and serialized your error codes back into your dev box with morse code.

But I guess then you'd have to debug that code and you'd be back where you started.


This setup is almost exactly like the one in which I first learned C (it had a massive 2048 bytes of SRAM!).

As a bonus, it used a dodgy proprietary compiler with a whole sack of undocumented "technical limitations."

The good part is I now have a really good understanding of pointer manipulation. The bad part is using it sometimes makes me twitch.

Edit: Here's someone who's got us both beat: http://web.archive.org/web/20070613032334/http://ipodlinux.o...


http://3.bp.blogspot.com/_AxcE8NTHeDU/TOW6kRd-FGI/AAAAAAAAAy...




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: