pedal gives 'effects missing' after uploading new effect

[josephcomer]

Hey folks!

As a newbie-ish Python guy, I was able to get all the packages downloaded and everything running.

I have some CDR+ effects that I'd like to add to my 50+. Extremely naively, looking back, I used the GUI, picked a CDR+ .zd2 effect, and attempted to install. The 50+ now displays something like "effect missing".

I'm sure this was me being a dumbass, as I didn't download anything before I pushed the new effect. I"m sure I didn't upload the master effect list on the 50+ before I tried.

A couple of questions: I tried the -R command line argument, to attempt to see the FLST_SEQ file, but the command line keeps telling me I need a filename. I thought this would be a blank file in which the FLST_SEQ file might write to, but I don't think that's correct.

Question 2: I assume if I reinstall all 50+ effects, it will then match up with the existing FLST_SEQ on the pedal, and it should work nominally again? Fully prepared to do some scripting, if necessary.

Apologies for being a dumb ass. Thanks so much for any suggestions.

[mungewell]

I'm not too sure what happened to confuse your pedal, were the new effects from the MS-70CDR+ or other pedal? Here's what I have on mine for reference...

temp.zt2.txt

I tried the -R command line argument

I guess that's a limitation of the coding, it's asking for the file that you want to save the ZT2 that it read. You can just give it a temp file name.

$ python3 zoomzt2.py -s -R temp.zt2 
Group 1 : DYNAMICS
0x01000010 : COMP.ZD2, (v1.10 1)
0x01000020 : RACKCOMP.ZD2, (v1.10 1)
0x01000030 : GRAYCOMP.ZD2, (v1.20 1)
...

Fully prepared to do some scripting

Scripting, or using xargs (if you're on Linux). The --install and --uninstall commands can take multiple ZD2 filenames, so you can remove every effect with something like

$ python3 zoomzt2.py -d -R temp.zt2 | grep "effect " | cut -d "'" -f 2 |$ python3 zoomzt2.py -d -R temp.zt2 | grep "effect " | cut -d "'" -f 2 | xargs python3 zoomzt2.py --uninstall

Or install everything from a directory with

$ ls *.ZD2 | xargs python3 zoomzt2.py --install

Note: if you're using MS-plus then you'll want to use the --include-zic and/or --include-zir flags to make sure those are sent as well. The --help also shows some other options for up/download without affecting pedal's 'zt2'.

Warning: Obviously all this is done at your own risk. I did have a few slip-ups through development, where I had multiple copies of the same file uploaded/left on the device.... I think that these are fixed now, but you may need to double check what's on the file system (easiest with GUI app).

[mungewell]

You can also double check that there's not an overlap with effect IDs, Zoom had some changes for the MS60-B+ but I think that MS-70CDR+ and MS-50G+ should be OK.

$ python3 decode_effect.py -s zoom_fx_HGL/zoom_fx/MS60BPLUS/BOMBER.ZD2 
0x09000040 : BOMBER.ZD2, Bomber (v1.10 8.45%)
$ python3 decode_effect.py -s zoom_fx_HGL/zoom_fx/MS50GPRO/BOMBER.ZD2 
0x07000040 : BOMBER.ZD2, Bomber (v1.10 8.45%

[mungewell]

Just for clarity; when the project started we were adjusting the 'FLST_SEQ.ZT2' file, manually adding/removing effects from it. This is no longer necessary, the command line (and GUI) handles the changing of 'ZT2' automatically.

So the user should just specify the effects to --upload (with 'zic' and 'zir' as necessary).

If you had sent an empty/partial 'ZT2' then re-uploading effects may fix this, but do one and double check whether the file-system has duplicates. I think that we put checks in place to prevent this, but without doing some checking I don't know for certain.

[josephcomer]

Wow! Thanks! i'll give it a try in the next few days and report back. Thanks so much. The CDR+ effects were from a fresh ZD2 file. I'll give the above a shot. Thanks again. Getting this stuff to work is obsessive! :) :)

[josephcomer]

I think, perhaps, I messed up again. The 50g+ hung on the effect upload, and I mistakenly unplugged it ( fell off my desk.)

I can get to the MS-50g+ "splash screen", but its not recognized as connected to the USB. Is there some sort of secret mode (I'm thinking of old school "target disk mode" for ipods) that would let me force a USB connect?

Thanks again.

[mungewell]

@josephcomer Not sure what/how you got your pedal 'stuck', or really what to suggest.... there was another user who figured out the 'FW update mode' for the pedal, but not sure if this would be helpful to recover.

#70 (comment)

[josephcomer]

Sure, I'll follow the link above and check it out. I've heard you can also go to drastic measures... like unsoldering the EPPROM and reflashing it. I don't necessarily want to go down that route, but I'd be a good excuse to get a solder hot air setup. :) I'll try the easy things first. Thanks!

[mungewell]

For my 'screw-up' I did not have to unsolder the EEPROM, using a scope I saw that the FW seemed to access it in 4 parts/sections when the pedal was booted. I took a guess that the 4th section was it reading the active configuration (ie loading effects and current preset).

During this 4th section I shorted the EEPROM data pin to ground (with low value resistor, ~100R) with the hope that it would 'invalidate' any checksum... this seems to have triggered the pedal into a 'factory reset' mode and then the pedal successfully booted.

Obviously I don't know what state your pedal is in, and whether there is any recovery path. All I can do is keep my fingers cross for you.

[hoststjaernen]

@josephcomer There is no need to unsolder EEPROM, you can use simple CH341A Programmer with a test clip.
Yes, it works) I restored my MS-60B+ with a similar "splash screen" error using this method.

[nomadbyte]

...I can get to the MS-50g+ "splash screen", but its not recognized as connected to the USB.

@josephcomer Does your pedal can still connect in firmware update mode?

If the failure occurred during the write to the internal flash, it should only affect the normal boot mode (that's when the firmware loads the "installed" effects). If any error happens at that stage, the boot process may hang. There will be some internal stack trace internally, which can't be seen on the panel anyway.

Meanwhile, the firmware update mode likely runs from a different part of the firmware. I'm not sure about that but it may be in ROM chip. It supports a subset of the SysEx functionality and handles the update of the "normal" firmware" modules.

So, based on this, your pedal may still be able to boot in Firmware Update mode. Assuming that the USB connector is still functional after the fall, the pedal should be available to receive a fw update. The firmware update won't fix the flash error problem by itself but we need to confirm that your pedal can connect to PC in the Firmware Update mode.