cr1901 changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, CD/floppy disk theory of operation, and the 68k CPU are also on-topic. Channel logs: https://libera.irclog.whitequark.org/~h~yamahasynths
endrift|ZNC is now known as endrift
ejs has joined ##yamahasynths
Degi_ has joined ##yamahasynths
Degi has quit [Ping timeout: 260 seconds]
Degi_ is now known as Degi
andlabs has quit [Read error: Connection reset by peer]
<m4t>
is there a straightforward way to extract the data from a midi syx file to get the firmware?
<m4t>
got a couple more of those tc-helicon voiceprism, and trying to swap the voicecraft expansion card from a dead one into an otherwise working non-plus model. it requires a firmware upgrade to support. just swapping the plcc32 flash chip from one with the card to one without didn't fully boot
<m4t>
i can find a few random fw scattered around but not the one mentioned in the pdf manual
<m4t>
wanted to take a look at the contents of these fw .syx i found and compare it to the flash dumps i took
<m4t>
i suppose the syx format might be different for different vendors
<KitsuWhooa>
You'd probably need to RE the usage of the sysex, yeah. Don't know what format the syx files is, but maybe amidi can read them/send them off to a midi device
<KitsuWhooa>
*don't know the format of your syx files
<m4t>
i'm tempted to just put the addon card in it (it boots but doesnt detect it) then follow the normal procedure to reflash the "plus" firmware
<m4t>
that bricked it hehe
<m4t>
i think it might be the fpga firmware that's incompatible but it's otp
andlabs_ has joined ##yamahasynths
andlabs has quit [Ping timeout: 244 seconds]
<m4t>
nice got both of 'em workin. the first one that'd reset/freeze randomly at boot and if you pressed any of a column of buttons is working fine after i reflashed the firmware via midi. might have been some flipped bits in the eeprom
<m4t>
second one that my friend had swapped the addon card into (but wasn't being detected) i got working after reflashing the firmware on the main unit + card from dumps taken on the first one
<m4t>
i think the addon card had an old incompatible fw version causing it to not be detected or freeze at boot