DIY Mutable Unsuccessful Builds

[Altitude909]

so right on the money.

[jkjelec]

Thanks arthurdent and Fouchy. It appears that the 3.3V regulator runs warm in the Warps normally. For the modules I've ben debugging here, it turns out that we had an incorrect part on the kits for IC2 (LM4040 regulator diode). The result was mostly just noise out of the audio output, and the LED for the algorithm knob only showed about 4 different colors/algorithms when the knob was turned, not the expected 9.
Replacing the LM4040 with the correct 10V part solved those problems. We're going to continue testing these modules; I'll post an update soon.

If IC2 on your PCB is marked "R5D", it is an incorrect part. If you bought a kit from synthCube and you have the wrong part, PM me and we'll get the correct part out to you.

[arthurdent]

Thanks arthurdent and Fouchy. It appears that the 3.3V regulator runs warm in the Warps normally. For the modules I've ben debugging here, it turns out that we had an incorrect part on the kits for IC2 (LM4040 regulator diode). The result was mostly just noise out of the audio output, and the LED for the algorithm knob only showed about 4 different colors/algorithms when the knob was turned, not the expected 9.
Replacing the LM4040 with the correct 10V part solved those problems. We're going to continue testing these modules; I'll post an update soon.

If IC2 on your PCB is marked "R5D", it is an incorrect part. If you bought a kit from synthCube and you have the wrong part, PM me and we'll get the correct part out to you.

PM sent.

[jkjelec]

I poked around on the one Warps PCB here that is showing distortion/glitchiness after installing the correct LM4040; here's what I found:

Tested the unit in crossfade mode, using two external oscillators into inputs 1 and 2.
With nothing plugged into Level jacks 1 or 2, input 1 is good, but input 2 drops out/crackles.
Plugging a CV into Level jack 2, the dropouts on audio input 2 stop, and the level of audio input 2 is controlled as expected when varying the CV.
Removing the plug from the Level 2 jack, the dropouts return.
Guessing that maybe the "NORMALIZATION PROBE" signals from the uC aren't getting back to the uC strongly enough, so it's waffling between "internal" and "external" control of the level of Input 2, causing the dropouts. Maybe if the gain of the Normalization probe signal is increased, the uC will see it and stop waffling.
Tacked in 400k ohms of resistance in parallel with R35, and the dropouts stop! And the Modulator Amplitude Knob for Audio input 2 still works as expected! This makes R35 133K rather than 200k ohms.
To explore further, I tried instead tacking 200k ohms of resistance in parallel with R35 instead of 400k. This makes R35 100K rather than 200k ohms. But this caused the audio of input 2 to go silent. So there seems to be a sweet spot for the gain of the uC feedback/the value of R35. Probably 150k to 175k ohms. I'll explore more tomorrow.

I wonder what the root cause of this is still? Tolerance and offsets of the analog circuits or power rails/voltage references? I'll check those tomorrow. Perhaps it's just due to SW that's a bit too unforgiving of various boards/component tolerances/schmutz on the boards?

If your Warps build is showing dropouts on input 2, it would help to know if this modification solves your board's issue.

[Altitude909]

have you calibrated it

[arthurdent]

I poked around on the one Warps PCB here that is showing distortion/glitchiness after installing the correct LM4040; here's what I found:

Tested the unit in crossfade mode, using two external oscillators into inputs 1 and 2.
With nothing plugged into Level jacks 1 or 2, input 1 is good, but input 2 drops out/crackles.
Plugging a CV into Level jack 2, the dropouts on audio input 2 stop, and the level of audio input 2 is controlled as expected when varying the CV.
Removing the plug from the Level 2 jack, the dropouts return.
Guessing that maybe the "NORMALIZATION PROBE" signals from the uC aren't getting back to the uC strongly enough, so it's waffling between "internal" and "external" control of the level of Input 2, causing the dropouts. Maybe if the gain of the Normalization probe signal is increased, the uC will see it and stop waffling.
Tacked in 400k ohms of resistance in parallel with R35, and the dropouts stop! And the Modulator Amplitude Knob for Audio input 2 still works as expected! This makes R35 133K rather than 200k ohms.
To explore further, I tried instead tacking 200k ohms of resistance in parallel with R35 instead of 400k. This makes R35 100K rather than 200k ohms. But this caused the audio of input 2 to go silent. So there seems to be a sweet spot for the gain of the uC feedback/the value of R35. Probably 150k to 175k ohms. I'll explore more tomorrow.

I wonder what the root cause of this is still? Tolerance and offsets of the analog circuits or power rails/voltage references? I'll check those tomorrow. Perhaps it's just due to SW that's a bit too unforgiving of various boards/component tolerances/schmutz on the boards?

If your Warps build is showing dropouts on input 2, it would help to know if this modification solves your board's issue.

I just rummaged through my stash of misc. pieces/parts. I don't have anything close to 400K to try; I have a couple of 100K but I don't have 4 that I could series to get to 400. Also, is this something that should be/needs to be done in conjunction with installing the correct LM4040? If so, then I'd have to wait until you send that out anyway. Guess you could sent a resistor too if that will work. DUNNO - maybe you need to complete all of your debugging first to see ALL of the changes that will need to be made; with everything in place on the PCB (including jacks, pots, etc.) things are pretty tight and I'd like to only go back in there one more time if possible. I've already been at it a couple times doing reflow on some components and I'm getting nervous about frying something or starting to lift pads.

[jkjelec]

arthurdent, no sense trying this R35 change unless you’ve changed to the correct LM4040 and there are dropouts.

[arthurdent]

arthurdent, no sense trying this R35 change unless you’ve changed to the correct LM4040 and there are dropouts.

Regarding the audio dropouts, there's been discussion in a few previous posts regarding this, some people solved it by changing out caps C7, C8, C12 & C14 from the 4,700p called out in the BOM to 10,000p. I have already done this but it did not solve my problem. BUT, if I have the wrong chip for IC2, MAYBE changing that out will get things running. Don't know, just a thought.....

[jkjelec]

arthurdent and Altitude909 thank you for the tips! The 1V/Oct calibration routine alone did not change anything, but the Normalization calibration routine from earlier in this thread, performed after the 1V/Oct calibration routine fixed the dropouts issue. There's no need for anyone to adjust the value of R35.

[arthurdent]

arthurdent and Altitude909 thank you for the tips! The 1V/Oct calibration routine alone did not change anything, but the Normalization calibration routine from earlier in this thread, performed after the 1V/Oct calibration routine fixed the dropouts issue. There's no need for anyone to adjust the value of R35.

So, are you saying that the only thing needed to fix the problems is to install the correct chip in place of IC2? Or are you still working through the build?

[jkjelec]

Yes, sort of. The correct IC (in the mail) will allow your board to work properly, if there aren't other underlying problems specific to your build that would cause your board to not work properly, that previously could not be tested due to the IC2 issue. It appears that any systematic or synthCube kit issues have been solved.

[arthurdent]

Yes, sort of. The correct IC (in the mail) will allow your board to work properly, if there aren't other underlying problems specific to your build that would cause your board to not work properly, that previously could not be tested due to the IC2 issue. It appears that any systematic or synthCube kit issues have been solved.

OK, thanks. I've already received the notice from synthCube that a package has shipped, I haven't ordered anything so I'm assuming it's the IC. I'll get it installed as soon as I get it and let you know what happens. Once again THANKS

[jkjelec]

Great! Even if your board has an issue once you replace IC2, don't worry, there's plenty of friendly, knowledgeable people like arthurdent and Altitude99 on this thread that can help you!

[arthurdent]

Yes, sort of. The correct IC (in the mail) will allow your board to work properly, if there aren't other underlying problems specific to your build that would cause your board to not work properly, that previously could not be tested due to the IC2 issue. It appears that any systematic or synthCube kit issues have been solved.

OK, thanks. I've already received the notice from synthCube that a package has shipped, I haven't ordered anything so I'm assuming it's the IC. I'll get it installed as soon as I get it and let you know what happens. Once again THANKS

IT LIVES!! I received the correct chip for IC2 from synthCube, changed it out (PITA!), fired it up, calibrated and ran the normalization routine - even got the CORRECT colors at the different steps this time - and everything functions. I even went through the DivKid Warps video at the MI website to verify that I was setting it up the right way (I sometimes mix up carriers and modulators). So, all is well. Thanks to the folks at synthCube as well as all the others who offered advice and support

[Rumble]

Have just built a 0603 Stages. Flashed successfully and have tested the voltages across the IC's and they look good.

However its not going into Calibration mode after flashing from mutable dev environment. It doesn't look like its even booting properly. LEDs are randomly lit (different each time its powered on) stage 5 and 6 are outputting negative voltage.
Buttons and sliders and non responsive.
Not responding to gates.

[Altitude909]

Have just built a 0603 Stages. Flashed successfully and have tested the voltages across the IC's and they look good.

However its not going into Calibration mode after flashing from mutable dev environment. It doesn't look like its even booting properly. LEDs are randomly lit (different each time its powered on) stage 5 and 6 are outputting negative voltage. Buttons and sliders and non responsive.
..

where did you get your processor from? 373RBT6 parts have been unobtanium for the last 2+ years, if it came from a non-official source its likely fake

[Rumble]

Have just built a 0603 Stages. Flashed successfully and have tested the voltages across the IC's and they look good.

However its not going into Calibration mode after flashing from mutable dev environment. It doesn't look like its even booting properly. LEDs are randomly lit (different each time its powered on) stage 5 and 6 are outputting negative voltage. Buttons and sliders and non responsive.
..

where did you get your processor from? 373RBT6 parts have been unobtanium for the last 2+ years, if it came from a non-official source its likely fake

I reckon you're right. Here's a screengrab from STLINK GUI

unobtainum.png (39.44 KiB) Viewed 729 times

[Altitude909]

yeah, thats all wrong. you have a remarked discard

[Rumble]

yeah, thats all wrong. you have a remarked discard

Thanks for confirming. Saved me a bunch of time troubleshooting. Much Appreciated.

[Fouchy]

Thanks arthurdent and Fouchy. It appears that the 3.3V regulator runs warm in the Warps normally. For the modules I've ben debugging here, it turns out that we had an incorrect part on the kits for IC2 (LM4040 regulator diode). The result was mostly just noise out of the audio output, and the LED for the algorithm knob only showed about 4 different colors/algorithms when the knob was turned, not the expected 9.
Replacing the LM4040 with the correct 10V part solved those problems. We're going to continue testing these modules; I'll post an update soon.

If IC2 on your PCB is marked "R5D", it is an incorrect part. If you bought a kit from synthCube and you have the wrong part, PM me and we'll get the correct part out to you.

This was the problem with my build. The correct part has fixed the problem. Warps is working.

Thanks Synthcube for debugging this and sending out the correct part.

[Rumble]

Does anyone know if its possible to using other STMF373 variants in the Stages module?

I have a STM32F373RC. It shares the same datasheet as the STM32F373RB.

Thanks
Rumble

[Altitude909]

Does anyone know if its possible to using other STMF373 variants in the Stages module?

I have a STM32F373RC. It shares the same datasheet as the STM32F373RB.

Thanks
Rumble

no. different RAM and program size

[Rumble]

no. different RAM and program size

Thanks again.

[forestcaver]

I’m not as confident as @Altitude909 that it wont work tbh. Your part *may* work ok. You’d need to carefully check the datasheet - I suspect there is a good chance it will work though. (It has a larger flash and RAM). I dont think you would need to change the code either - but check all the peripherals in the datasheet carefully. I havent checked carefully enough to be sure either way, but if you dont want it, I’ll try it :-)

[Altitude909]

i may have read the spec sheet backwards, if its bigger it should work.