Hi, I have a question about eeprom programming. The last thing I need to do when writing eeprom effects is to use Asprogrammer and the ch341 device. That's the background. The first thing I need to do is convert the SPN effect code file I downloaded. Is this correct? To do this, I downloaded SpinAsm to my computer. I wanted eight effects in SPN format. I loaded these eight different effect files into the desired list, in eight SPN files, and got one hex output. Now, to write this hex file to the eeprom, I opened the file in the Asprogrammer program I mentioned earlier. I can write the hex file to the eeprom, and I see it. But what I don't understand is, will my eeprom be able to read the hex file on my FV-1 pedal kit? Is that all there is to it? Don't I need to convert it to a bin file or something? If so, how can I do this?
Fv-1 EEPROM
- Thread starter serhay
- Start date
Robert
Reverse Engineer
The last time I used Asprogrammer (years ago) I don't think it supported HEX files, so you had to convert the HEX file produced by SpinAsm into a BIN file.
If Asprogrammer now supports HEX files and successfully wrote the file to the EEPROM that's all you need to do.
If Asprogrammer now supports HEX files and successfully wrote the file to the EEPROM that's all you need to do.
Hi, Yes, I understand better now. What you're trying to say is that if any program can read and write the resulting hex file, you don't need to convert it to bin format. So, load the hex file into the eeprom and insert the eeprom chip into your FV-1 effects circuit. Cheers, the effects will work. Is what I understand correct? Thank you very much. I have no doubts left in my mind.
Açıklayayım: spinASM'den efekt çıktısından tek bir hex dosyası alıyorum ve bu hex dosyasını AsProgrammer ve ch341 eeprom adlı bir programla okuyabiliyor, hatta bir eeprom'a yazabiliyorum. Yani, size göre her şey yolunda, yani bir sorun yok. Öyle mi? Değerli üstatlar, tüm saygımla teşekkür ederim.
Robert
Reverse Engineer
Correct, as long as Asprogrammer is reading the HEX files correctly there is no need to convert to BIN.
Asprogrammer doesn't know what it is writing to the EEPROM, it just writes the file you give it.
It's entirely possible that it wrote useless data to the EEPROM if it doesn't properly support the HEX format.
Plug it in and try it, the worst that will happen is the EEPROM won't work and you'll have no sound from the FV-1 IC. You can reflash the EEPROM as many times as necessary.
Paradox916
Well-known member
Good to know if I ever decide to mess with EEPROMs again
Robert
Reverse Engineer
I should add, the "Verify EEPROM" button in an EEPROM programmer tool just confirms that what is on the EEPROM matches what is in the file.
The EEPROM programmer software has no idea if it's valid data, corrupt data, an FV-1 algorithm, or a JPEG image. All it knows is that the contents of the file you provided (regardless of whether it's in a format the FV-1 can read or not) matches what is on the EEPROM.
Exactly. (Except the part about SpinAsm, it doesn't write BIN files, there's a different tool to handle the conversion)
I think some of this might be outdated but the general idea is covered here:
wiki.pedalpcb.com
wiki.pedalpcb.com
wiki.pedalpcb.com
The EEPROM programmer software has no idea if it's valid data, corrupt data, an FV-1 algorithm, or a JPEG image. All it knows is that the contents of the file you provided (regardless of whether it's in a format the FV-1 can read or not) matches what is on the EEPROM.
Exactly. (Except the part about SpinAsm, it doesn't write BIN files, there's a different tool to handle the conversion)
I think some of this might be outdated but the general idea is covered here: