TRINITY
Organization:
The Team
Abstract
Charter
Deliverables:
Background
Requirements
Considerations
Design Spec.
Compliance
Certification
Management:
Status
Timeline
Resources:
Software
Hardware
Tutorials
Extras:
Weasel's Dev Diary
Weasel's Dev Diary

September 15th, 2001

Inspired by developers diaries such as Alan Cox's linux kernel development diary, and the numerous .plan diaries among developers in the game industry, I've decided to keep one of my own on here as we go through the processes of developing the Trinity product.

I just got through doing the web page, and putting in all the bits that are sensible to put in. I updated the charter as I pasted it in to reflect how we're going about the project now, and it's all looking quite nice I think.

Before I left for home for the weekend, I was tinkering with an old Motorola MVME133 single board computer. Wired up the power supply, attached my laptop as a terminal, and managed to talk to the debugger, 133bug, a bit before I took some pictures and went to bed for the night. Need to figure out how to get a C compiler to generate useful code for it, and get it talking on its serial ports. If we can't do that, we'll be on the hunt for a better machine to make a prototype out of. At the very least, I intend upon writing a Linux version of the prototype software so that I can test out the Palm OS code while we're waiting on getting the prototype up and running.

Once the Palms come in and I can start writing the code for that, I'll probably pass what I've got on the the MVME133 off to Lee, since he'll be doing the programming for the prototype, but I'll still be working close with him on getting GCC cross-compiling code for it.

Now, time to take a break...


Design by Wesley "Weasel" McGrew