problems burning

[2inil8]

hi guys having a few dramas burning tunes atm
my burner reader was working ok,had a virus wich stuffed everthing so started again
lucky i had all my tunes on another comp.
what happens it reads fine, some memcals burn ok but this one atm a national 256 (vr v8 man)
just doesent want to write sometimes gets halfway stops others doesnt even start
i did however get it to burn yesterday ok but erasesd as i changed tune.
is it just a prob with them eeprom or perhaps settings on my reaader/burner?
its the GQ-4X btw.

[The1]

you using a header to interface the chip, sometimes needs riggle the contacts sorta rust up a bit though you can't see it. Should work though unless the chip is going faulty, ive had some like that, just needed a slower burn speed.

[Holden202T]

yeah i second the slower speed .... i had a similar issue the other week, moved the twp and twc ? sliders to slow the whole process down and it worked fine. i think from memory i doubled the numbers that it was default set at.

[2inil8]

Thanks guys worked like a charm!

[2inil8]

hey guys got another question
i want to burn a 32k bin to 64k chip
but not sure on the offset
file offset has 000000 and device offset 000000
i seen its 8000 but not sure wich to set???
never done it before.

[The1]

do a stack in tp5 then burn the stacked bin.

[charlay86]

32K = 32 * 1024 = 32768 = 0x8000
Hint: If you set windows calculator to scientific view it converts between decimal and hexadecimal.
You would need to set the device offset to 0x8000.
File offset is how far into the binary file you want to start taking the data from, to write to the device.

[2inil8]

thanks tried it today worked perfect