On 12 Nov 2003 at 9:41, Jerome Grimbert wrote:
> To check the process, I read the old 2.91 eprom, process them via rrom_bas.
> I get a nice file which menuconfig is happy with, finding config block.
> Alas, this file fails badly when lrespr-ised.
Oh, now that is very strange!
> Looking at the beginning of the two files (the 2.91 and my home 3.01),
> the 2.91 seems to start with a Q40 Hardware Initialisation module,
> where as in the 3.01 that module is after a SMSQ/E modules management module
> (or something that sound similar). Is this the reason for my failure ?
No, it shouldn't be.
I've checked the startup code and couldn't find anything suspicious in it (I'm not
sure I
would have been able to find it, anyway).
It looks something like this
base
bra.s user ; junk SP
bra.s debug
dc.l rom_start-base+Q40_ROM ; jump to start of ROM
which should be the perfect way to differentiate between ram and ROM, knowing that if
it is in ROM, this should be at address 0. There the first 4 bytes are supposed to be
the
SSP and the next four bytes the PC.
Since the code junks the SSP anyway, we don't care about the first four bytes...
> (I just used the provided flp_bas program, must it be modified to produce the rom
> code ?)
No, it shouldn't.
> Does anybody succeed in making eprom for the Q40 with a recent version of SMSQ/E ?
Unfortunately, I don't have en Eprom blower, so I can't test this.
>How did you do ? (hint and direction welcome)
Sorry, no help here yet.
Wolfgang
