DIY Mutable Unsuccessful Builds

[Stoneyards]

Have you inadvertently used a 2.5V voltage reference instead of a 10V component?

Yes. This is exactly what I did.

Thanks cnicht and Adam, who suggested the same thing. (Thx for the support, Adam btw.). I had ruled this out initially because "why on earth would I have a selection of LM4040s?" Turns out I built a batch of PCBs, and bought parts for Frames, Ripples, Plaits, and Elements all at once. These use a variety of LM4040s in 2.5V, 5V and 10V flavours. Luckily I'd only messed up on Elements.

I found the most valuable part of this thread is the "here's what I learned" section, so here's what I learned:

• Don't skip the step of checking all your voltages, SMD parts are much harder to deal with once you have pots, jacks mounted.
• When looking at long part numbers, pay attention to the WHOLE part number.
• If a VREF is "perfectly" wrong, like 2.5, 5. 10, 12V, look at the vref part before searching for other problems.

[cnicht]

Excellent

[bosko303]

Hi All,

I've recently finished a Jak Plugg Pachinko (Mutable Instruments Marbles) and am having trouble getting full functionality. When flashing the module I get the following response:

Cheers, Alex

Probably an issue with the DAC or path from the DAC to outputs.I would try a reflow again with tons of flux. If that doesn't work, start probing from the stm onward. It does not need to be fully calibrated to get outputs. They will just not be perfectly accurate. You've confirmed value, but have you confirmed orientation from the eagle of the original marbles? Pachinko switches some of the orientation relative to the original.

A well lit, up close pic of the back will help far more for diagnostics than the pic provided.

Here's a picture of the back :

I've gone through and confirmed all orientations/correct IC against the .dip file for the Pachinko so no luck there unfortunately. I've also checked continuity between every pin/surrounding pin on the STM and found that to all be correct.

I'm a little confused as the RESET pin (NRST pin 7) has a constant 3.3v after it boots up. I've had a look at the schematic of the STM and it does have an internal pull up resistor on this pin, but would you expect that to drop to 0v once it's correctly booted ?

[elcoco]

Hi everyone I'm back with the same problem but this time on a new pcb. I tried just the components for power and programming the board but my stlink utility doesn't even detect that the board is connected.I'm using an stlink\v2 with the latest firmware, stlink utility and the pin adapter shown in the first picture.,

-Elcoco

[mrverschwie]

Unfortunately I still haven't got any luck finishing my Jak Plugg Twists. When flashing the STM everything seems to be ok, but when I power on the module the STM doesn't seem to be working. The LED's don't work, neither do any of the controls or cv-inputs. All of the voltages measure correct, no shorts, 3.3v at the vdd of the STM and other ic's. I'm starting to think there's something wrong with the STM, or the bootloader and firmware aren't loaded correctly. So I'm hoping someone can have a look at the output I got from the terminal after flashing the STM

Many thanks!

mv:~/Desktop/eurorack-modules/build$ ls -la warps/warps.hex
-rw-rw-r-- 1 mv 296635 Dec 31 14:22 warps/warps.hex
mv-VirtualBox:~/Desktop/eurorack-modules/build$ ls -la warps_bootloader/warps_bootloader.hex
-rwxrwxr-x 1 mv 46536 Dec 31 14:22 warps_bootloader/warps_bootloader.hex

mv-VirtualBox:~/Desktop/eurorack-modules$ make -f warps/makefile upload
cat build/warps/ui.d build/warps/warps.d build/warps/resources.d build/warps/cv_scaler.d build/warps/settings.d build/warps/debug_port.d build/warps/adc.d build/warps/system.d build/warps/leds.d build/warps/switches.d build/warps/codec.d build/warps/filter_bank.d build/warps/vocoder.d build/warps/oscillator.d build/warps/modulator.d build/warps/atan.d build/warps/units.d build/warps/random.d build/warps/bootloader_utils.d build/warps/system_clock.d build/warps/system_stm32f4xx.d build/warps/stm32f4xx_wwdg.d build/warps/stm32f4xx_sai.d build/warps/stm32f4xx_dcmi.d build/warps/stm32f4xx_adc.d build/warps/stm32f4xx_spdifrx.d build/warps/stm32f4xx_dac.d build/warps/stm32f4xx_can.d build/warps/stm32f4xx_qspi.d build/warps/stm32f4xx_hash_sha1.d build/warps/stm32f4xx_hash.d build/warps/stm32f4xx_iwdg.d build/warps/stm32f4xx_flash.d build/warps/misc.d build/warps/stm32f4xx_sdio.d build/warps/stm32f4xx_dma.d build/warps/stm32f4xx_cryp_des.d build/warps/stm32f4xx_hash_md5.d build/warps/stm32f4xx_cec.d build/warps/stm32f4xx_rng.d build/warps/stm32f4xx_dma2d.d build/warps/stm32f4xx_lptim.d build/warps/stm32f4xx_spi.d build/warps/stm32f4xx_flash_ramfunc.d build/warps/stm32f4xx_fmpi2c.d build/warps/stm32f4xx_exti.d build/warps/stm32f4xx_fsmc.d build/warps/stm32f4xx_cryp_tdes.d build/warps/stm32f4xx_dbgmcu.d build/warps/stm32f4xx_rtc.d build/warps/stm32f4xx_pwr.d build/warps/stm32f4xx_i2c.d build/warps/stm32f4xx_gpio.d build/warps/stm32f4xx_fmc.d build/warps/stm32f4xx_rcc.d build/warps/stm32f4xx_ltdc.d build/warps/stm32f4xx_syscfg.d build/warps/stm32f4xx_crc.d build/warps/stm32f4xx_usart.d build/warps/stm32f4xx_dsi.d build/warps/stm32f4xx_cryp_aes.d build/warps/stm32f4xx_cryp.d build/warps/stm32f4xx_tim.d build/warps/startup_stm32f4xx.d > build/warps/depends.mk
cat build/warps/warps.hex build/warps_bootloader/warps_bootloader.hex | \
awk -f stmlib/programming/merge_hex.awk > build/warps/warps_bootloader_combo.hex
/usr/local/arm-4.8.3/bin/arm-none-eabi-objcopy -I ihex -O binary build/warps/warps_bootloader_combo.hex build/warps/warps_bootloader_combo.bin
openocd -s /usr/share/openocd/scripts/ -f interface/stlink-v2.cfg -f target/stm32f4x.cfg -c "init" -c "halt" -c "sleep 200" \
-c "flash erase_address 0x08000000 32768" \
-c "reset halt" \
-c "flash write_image erase build/warps/warps_bootloader_combo.bin 0x08000000" \
-c "verify_image build/warps/warps_bootloader_combo.bin 0x08000000" \
-c "sleep 200" -c "reset run" -c "shutdown"
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : clock speed 1800 kHz
Info : STLINK v2 JTAG v29 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.185882
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : device id = 0x100f6413
Info : flash size = 1024kbytes
erased address 0x08000000 (length 32768) in 0.898773s (35.604 KiB/s)
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
adapter speed: 1800 kHz
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x1fff3da0 msp: 0x20001d80
auto erase enabled
wrote 262144 bytes from file build/warps/warps_bootloader_combo.bin in 12.448898s (20.564 KiB/s)
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000002e msp: 0x20001d80
verified 138208 bytes in 2.392233s (56.420 KiB/s)
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
adapter speed: 1800 kHz
shutdown command invoked

[elcoco]

Hi everyone, I finally got it working, it was the cable that wasn't making a good connection. I just bought some jumper cables and they both work now Thanks for your help.

[pjbulls]

Ran into some issues with my DIY Braids... Worked OK until I tried to calibrate it. After that, the output frequency would switch only between extremely high-pitched and subsonically slow, and did so continuously throughout the rotation of the coarse tune knob (so not low to high as you'd expect).

Turns out I was calibrating it from the A output on my uO_c while toggling octaves on the D channel. That and I switched the tuning source to 'extended' in trying to fix the previous error which further breaks V/oct tracking.

Took me an hour of reflashing and recalibrating to figure all of that out, works great again. 11/10 module, too bad it doesn't protect me from my own stupidity

[batchas]

Hi everyone, I finally got it working, it was the cable that wasn't making a good connection. I just bought some jumper cables and they both work now Thanks for your help.

Great it works now. Time to play!

Took me an hour of reflashing and recalibrating to figure all of that out, works great again. 11/10 module, too bad it doesn't protect me from my own stupidity

The positive thing is that we learn out of our errors. And most of all it works. Very cool. Braids is a great module, have fun

[djd_oz]

I attempted to build the Mutable Shelves .... and am experiencing a strange issue which I tried to demonstrate the video below. The yellow line is the input which is a Saw Wave and the output is the blue line. With all the Gain knobs set at the center position I'm getting a -10V at the outputs. Only if I turn the High Self Gain or Low Shelf Gain clockwise, I see a signal at the output, which is only the positive signal (i.e. 0 - 5V), the negative part of the signal is missing.

Also, it seems like only the first parametric EQ is working, the second does not make any changes to the sound. However, I think we probably need to fix the above problem first.

Any assistance in troubleshooting this will be greatly appreciated.

[cnicht]

Several components seem not to be correctly soldered - C40 and C50 for example.

Also there are lots of globules of solder all over the board which need cleaning off.

[djd_oz]

I tried cleaning it up a bit and fixing some solder joints and it worked for a couple of mins and then after moving the module a little it stopped working and went back to what it was before.

Sounds like a loose component of sorts ... the problem is which one? lol

[djd_oz]

the problem is which one? lol

Found it! Looks like pin7 on IC5 wasn't soldered on correctly .... now to troubleshoot the second fault.

[djd_oz]

Second problem have been resolved, one of the TL074 chips was faulty, I replaced it and am getting some response from turning the knobs for the 2nd parametric EQ, however, it is all over the place. I've discovered that I'm getting a reading of 10.4V at both ends of C39 and R85, no matter what the position is with the R68 pot. Also, 10.4V at pin3 of IC11A.

I'm comparing with the 1st parametric EQ which is working, where I'm getting 0V at the left hand side of the equivalent of C39 and R85, and on the right hand side is between 0 - 2.6V depending on the position of the pot and also 0 - 2.6 V at the equivalent pin3 of IC11A.

Could this be another faulty TL074 that I should be replacimg?



And the relevent components are in the below pic.

[cnicht]

Are the diodes D11 and D16 the correct way round?

[mrverschwie]

Anyone any idea on this one? I still haven't got any further.

Unfortunately I still haven't got any luck finishing my Jak Plugg Twists. When flashing the STM everything seems to be ok, but when I power on the module the STM doesn't seem to be working. The LED's don't work, neither do any of the controls or cv-inputs. All of the voltages measure correct, no shorts, 3.3v at the vdd of the STM and other ic's. I'm starting to think there's something wrong with the STM, or the bootloader and firmware aren't loaded correctly. So I'm hoping someone can have a look at the output I got from the terminal after flashing the STM

Many thanks!

mv:~/Desktop/eurorack-modules/build$ ls -la warps/warps.hex
-rw-rw-r-- 1 mv 296635 Dec 31 14:22 warps/warps.hex
mv-VirtualBox:~/Desktop/eurorack-modules/build$ ls -la warps_bootloader/warps_bootloader.hex
-rwxrwxr-x 1 mv 46536 Dec 31 14:22 warps_bootloader/warps_bootloader.hex

mv-VirtualBox:~/Desktop/eurorack-modules$ make -f warps/makefile upload
cat build/warps/ui.d build/warps/warps.d build/warps/resources.d build/warps/cv_scaler.d build/warps/settings.d build/warps/debug_port.d build/warps/adc.d build/warps/system.d build/warps/leds.d build/warps/switches.d build/warps/codec.d build/warps/filter_bank.d build/warps/vocoder.d build/warps/oscillator.d build/warps/modulator.d build/warps/atan.d build/warps/units.d build/warps/random.d build/warps/bootloader_utils.d build/warps/system_clock.d build/warps/system_stm32f4xx.d build/warps/stm32f4xx_wwdg.d build/warps/stm32f4xx_sai.d build/warps/stm32f4xx_dcmi.d build/warps/stm32f4xx_adc.d build/warps/stm32f4xx_spdifrx.d build/warps/stm32f4xx_dac.d build/warps/stm32f4xx_can.d build/warps/stm32f4xx_qspi.d build/warps/stm32f4xx_hash_sha1.d build/warps/stm32f4xx_hash.d build/warps/stm32f4xx_iwdg.d build/warps/stm32f4xx_flash.d build/warps/misc.d build/warps/stm32f4xx_sdio.d build/warps/stm32f4xx_dma.d build/warps/stm32f4xx_cryp_des.d build/warps/stm32f4xx_hash_md5.d build/warps/stm32f4xx_cec.d build/warps/stm32f4xx_rng.d build/warps/stm32f4xx_dma2d.d build/warps/stm32f4xx_lptim.d build/warps/stm32f4xx_spi.d build/warps/stm32f4xx_flash_ramfunc.d build/warps/stm32f4xx_fmpi2c.d build/warps/stm32f4xx_exti.d build/warps/stm32f4xx_fsmc.d build/warps/stm32f4xx_cryp_tdes.d build/warps/stm32f4xx_dbgmcu.d build/warps/stm32f4xx_rtc.d build/warps/stm32f4xx_pwr.d build/warps/stm32f4xx_i2c.d build/warps/stm32f4xx_gpio.d build/warps/stm32f4xx_fmc.d build/warps/stm32f4xx_rcc.d build/warps/stm32f4xx_ltdc.d build/warps/stm32f4xx_syscfg.d build/warps/stm32f4xx_crc.d build/warps/stm32f4xx_usart.d build/warps/stm32f4xx_dsi.d build/warps/stm32f4xx_cryp_aes.d build/warps/stm32f4xx_cryp.d build/warps/stm32f4xx_tim.d build/warps/startup_stm32f4xx.d > build/warps/depends.mk
cat build/warps/warps.hex build/warps_bootloader/warps_bootloader.hex | \
awk -f stmlib/programming/merge_hex.awk > build/warps/warps_bootloader_combo.hex
/usr/local/arm-4.8.3/bin/arm-none-eabi-objcopy -I ihex -O binary build/warps/warps_bootloader_combo.hex build/warps/warps_bootloader_combo.bin
openocd -s /usr/share/openocd/scripts/ -f interface/stlink-v2.cfg -f target/stm32f4x.cfg -c "init" -c "halt" -c "sleep 200" \
-c "flash erase_address 0x08000000 32768" \
-c "reset halt" \
-c "flash write_image erase build/warps/warps_bootloader_combo.bin 0x08000000" \
-c "verify_image build/warps/warps_bootloader_combo.bin 0x08000000" \
-c "sleep 200" -c "reset run" -c "shutdown"
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : clock speed 1800 kHz
Info : STLINK v2 JTAG v29 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.185882
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : device id = 0x100f6413
Info : flash size = 1024kbytes
erased address 0x08000000 (length 32768) in 0.898773s (35.604 KiB/s)
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
adapter speed: 1800 kHz
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x1fff3da0 msp: 0x20001d80
auto erase enabled
wrote 262144 bytes from file build/warps/warps_bootloader_combo.bin in 12.448898s (20.564 KiB/s)
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000002e msp: 0x20001d80
verified 138208 bytes in 2.392233s (56.420 KiB/s)
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
adapter speed: 1800 kHz
shutdown command invoked

[10T5]

Wondering if anybody has any advise or spot anything obvious,

I built elements about a year ago, installed the firmware with STM link32 utility via PC and the module seemed to be working ok, sound was working and knobs were responsive to changing the sound.

The only thing was i hadn't installed the gate switch (was waiting for it to arrive)

Once i soldered the gate switch into place, the gate switch flashed for a second and the module never worked again, no LEDS, No sound, Dead.

The STM link 32 utility doesn't see the module anymore, so i tried it with a braids i made and it sees braids ok so i know there no issue with the STM link side of things, tried different orientation with oumex ribbon/JTAG no luck.

Read on this forum that maybe its just my potentiometer positions, tried that no luck.

Going by "occams razor" adding the Gate switch caused my issue, but maybe adding that blew something else? didnt see any magic smoke at the time and can't see anything burnt on the board, you can see the orientation of the gate switch in the photo with the green spot at the bottom i assume thats right?
I don't feel like removing the Gate switch yet, desoldering 8 solder points could cause a bit of destruction.

I noticed when i hook up to 12v, the back of the PCB around where the 12v and gate switch area gets rather hot to the touch, don't know if this is normal?

i've looked over and over at the solder joints with a loupe.

Hey Cane Creek
Have exactly the same issue (same board, same switch). Did you found any solution? Saw somewhere it may indicate a communication issue between the MCU and the audio codec

[AlterX]

Re: Anookum - programming the 328P MCU
1. Has anyone who's built the Anookum (Anushri, or anything similar that had to burn the MCU) used an ArduinoISP? Was it successful?
2. Is there any other troubleshooting I can/should do on the finished boards to see if there's another problem? I have read the Mutable Instruments pages on the Anushri, but they assume you have a factory-programmed MCU chip.

Thank you!

I was entirely unsuccessful using ArduinoISP when I built my Anookum (2018)
When I built a USB Tiny interface and a ZIF skiff to program my chips independent of Arduino, AVRDude worked perfectly, and I had zero issues. For some reason, I always have issues flashing chips while they are onboard in my builds.
Also, the MI forums have a wealth of knowledge...in addition to the build guides.

Greetings.

I used AVRDude to flash my build. Had to make a few tweeks to the code links and add the fuses, but works fine biz. Getting the BP Filter to work on my build is fun. Drums are cool too :-)

[AlterX]

Wondering if anybody has any advise or spot anything obvious,

I built elements about a year ago, installed the firmware with STM link32 utility via PC and the module seemed to be working ok, sound was working and knobs were responsive to changing the sound.

The only thing was i hadn't installed the gate switch (was waiting for it to arrive)

Once i soldered the gate switch into place, the gate switch flashed for a second and the module never worked again, no LEDS, No sound, Dead.

The STM link 32 utility doesn't see the module anymore, so i tried it with a braids i made and it sees braids ok so i know there no issue with the STM link side of things, tried different orientation with oumex ribbon/JTAG no luck.

Read on this forum that maybe its just my potentiometer positions, tried that no luck.

Going by "occams razor" adding the Gate switch caused my issue, but maybe adding that blew something else? didnt see any magic smoke at the time and can't see anything burnt on the board, you can see the orientation of the gate switch in the photo with the green spot at the bottom i assume thats right?
I don't feel like removing the Gate switch yet, desoldering 8 solder points could cause a bit of destruction.

I noticed when i hook up to 12v, the back of the PCB around where the 12v and gate switch area gets rather hot to the touch, don't know if this is normal?

i've looked over and over at the solder joints with a loupe.

Hey Cane Creek
Have exactly the same issue (same board, same switch). Did you found any solution? Saw somewhere it may indicate a communication issue between the MCU and the audio codec

Sorry to ask. Is the switch orientated correctly ?

[pjbulls]

That was my first thought as well, but it looks like it (the little notches on top of the black body are aligned with the dot on the silkscreen - unless that is what's wrong).

[djd_oz]

Are the diodes D11 and D16 the correct way round?

I removed D11, D16, R85 and C39 and put resoldered them back in again and now it works!

[cnicht]

Excellent!

[Altitude909]

That was my first thought as well, but it looks like it (the little notches on top of the black body are aligned with the dot on the silkscreen - unless that is what's wrong).

The dot on the switch should be on the same side as the dot on the PCB, it looks like it is

[CliffordMilk]

I've just finished building a Clouds and a Rings. I Flashed the firmware on Clouds no problem but when I try for rings, I get the following error. Can anyone see anything obvious before I go over the board again?

make -f rings/makefile upload_combo_jtag
openocd -s /opt/local/share/openocd/scripts/ -f interface/stlink-v2.cfg -f target/stm32f4x.cfg -c "init" -c "halt" -c "sleep 200" \
-f stmlib/programming/jtag/erase_f4xx.cfg \
-c "flash write_image erase build/rings/rings_bootloader_combo.bin 0x08000000" \
-c "verify_image build/rings/rings_bootloader_combo.bin 0x08000000" \
-c "sleep 200" -c "reset run" -c "shutdown"
Open On-Chip Debugger 0.9.0 (2021-01-12-19:18)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : clock speed 1800 kHz
Info : STLINK v2 JTAG v29 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 2.971504
Error: init mode failed (unable to connect to the target)
in procedure 'init'
in procedure 'ocd_bouncer'

make: *** [upload_combo_jtag] Error 1
vagrant@vagrant-ubuntu-trusty-64:/vagrant/eurorack-modules$

[in-fm]

Hadn't seen this problem posted before but apologies if it has been asked. Finished my Rings build last week using the SynthCube kit I was gifted, and everything has worked great in my testing except for the attenuators. It seems as though they are reversed (turning CCW makes the CV increase the value instead of decrease). It is this way on all of the attenuators. I wasn't really sure where to start looking for the problem and thought it might even be a firmware issue but any help is greatly appreciated. Thanks!

[pjbulls]

Most CV inputs on MI modules pass through attenuverters, not attenuators. The difference is that an attenuverter can change the amplitude as well as the sign of the CV: 0% near center, +100% fully CW, and -100% fully CCW.

Are you sure you're not actually inverting your CV, and that it is fully attenuated near the pot's 12 o'clock position?