Personal tools
You are here: Home Systems NCD 88k X-Terminal toolchain built but file format problems
Document Actions

toolchain built but file format problems

by Maki Kato last modified 2004-11-12 15:56

binutils 2.15 built without much problems on a linux(fedora core 2) box using --target=m88k-ncd-none. For a test, I decided to use the one instruction "jmp r1" which for the 88k means return.

gas, ld, and strip did what it's supposed to and I ended up with a reasonable looking 88k BCS executable. Howerer, when I go to boot this on the NCD, it gives me "Incorrect object file" error. I've tried a number of things to tweek the executable to look more like the Xncd19c file, but nothing seems to work.
To verify that a "jmp r1" would work, I copied and modified the Xncd19c file and replaced the first instruction with "jmp r1". This time I got a "File corrupted CRC error". Oops. Upon further inspection, it looks like the ncd looks in the coff timestamp field for a checksum. Substituting zeros here didn't make it work any better. Sigh, I guess I'm gonig to go look at CRC now.

11/12 -- further investigation shows that the timesamp field is not what holds the crc, or I'm not sure how the crc is calculated. I assumed the crc is calculated on the whole file with the crc field set to zero, but quite a number of trial and errors produced no good information.
I'm now guessing that the .bss segment or perhaps the .text or .data contains the CRC. sigh.


Powered by Plone, the Open Source Content Management System

This site conforms to the following standards: