I have a partial disassembly (somewhere) of the code that gets
downloaded into the M100 from the DVI. I will l send it to you. It
contains some "guesses" of what is going on because I don't have it
completely disassembled and understood.
Ken
On 11/23/18 8:46 AM, Stephen Adolph wrote:
interesting. do you have a disassembly?
On Fri, Nov 23, 2018 at 11:27 AM Fugu ME100 <[email protected]
<mailto:[email protected]>> wrote:
The I2C serial EEPROM will need to hold the M100/T102/T200 boot
code, M100/T102 Disk BASIC Code and the T200 disk BASIC code (2
parts) which is probably not a lot of bytes by todays standards
:-) The Disk BASIC also goes out to read the version info from
the DVIs own boot code which is an interesting twist, it requests
the specific sector where the version info is located. As all the
sector locations are fixed they are very easy to intercept.
From: M100 <[email protected]
<mailto:[email protected]>> on behalf of Stephen
Adolph <[email protected] <mailto:[email protected]>>
Reply-To: <[email protected] <mailto:[email protected]>>
Date: Friday, November 23, 2018 at 6:05 AM
To: <[email protected] <mailto:[email protected]>>
Subject: Re: [M100] project updates.
update:
I received my MTVGA PCBs yesterday and have built one up. So
far so good, powers up like it should.
I've been reverse engineering the DVI, and I've decided to try
and make this 100% compatible with DVI meaning the M100 will
auto-detect it's presence, and MTVGA will auto-load and
install the DVI software that originally came with DVI. This
requires the ability for MTVGA to store and deliver to the
M100 the needed DVI software. Plan is to use I2C serial
eeprom for that.
<snip>
