burning .dat files on GQ4X

A place For General Chit Chat Etc
hatchssv8
Posts: 45
Joined: Sun Jan 17, 2010 8:14 am
cars: Holdens 66, 76, 77, 90, 05
Location: Melbourne

burning .dat files on GQ4X

Post by hatchssv8 »

Can anyone help me out here guys?

I am familiar with burning .bin files but have a request from someone to burn some eproms with .dat files.
Is it just the same as burning the bin files? I noticed on the programmer requests what type of file is to be written but .dat is not listed

Any ideas are much appreciated

Thanks in advance

PS: I have a 9kb .dat file to be burnt on a 27c64A eprom
User avatar
antus
Site Admin
Posts: 10016
Joined: Sat Feb 28, 2009 10:34 am
cars: TX Gemini 2L Twincam 8psi
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Subaru WRX 2007

Re: burning .dat files on GQ4X

Post by antus »

the 64 denotes 64bit, so divide by 8 to convert to kbyte. So that makes it an 8kilobyte chip. Can you post the file up? It might need some kind of conversion. I suspect its not going to be raw data.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
hatchssv8
Posts: 45
Joined: Sun Jan 17, 2010 8:14 am
cars: Holdens 66, 76, 77, 90, 05
Location: Melbourne

Re: burning .dat files on GQ4X

Post by hatchssv8 »

test.DAT.bin
here is the file



delete the .bin to rename the file....it would not let me upload as .dat
You do not have the required permissions to view the files attached to this post.
User avatar
antus
Site Admin
Posts: 10016
Joined: Sat Feb 28, 2009 10:34 am
cars: TX Gemini 2L Twincam 8psi
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Subaru WRX 2007

Re: burning .dat files on GQ4X

Post by antus »

Ok, that is raw data but its too long. (The data appears to start at the start, but its 50/50 if its correct and/or why its too long. I'd suggest to rename to bin and try and burn it with the gq4x. If it truncates the file you might be ok. But if the result doesnt work i'd say the problem is with your input file. 9068 bytes instead of 8192.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396