DIY Mutable Unsuccessful Builds

From circuitbending to homebrew stompboxes & synths, keep the DIY spirit alive!

Moderators: lisa, luketeaford, Kent, Joe.

Post Reply
p_boban
Learning to Wiggle
Posts: 17
Joined: Wed May 27, 2020 9:42 am

Re: DIY Mutable Unsuccessful Builds

Post by p_boban » Sat Jun 06, 2020 10:01 am

Hey all,

I am having trouble flashing Grids as well as Branches. I am getting the same error in the Mutable Vagrant for both so it seems to be the programmer, although unsure.

-Using olimex avr-isp-mk2
-Windows 10 with mutable vagrant up and running
- avrdude patched to 5.11, confirmed with "avrdude -v" although i'm a novice with linux so I could be wrong here
- olimex shows up under libusb for device manager on a fresh restart. once vagrant is up and running it disappears from device manager in windows
- used flip to load libusb hex

Error:
make[1]: Entering directory `/vagrant/eurorack-modules'
/usr/local/CrossPack-AVR/bin/avrdude -V -p m328p -c avrispmkII -P usb -B 10 -e -u \
-U efuse:w:0x05:m \
-U hfuse:w:0xd8:m \
-U lfuse:w:0xff:m \
-U lock:w:0x2f:m
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_command(): failed miserably to execute command 0x03
avrdude: stk500v2_getparm(): failed to get parameter 0x98
avrdude: Unable to get parameter 0x98
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_command(): failed miserably to execute command 0x02

avrdude: stk500v2_setparm(): failed to set parameter 0x98

avrdude done. Thank you.

Before flashing firmware or installing anything I would get the same error but a lot slower. These rapid fire

Appreciate any help, thank you!

User avatar
Faye
Common Wiggler
Posts: 55
Joined: Thu Jan 30, 2020 10:45 am

Re: DIY Mutable Unsuccessful Builds

Post by Faye » Sat Jun 06, 2020 3:45 pm

This may be a somewhat stupid question, but it's really preoccupying me: As a novice, I assume that on a completely unpopulated PCB there is either complete continuity between 2 solder pads or there is no continuity at all. I'm making this assumption since there are no kind of resistors or other components present on the PCB. So either there is a direct connection between 2 pads or none at all.
However, when measuring resistance between certain solder pads, this assumption is quickly disproved: I get fluctuating measurements in the range of 80-150k. Is there an explanation for this? :hmm: (I observed this phenomenon on PCBs of different modules, so I don't think that the cause is a faulty PCB.)

Btw, is there a better thread for such small questions? If so, I'll gladly move it.

User avatar
emmaker
Veteran Wiggler
Posts: 622
Joined: Sat Mar 10, 2012 5:07 pm
Location: PDX

Re: DIY Mutable Unsuccessful Builds

Post by emmaker » Sat Jun 06, 2020 4:25 pm

Faye wrote:
Sat Jun 06, 2020 3:45 pm
This may be a somewhat stupid question, but it's really preoccupying me: As a novice, I assume that on a completely unpopulated PCB there is either complete continuity between 2 solder pads or there is no continuity at all. I'm making this assumption since there are no kind of resistors or other components present on the PCB. So either there is a direct connection between 2 pads or none at all.
However, when measuring resistance between certain solder pads, this assumption is quickly disproved: I get fluctuating measurements in the range of 80-150k. Is there an explanation for this? :hmm: (I observed this phenomenon on PCBs of different modules, so I don't think that the cause is a faulty PCB.)

Btw, is there a better thread for such small questions? If so, I'll gladly move it.
For a normal board with no components you are correct. There should be no conductivity for no connection or probably less that 1 ohm if there is a connection.

Are you measuring the board on a conductive surface or putting your figures on the meter probes?

A slightly conductive surface will change resistance the more you press the board down on it.

Peoples hands usually are moist and thus conduct. Resistance depends on the moisture content of your hand and how hard you press. Grab your meter probes with it set to megohms or ohms with autoranging and see what happens.

User avatar
Faye
Common Wiggler
Posts: 55
Joined: Thu Jan 30, 2020 10:45 am

Re: DIY Mutable Unsuccessful Builds

Post by Faye » Sat Jun 06, 2020 5:41 pm

I took measurements with the PCB lying on a piece of paper and on glass. Same results on both surfaces. My fingers are not touching the probes.
I also tried cleaning the PCB with isopropyl alcohol. No difference.

I think this may be an issue with the device that I'm using to take measurements. It's the smart tweezer LCR Research Elite 2. It has no ohm/megaohm settings, but I can change the test frequencies. On higher test frequencies (>100kHz) which are used for measuring capacitance and inductance, I get no continuity. But on 1kHz (which is the recommended frequency for anything ranging from 25mOhm to 10MOhm) I get those resistances in the 80-150k range. I think I will contact the manufacturer. Maybe he has an explanation for this behavior on some solder pads.

User avatar
emmaker
Veteran Wiggler
Posts: 622
Joined: Sat Mar 10, 2012 5:07 pm
Location: PDX

Re: DIY Mutable Unsuccessful Builds

Post by emmaker » Sat Jun 06, 2020 9:37 pm

Faye wrote:
Sat Jun 06, 2020 5:41 pm
I think this may be an issue with the device that I'm using to take measurements. It's the smart tweezer LCR Research Elite 2.
A LCR/network analyzer is the wrong tool for this job.

PCB runs close together form a RC circuit and the AC signal generated is probably going from one run to another.

Get a DVM, even a cheap one ($5-$10) would be better than what you're using.

User avatar
Faye
Common Wiggler
Posts: 55
Joined: Thu Jan 30, 2020 10:45 am

Re: DIY Mutable Unsuccessful Builds

Post by Faye » Sun Jun 07, 2020 1:17 am

@emmaker I see....thanks a lot for this valuable information! That means that the underlying technology to measure resistance is different between DMM and LCR?
Why does such an expensive tool have a "resistance measuring" mode if it's delivering wrong values then?

User avatar
emmaker
Veteran Wiggler
Posts: 622
Joined: Sat Mar 10, 2012 5:07 pm
Location: PDX

Re: DIY Mutable Unsuccessful Builds

Post by emmaker » Sun Jun 07, 2020 3:54 pm

Faye wrote:
Sun Jun 07, 2020 1:17 am
@emmaker I see....thanks a lot for this valuable information! That means that the underlying technology to measure resistance is different between DMM and LCR?
Why does such an expensive tool have a "resistance measuring" mode if it's delivering wrong values then?
Yes, the measurement techniques are different. For ohms a DVM puts a small current thru a part and measures resistance with that. The LCR puts a signal thru the circuit and figures things out.

LCR falls into a realm called network analysis. Network analysis is mainly used to figure out the impedance and reactance of passive LCR (inductance, capacitance, resistance) circuits. One of the other things you can do with it is with a number of knowns you can figure out some of the unknowns which could be resistance.

No need to regurgitate it all here. Go to Wikipedia and look up electronic network analyzer and LCR meter.

Jay S.
Last edited by emmaker on Sun Jun 07, 2020 5:16 pm, edited 1 time in total.

User avatar
Faye
Common Wiggler
Posts: 55
Joined: Thu Jan 30, 2020 10:45 am

Re: DIY Mutable Unsuccessful Builds

Post by Faye » Sun Jun 07, 2020 4:47 pm

@emmaker cool! Thanks a lot for the explanation. I will do so!
@mods again, sorry for hijacking the thread.

p_boban
Learning to Wiggle
Posts: 17
Joined: Wed May 27, 2020 9:42 am

Re: DIY Mutable Unsuccessful Builds

Post by p_boban » Mon Jun 08, 2020 12:35 pm

Hey all,

I am having difficulty understanding why I am getting the "avrdude: stk500v2_recv_mk2: error in USB receive" error but when I run the check test with Grids - "avrdude -p m328p -c avrispmkII -P usb" - it will recognize the 328p chip. I am using avrdude 5.11 but would it be possible that installing avrdude 5.11 on top of 6.0.1 causes errors? Thank you!

User avatar
sines
A Certain Wiggler
Posts: 177
Joined: Fri Jul 31, 2009 3:28 pm
Location: NYC

Re: DIY Mutable Unsuccessful Builds

Post by sines » Mon Jun 08, 2020 3:44 pm

Banging my head against the wall here. Have successfully flashed 10+ times in the past, but that's when Vagrant was working on a more current Macbook Pro. Now I have a very stripped down OG Macbook Air running 10.11.6 El Capitan, with a whopping 2GB of RAM and about 8-10GB of free space. Xcode for El Capitan and Command Line Tools are install. I've installed VirtualBox 5.2.42, 5.2.36, and 6.1.10 with corresponding Extension Packs. Installed current [as of June 7, 2020] Vagrant.

When I type

Code: Select all

vagrant up
My machine starts installing and then hangs .. to the point of being immobilized after 20 minutes.

So I'm trying to do the most up to date GCC-ARM chain via

Code: Select all

brew install homebrew/cask/gcc-arm-embedded
And also modifying “eurorack/stmlib/makefile.inc”

Code: Select all

TOOLCHAIN_PATH to /Users/§username§/arm-cs-tools/
After running

Code: Select all

make install-cross

Code: Select all

I get the following
../../../../../gcc-4.8-2014.05/libgcc/config/arm/ieee754-df.S: Assembler messages:
../../../../../gcc-4.8-2014.05/libgcc/config/arm/ieee754-df.S:567: Error: invalid constant (ff) after fixup
../../../../../gcc-4.8-2014.05/libgcc/config/arm/ieee754-df.S:673: Error: invalid constant (ff) after fixup
../../../../../gcc-4.8-2014.05/libgcc/config/arm/ieee754-df.S:689: Error: invalid constant (fd) after fixup
../../../../../gcc-4.8-2014.05/libgcc/config/arm/ieee754-df.S:875: Error: invalid constant (ff) after fixup
../../../../../gcc-4.8-2014.05/libgcc/config/arm/ieee754-df.S:912: Error: invalid constant (fd) after fixup
../../../../../gcc-4.8-2014.05/libgcc/config/arm/ieee754-df.S:985: Error: invalid constant (fd) after fixup
make[5]: *** [_arm_muldivdf3_s.o] Error 1
make[5]: *** Waiting for unfinished jobs....
make[4]: *** [multi-do] Error 1
make[3]: *** [all-multi] Error 2
make[2]: *** [all-target-libgcc] Error 2
make[1]: *** [all] Error 2
make: *** [cross-gcc-first] Error 2
If I try to build a hex / makefile of any firmware it looks like this:

Code: Select all

stmlib/makefile.inc:374: build/rings_bootloader/depends.mk: No such file or directory
/usr/local/arm-4.8.3/bin/arm-none-eabi-g++ -MM -g -O2 -Wall -Werror -Wno-unused-local-typedefs -Wno-strict-aliasing -fasm -finline -finline-functions-called-once -fdata-sections -ffunction-sections -fshort-enums -fno-move-loop-invariants -fno-unwind-tables -I. -DGCC_ARMCM4 -DSTM32F40_41xxx -DSTM32F4XX -DARM_MATH_CM4 -D__FPU_PRESENT -DNO_APPLICATION  -DF_CPU=168000000L -DF_CRYSTAL=8000000L -DHSE_VALUE=8000000L -DUSE_STDPERIPH_DRIVER -DSYSCLK_FREQ_168MHz=168000000L -Istmlib/third_party/STM -Istmlib/third_party/STM/CMSIS/CM3_f4xx -Istmlib/third_party/STM/CMSIS/CM3_f4xx/startup/gcc -Istmlib/third_party/STM/STM32F4xx_StdPeriph_Driver/inc -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -mthumb-interwork -funroll-loops -fno-exceptions -fno-rtti rings/bootloader/bootloader.cc -MF build/rings_bootloader/bootloader.d -MT build/rings_bootloader/bootloader.o
make: /usr/local/arm-4.8.3/bin/arm-none-eabi-g++: No such file or directory
make: *** [build/rings_bootloader/bootloader.d] Error 1
I have done the following commands:

Code: Select all

brew install homebrew/cask/gcc-arm-embedded
sudo python setup.py install
export PYTHONPATH=.
export PYTHONPATH=$PYTHONPATH:/usr/local/lib/python2.7/site-packages
git submodule init && git submodule update
git submodule update stmlib
+++ probably 10 commands as well.

I cannot move forward. I sense I'm close — and would be DONE if Vagrant would work, but with a memory leak, I can't complete the build of the Mutable vagrant environment to finish.

I'm all ears!

Thanks,

Todd

davidcolinsmith
Learning to Wiggle
Posts: 4
Joined: Fri Apr 17, 2020 6:31 pm

Re: DIY Mutable Unsuccessful Builds

Post by davidcolinsmith » Mon Jun 08, 2020 3:54 pm

Hey, folks!

I have a Rings build that is working as designed, except for that I'm only getting half of the expected output when in duo or quad mode. Another symptom is that there doesn't seem to be any input coming out of the WM8731 AUX_OUT/ROUT port. I will reflow C33 after work today, but my hunch is that the issue is upstream from the WM8731.

All tests have been run with an external baby10-style sequencer, CV out to V/Oct and clock out to Strum. The tone sounds so great!

I am not familiar enough with the code base (this is my first MCU-based build) and can't tell from the schematic what port the MCU is sending the oscilator signal to the WM8731 on. I'll dig into the code tonight, but if someone could tell me how the MCU is sending the oscillator to the WM8731, I can probably diagnose from there.

Any help/advice would be greatly appreciated!

User avatar
roya
Common Wiggler
Posts: 151
Joined: Thu May 11, 2017 10:15 am
Location: London

Re: DIY Mutable Unsuccessful Builds

Post by roya » Mon Jun 08, 2020 7:25 pm

davidcolinsmith wrote:
Mon Jun 08, 2020 3:54 pm
Hey, folks!

I have a Rings build that is working as designed, except for that I'm only getting half of the expected output when in duo or quad mode. Another symptom is that there doesn't seem to be any input coming out of the WM8731 AUX_OUT/ROUT port. I will reflow C33 after work today, but my hunch is that the issue is upstream from the WM8731.

All tests have been run with an external baby10-style sequencer, CV out to V/Oct and clock out to Strum. The tone sounds so great!

I am not familiar enough with the code base (this is my first MCU-based build) and can't tell from the schematic what port the MCU is sending the oscilator signal to the WM8731 on. I'll dig into the code tonight, but if someone could tell me how the MCU is sending the oscillator to the WM8731, I can probably diagnose from there.

Any help/advice would be greatly appreciated!
Are you using the even output? Try the odd (or vice versa, not in front of my rack)

davidcolinsmith
Learning to Wiggle
Posts: 4
Joined: Fri Apr 17, 2020 6:31 pm

Re: DIY Mutable Unsuccessful Builds

Post by davidcolinsmith » Mon Jun 08, 2020 7:39 pm

roya wrote:
Mon Jun 08, 2020 7:25 pm
Are you using the even output? Try the odd (or vice versa, not in front of my rack)
Thanks for the reply! I understand the general ODD=mono, ODD+EVEN=stereo, but following the logic, I'm never actually getting signal out of even via the AUX_OUT, per the schematic. More to the point, when only ODD is connected (should get combined left and right fields), I get all notes for monophonic, but only every other note for duophonic or quadrophonic.

User avatar
cnicht
Veteran Wiggler
Posts: 699
Joined: Mon Sep 23, 2013 9:23 am

Re: DIY Mutable Unsuccessful Builds

Post by cnicht » Tue Jun 09, 2020 9:06 am

Both output channels of the CODEC should have signal on them.

Are you able to measure this?

davidcolinsmith
Learning to Wiggle
Posts: 4
Joined: Fri Apr 17, 2020 6:31 pm

Re: DIY Mutable Unsuccessful Builds

Post by davidcolinsmith » Tue Jun 09, 2020 11:18 am

I'll get an oscilloscope on both PIN12 and PIN13 tonight and report back.

I just reviewed the J9/J10 portion of the schematic, and realized what the connection from J10-P2 to R39 means. :doh: I had assumed that there were multiple digital outs from the STM, is that a false assumption? If so (and it sounds/looks like that is the case), it seems that my issue is likely between PIN13 and R56, and should be pretty easy to locate with the oscilloscope!

User avatar
cnicht
Veteran Wiggler
Posts: 699
Joined: Mon Sep 23, 2013 9:23 am

Re: DIY Mutable Unsuccessful Builds

Post by cnicht » Tue Jun 09, 2020 12:05 pm

Pin 13 is a good place to start

steviet
Common Wiggler
Posts: 216
Joined: Wed Oct 17, 2018 9:47 am
Location: Montréal
Contact:

Re: DIY Mutable Unsuccessful Builds

Post by steviet » Tue Jun 09, 2020 2:54 pm

p_boban wrote:
Mon Jun 08, 2020 12:35 pm
Hey all,

I am having difficulty understanding why I am getting the "avrdude: stk500v2_recv_mk2: error in USB receive" error but when I run the check test with Grids - "avrdude -p m328p -c avrispmkII -P usb" - it will recognize the 328p chip. I am using avrdude 5.11 but would it be possible that installing avrdude 5.11 on top of 6.0.1 causes errors? Thank you!
Flashing the chips can get weird, especially if you've updated/downgraded/replaced drivers. That being said these errors are very generic. I would attempt to use a different programmer, or a different computer. Do you have an arduino laying around? It can be used an ISP programmer in a pinch, and was actually how I ended up getting both grids and branches programmed.

After a lot of trial, error, and starting with a fresh install, I got the Olimex adapter working in Atmel studio but never from the command line. I did get my arduino ISP programmer working from the command line using this tutorial here.
Soundcloud
Website - DIY/Euro/Gear Blog updated every Sunday

davidcolinsmith
Learning to Wiggle
Posts: 4
Joined: Fri Apr 17, 2020 6:31 pm

Re: DIY Mutable Unsuccessful Builds

Post by davidcolinsmith » Tue Jun 09, 2020 4:39 pm

Yep, 'twas right at PIN13! Joint looked good, but after pulling the Damping pot and taking a closer look with a 30x loupe, it looked a bit off. Reflowed that pin, and everything is working as expected now. Thanks for the help!!!

User avatar
cnicht
Veteran Wiggler
Posts: 699
Joined: Mon Sep 23, 2013 9:23 am

Re: DIY Mutable Unsuccessful Builds

Post by cnicht » Tue Jun 09, 2020 4:44 pm

:tu:

soupspoon
Learning to Wiggle
Posts: 20
Joined: Thu May 28, 2020 3:45 pm

Re: DIY Mutable Unsuccessful Builds

Post by soupspoon » Tue Jun 09, 2020 5:09 pm

I managed to load the bootloader and the firmware, but now there is no output. The LEDs are completely dark, except for a constant green LED at the bottom and a flickering red LED at the top. The supply rails are correct (+/-12V) and the 10V and 3.3V references are correct. What should I check?

User avatar
cnicht
Veteran Wiggler
Posts: 699
Joined: Mon Sep 23, 2013 9:23 am

Re: DIY Mutable Unsuccessful Builds

Post by cnicht » Wed Jun 10, 2020 4:33 am

I presume you're referring to a Plaits build?

Have you placed the jack sockets?

soupspoon
Learning to Wiggle
Posts: 20
Joined: Thu May 28, 2020 3:45 pm

Re: DIY Mutable Unsuccessful Builds

Post by soupspoon » Wed Jun 10, 2020 9:50 am

cnicht wrote:
Wed Jun 10, 2020 4:33 am
I presume you're referring to a Plaits build?

Have you placed the jack sockets?
Yes, sorry! Totally forgot that information. I have placed everything on the PCB, including the jacks.

funketek
Learning to Wiggle
Posts: 11
Joined: Sun Jan 19, 2020 11:48 pm

Streams JTAG issue

Post by funketek » Wed Jun 10, 2020 11:25 am

Hello - I just completed a Streams build but cannot flash the firmware (using STLink v2 with ST Utility application on Windows 10). AREF 2.5 and 10V are correct, however the voltage regulator is being fed 11.73V and putting out ~3.6V, not the expected 3.3. I tried changing out the voltage reg, but still have the same reading. Also replaced the diode which drops the 12V from 12 down to 11.73, but again same reading.

What's interesting is when I connect the cable to the JTAG, the 3.3v rail does drop from 3.6 to the correct 3.3, but ST utility cannot find the target. I have successfully flashed many other Mutable builds with this STlink so I do not think that is the issue. The 12V power draw (without LEDs/Bargraph plugged in) is 40mA with nothing plugged in. When JTAG cable is connected the power draw goes up to 80mA (or 270 mA if plugged in the other way) and the voltage reg starts to heat up. I am measuring 3.3-3.6v on the JTMS and JTDI pins on the JTAG, but I am not sure if that is correct? Pictures of the board included if anyone can see any glaring issues.

Wondering if anyone has experienced anything similar or has any suggestions?

Thanks!

Image
You do not have the required permissions to view the files attached to this post.

User avatar
forestcaver
Veteran Wiggler
Posts: 639
Joined: Tue Mar 14, 2017 4:41 pm
Location: UK
Contact:

Re: DIY Mutable Unsuccessful Builds

Post by forestcaver » Wed Jun 10, 2020 12:44 pm

Any reason for mounting the jtag connector on the component side? That’s going to make some interesting wiring to get the right pinout for the stlinkv2..... :-)

User avatar
cnicht
Veteran Wiggler
Posts: 699
Joined: Mon Sep 23, 2013 9:23 am

Re: DIY Mutable Unsuccessful Builds

Post by cnicht » Wed Jun 10, 2020 2:01 pm

soupspoon wrote:
Wed Jun 10, 2020 9:50 am
cnicht wrote:
Wed Jun 10, 2020 4:33 am
I presume you're referring to a Plaits build?

Have you placed the jack sockets?
Yes, sorry! Totally forgot that information. I have placed everything on the PCB, including the jacks.
Is there any signal coming out of the DAC?

Post Reply

Return to “Music Tech DIY”