i checked the dip2plcc adapter -- everything is fine. all pins are connected properly.
is it possible that this does not work because the wires are too long (bios savior + dip2plcc adapter)? would it help to reduce the clockrate of the epia-m? does someone know how that could be done?
it is okay if i boot without dip2plcc converter and then plug it on top of the bios savior. i am going to try booting linux and then place only dip2plcc conv + doc mill. see if the mtd is detected.
niki
On Tue, 2 Sep 2003, Niki Waibel wrote:
is it possible that this does not work because the wires are too long (bios savior + dip2plcc adapter)?
it is asynch. logic last time I checked.
It could still be a timing issue however.
it is okay if i boot without dip2plcc converter and then plug it on top of the bios savior. i am going to try booting linux and then place only dip2plcc conv + doc mill. see if the mtd is detected.
good idea.
ron
is it possible that this does not work because the wires are too long (bios savior + dip2plcc adapter)?
it is asynch. logic last time I checked.
It could still be a timing issue however.
it is okay if i boot without dip2plcc converter and then plug it on top of the bios savior. i am going to try booting linux and then place only dip2plcc conv + doc mill. see if the mtd is detected.
good idea.
hmmm -- modprobe docprobe doc_config_location=0xFFFFe000 (is this the right way to check it?) reports: 0E: bios savior with orig rom (i010010f.bin) without dip2plcc (switched to internal rom) OE: bios savior with orig rom (i010010f.bin) + dip2plcc + doc (switched to internal rom) 00: bios savior with orig rom (i010010f.bin) + dip2plcc + doc (switched to external rom) FF: nothing in the bios socket 00: dip2plcc + doc in the bios socket hmm -- 00 ... seems to be ok in both cases... or should it be sthg else? is doc_config_location=0xFFFFe000 corect?
niki
is it possible that this does not work because the wires are too long (bios savior + dip2plcc adapter)?
it is asynch. logic last time I checked.
It could still be a timing issue however.
it is okay if i boot without dip2plcc converter and then plug it on top of the bios savior. i am going to try booting linux and then place only dip2plcc conv + doc mill. see if the mtd is detected.
good idea.
hmmm -- modprobe docprobe doc_config_location=0xFFFFe000 (is this the right way to check it?) reports: 0E: bios savior with orig rom (i010010f.bin) without dip2plcc (switched to internal rom) OE: bios savior with orig rom (i010010f.bin) + dip2plcc + doc (switched to internal rom) 00: bios savior with orig rom (i010010f.bin) + dip2plcc + doc (switched to external rom) FF: nothing in the bios socket 00: dip2plcc + doc in the bios socket hmm -- 00 ... seems to be ok in both cases... or should it be sthg else? is doc_config_location=0xFFFFe000 corect?
maybe this has sthg to do with the reset state of the doc mill... maybe that confuses the bios savior...
no. not possible, because then it would work with bios savior +dip2plcc -doc... all this is very strange to me.
niki
-
Niki Waibel -
ron minnich