Working on my player, fidsifting, upgrading hijack, installing cushman's xml interface, and who knows what else...

Anyone know what the following boot log means? Neither google nor the bbs search function has anything for ide_data_test.

Boot log contains:
Probing primary interface...
ide_data_test: wrote 0x0000 read 0x0080 -- FAILED
ide_data_test: wrote 0xffff read 0x0080 -- FAILED
ide_data_test: wrote 0xaaaa read 0x0080 -- FAILED
ide_data_test: wrote 0x5555 read 0x0080 -- FAILED
hdb: FUJITSU MHT2030AT, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0080 -- FAILED
ide_data_test: wrote 0xffff read 0x0080 -- FAILED
ide_data_test: wrote 0xaaaa read 0x0080 -- FAILED
ide_data_test: wrote 0x5555 read 0x0080 -- FAILED
hdb: FUJITSU MHT2030AT, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0080 -- FAILED
ide_data_test: wrote 0xffff read 0x0080 -- FAILED
ide_data_test: wrote 0xaaaa read 0x0080 -- FAILED
ide_data_test: wrote 0x5555 read 0x0080 -- FAILED
hdb: FUJITSU MHT2030AT, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0080 -- FAILED
ide_data_test: wrote 0xffff read 0x0080 -- FAILED
ide_data_test: wrote 0xaaaa read 0x0080 -- FAILED
ide_data_test: wrote 0x5555 read 0x0080 -- FAILED
hdb: FUJITSU MHT2030AT, ATA DISK drive
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: IBM-DJSA-220, ATA DISK drive
hdb: FUJITSU MHT2030AT, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: IBM-DJSA-220, 19077MB w/1874kB Cache, CHS=38760/16/63
hdb: FUJITSU MHT2030AT, 28615MB w/2048kB Cache, CHS=58140/16/63

The rest looks just fine. The player works fine, havn't had any no harddisk found messages or anything. I'll just ignore it for the time being. Is the drive/cable/solder joint on the way out?

Matthew

It looks like one drive took longer to spin up on boot and become ready than the other did. Although I have never seen those debug messages before. Are they new to recent hijack revisions? Edit: Answered my own question - hijack 447.

As long as the final set of tests pass, then no worries.

I have those messages there to help diagnose problems on the empeg peripheral bus (to which the IDE header is soldered).

It is rather curious that it shows 0080 on the data lines before the IDE drives finish their reset cycles. I see the same pattern here on the units I've looked at.

What's strange about it, is that 0080 is what the cs4231a chip is designed to emit when it is in "power saving mode".

I don't think this is a coincidence, and it may have something to say about how/why those cs4231a chips seem to fail for no good reason -- there may be a slight timing issue or something that causes them to try and drive the bus when they shouldn't be doing that.

Mmmm..

Ok, glad to hear I can safely ignore it.

Matthew