devaliasdev pci ls
-or-
dev pci1 ls
-or-
dev pci2 lsdev pci1/@d .properties
I have been working on my garage for the past week and a half and am finally getting to where all the computer stuff has been dumped (boxes, cables, screws, parts, bits and pieces, etc). I will keep an eye out for the box the card was sent in (it's in one of the piles) and verify.
hex
tokenizer[ 0000 ]tokenizer set-rev-level
tokenizer[ 004A ]tokenizer pci-architecture
tokenizer[ 002A ]tokenizer pci-data-structure-start
tokenizer[ 0020 ]tokenizer pci-data-structure-length
tokenizer[ 105A 4D69 018085 ]tokenizer pci-header
tokenizer[ 10000 ]tokenizer rom-size
fcode-version2
\ format: 0x08
\ checksum: 0x72c0 (ok)
\ len: 0xfd1a (64794 bytes)
hex
headerless
variable variable_800 \ (800)
…
variable variable_816 \ (816)
: colon_l! \ (817)
: colon_l@ \ (818)
: colon_variable_805_l@ \ (819)
: colon_variable_804_l@ \ (81a)
: colon_definition_function_81b \ (81b)
…
: colon_definition_function_822 \ (822)
: colon_variable_80a_l! \ (823)
: colon_definition_function_824 \ (824)
…
: colon_definition_function_83f \ (83f)
" "(…)" \ 252 bytes
encode-bytes
" "(…)" \ 252 bytes
encode-bytes
encode+
…
" "(…)" \ < 252 bytes
encode-bytes
encode+
" driver,FirmTek,MacOS,PowerPC"
property
colon_definition_function_83f \ (83f)
colon_definition_function_824 \ (824)
['] c@
byte-load
fcode-end
pci-end: colon_definition_function_83f \ (83f)
" driver,FirmTek,MacOS,PowerPC"
colon_definition_function_83e \ (83e)
0=
if \ (0x5)
2drop
exit
then
get-package-property
if \ (0x4)
exit
then
drop
dup
colon_l@ \ (818)
dup
0
<>
if \ (0x56)
colon_variable_80a_l! \ (823)
4
+
colon_variable_809_l! \ (821)
" create driver-buffer"
evaluate
colon_variable_80a_l@ \ (822)
allot
" driver-buffer"
evaluate
colon_variable_80b_l! \ (825)
colon_variable_80b_l@ \ (824)
0
<>
if \ (0xb)
colon_variable_80b_l@ \ (824)
colon_variable_80a_l@ \ (822)
erase
colon_definition_function_83d \ (83d)
then
else \ (0x5)
2drop
then
" driver,FirmTek,MacOS,PowerPC"
delete-property
;
ROM dump attached.
The Promise Dos Flashing utility refuses to flash the ROM extracted from the Sonnet utility rsrc fork, says "bad file" or some such. Older versions of PTIFlash supported a Dos command line switch of /Unlimit to bypass any checking for flashing the Promise ATA 100 and older cards, but these versions don't support the ATA 133 card.What about flashing the card under DOS using PROMISE flasher? It loads ROM from the file, unlike Sonnet utility which has it integrated in rsrc part of application. I got ROM dump from Tempo 133 (found on macos9lives forum), saved using PROMISE flasher, but I have a doubt if it's complete. File size is 32768 bytes, while length specified in the header should be 37888 bytes - unless my math is incorrect. 4A in hex gives 74 in decimal, 74x512 gives 37888. Incomplete ROM would brick the card and as I have only one ATA133 to play with, it most likely will be one-way journey
That really doesn't help, we really need a dump of the devices full Open Firmware .properties. Pretty easy on New World machines, but you'll need two Mac's with a serial connection to do it on an Old World machine.
" enet:telnet,192.168.1.201" iotelnet 192.168.1.201It's pretty apparent what the drive-buffer is, it's a buffer. LOL
load hd:,\SonnetPCIROM.bin
" pci/@e" open-dev to my-self
400004a 1 byte-loaddev pci/@e
" Ultra-Tek133P+" encode-string " name" property
" PDC20269" encode-string " model" property
dev .propertiesdevaliasdev pci*number lsYou're right. File size 32768 is too short.What about flashing the card under DOS using PROMISE flasher? It loads ROM from the file, unlike Sonnet utility which has it integrated in rsrc part of application. I got ROM dump from Tempo 133 (found on macos9lives forum), saved using PROMISE flasher, but I have a doubt if it's complete. File size is 32768 bytes, while length specified in the header should be 37888 bytes - unless my math is incorrect. 4A in hex gives 74 in decimal, 74x512 gives 37888. Incomplete ROM would brick the card and as I have only one ATA133 to play with, it most likely will be one-way journey
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/joevt/Library/Python/2.7/bin:/opt/X11/bin:/Library/Apple/usr/bin:/Volumes/Updates/Docs/Open_Firmware_and_Forth/OpenBIOS/JoesOpenBIOSStuff/detok/obj-amd64:/Volumes/Updates/Docs/Open_Firmware_and_Forth/OpenBIOS/JoesOpenBIOSStuff/toke/obj-amd64:/Volumes/Updates/Docs/Open_Firmware_and_Forth/MacOSX
cd /Volumes/Updates/Third\ Party\ System\ Software/Sonnet/ATA133\ Jaguar\ lg\ drive\ support2
theapp=ata133_lgdrv_45
derez "$theapp" > app.z
for theresource in $(perl -0777 -n -E 'while (/data .(....). \((\d+).*\n\t\$"55AA/mg) { print $1 . "_" . $2 . "\n"; }' app.z); do
echo $theresource
derez -only "'${theresource:0:4}'(${theresource:5})" "$theapp" | sed -nE '/.\$"([0-9A-F ]+).*/s//\1/p' | xxd -p -r > "${theresource}.rom"
DumpPCIRom.sh "${theresource}".rom > "${theresource}".4th 2> "${theresource}".log
doneThe firmware is usually loaded from pci probe context. Maybe something is different when you're loading the firmware from disk. Compile a version of the firmware with a bunch of debug statements to see if it gets to the final byte-load command and also to output the address used for the byte load command.
The driver,FirmTek,MacOS,PowerPC property during the first step of the load is not an NDRV - it is missing the PEF header
Joy!peffpwpc that an NDRV should have in the first 12 bytes.I have a Tempo 133 Firmware 4.0.app (for the Tempo Trio) It is similar to the other Tempo firmwares where it decompresses from a driver,FirmTek,MacOS,PowerPC property. I extracted part 2 of the firmware (the decompressed part) from memory in Open Firmware on my 8600 (I think I explained how to get the memory from Open Firmware elsewhere - basically just get a hex dump of the memory range used for the Open Firmware dictionary which also includes all the properties and buffers).
Thank you, it almost worked
sed: RE error: illegal byte sequence-bash: DumpPCIRom.sh: command not found
don't know what could cause that. Post the result of
derez -only "'${theresource:0:4}'(${theresource:5})" "$theapp" > "${theresource}.txt" as a zipped file.That's because you don't have DumpPCIRom.sh.
I'm using Monterey which uses zsh instead of bash so there might be a difference that needs fixing.
I don't know what you mean. Selecting 37888 bytes from what? It sounds like you want to just append some random extra bytes. How is that any better than not having the bytes at all (like your truncated 32768 sized rom).
Here you go. I got an error using this code, attached.
That's because you didn't run the first command which sets
theresource=fwre_136How did you calculate 260 as the offset?
derez to parse the resource fork?toke to create a binary that doesn't have the pci header? (use DumpPCIRom to confirm the result matches the source). And this way you can add to the code to help with debugging.Regarding the compression, the example firmware I have has 64193 bytes of fcode in the first step (63K) and the decompressed fcode is 93816 bytes (91K) so you see how it can be useful if the rom chip is only 64K or if the rom chip also contained a BIOS or EFI image.
