MUFF WIGGLER Forum Index
 FAQ & Terms of UseFAQ & Terms Of Use   Wiggler RadioMW Radio   Muff Wiggler TwitterTwitter   Support the site @ PatreonPatreon 
 SearchSearch   RegisterSign up   Log inLog in 
WIGGLING 'LITE' IN GUEST MODE

MI Elements build thread
MUFF WIGGLER Forum Index -> Music Tech DIY Goto page 1, 2, 3, 4, 5, 6  Next [all]
Author MI Elements build thread
BARE BONES
are the jacks PJ301BM for Elements?
BARE BONES
any changes from the published BOM?
looks the same to me
adam
PJ-301-M-12 same as clouds
_________________
Veils and Blinds pcb's shipping now Top quality Rings, Elements, Braids, Clouds, Module Tester pcb's available here
bezier
BARE BONES wrote:
any changes from the published BOM?
looks the same to me


I don't think so. I ordered Oliviers bom, built it with the .brd bom, and didn't notice any changes.
loderbast
+1 for what bezier wrote.
mine works fine with the parts from oliviers bom from google docs.
Puzzler
81-GRM185C1H180JA01J is not available at mouser, I changed it to
81-GRM0335C1H180JD1D.

Is this problematic? Miley Cyrus
mxmxmx
Puzzler wrote:


81-GRM0335C1H180JD1D.

Is this problematic?


depends on your eyesight. but probably yes; those would seem to be 0201 (inch) = 0603 (metric), whereas you want 0603 (inch) = 1608 (metric).

there's plenty of alternatives though, which should work just as well.
for example:

81-GRM39C180J50
80-C0603C180J5G
581-06035A180J
...
Puzzler
Oh no, i must have confused "Case Code - in" with "Case Code - mm" cry d'oh!
hallvard
EDIT: moved to another thread, sorry.
limpmeat
I seem to have mangled some of the pads while soldering the STM32.

I tried to trace the pads and it looks like they are floating, which I suppose is why they overheated so easy and lifted.

I checked the schematic and it looks like they are left disconnected anyway. Pads for pins 52 and 53. Can anybody confirm that it's OK to leave them? They don't seem to need to be grounded.
hallvard
I did the same thing on some floating pins and can confirm it worked fine for me!
BARE BONES
When powering up the module before programming the arm chip should the leds light?
I'm trying to program the arm before I put on all the pots and jacks in case there is an issue.
Seemingly not getting any power at the moment
adam
someone else had mysterious issues before fitting pots - strange voltages etc, that all vanished once he'd fitted them
BARE BONES
thanks Adam, i'll put them all on and see what happens then smile
BARE BONES
sadly it's still not working, 3 successful MI builds but it seems like my run of good luck is over....

Could plugging the jtag cable in upside down have caused an issue?

I'm building two and I soldered an ic upside down on the other one, waiting on a replacement part, hopefully that one will work...
BARE BONES
my second Elements took the firmware fine, it seems to work, the leds and push button react to a gate but it doesn't make any sound.
Will have to get my head in the schematics tomorrow
BARE BONES


jtag cable orientation is a bit confusing so here's a pic of the correct way round for anyone who's not sure
BARE BONES
deleted
BARE BONES
there was a tiny solder bridge on IC12, one Elements now fully operational

hihi

get magnification kids!
SoundPool
just being lazy, but has anyone made a mouser or reichelt cart for this?
Zenner
I've already programmed my elements with the bootloader (with stlink utility) I found on github (build folder).
To program the firmware in the same way I do (with stlink utility). The firmeware is elements.hex on github?
BARE BONES
yes
MAHL'-cheek
This keeps happening to me . I Flashed a braids and everything went fine. But with elements it keeps stopping at random times while writing.
I'm using the Vagrant environment.
If anyone has any tips I would really appreciate it.

vagrant@vagrant-ubuntu-trusty-64:/vagrant/eurorack-modules$ make -f elements/makefile upload_combo_serial
python stmlib/programming/serial/stm32loader.py \
-p /dev/ftdi-usbserial \
-b 115200 \
-e -v \
-w build/elements/elements_bootloader_combo.bin
Bootloader version 31
Chip id `['0x4', '0x13']'
Global mass erase; this may take a while
Write 256 bytes at 0x8000000
Write 256 bytes at 0x8000100
Write 256 bytes at 0x8000200
Write 256 bytes at 0x8000300
Write 256 bytes at 0x8000400
Write 256 bytes at 0x8000500
Write 256 bytes at 0x8000600
Write 256 bytes at 0x8000700
Write 256 bytes at 0x8000800
Write 256 bytes at 0x8000900
Write 256 bytes at 0x8000A00
Write 256 bytes at 0x8000B00
Write 256 bytes at 0x8000C00
Traceback (most recent call last):
File "stmlib/programming/serial/stm32loader.py", line 428, in <module>
cmd.writeMemory(conf['address'], data)
File "stmlib/programming/serial/stm32loader.py", line 307, in writeMemory
self.cmdWriteMemory(addr, data[offs:offs+256])
File "stmlib/programming/serial/stm32loader.py", line 188, in cmdWriteMemory
self._wait_for_ack("0x31 programming failed")
File "stmlib/programming/serial/stm32loader.py", line 69, in _wait_for_ack
raise CmdException("No response to %s" % info)
__main__.CmdException: No response to 0x31 programming failed
make: *** [upload_combo_serial] Error 1
gbiz
Try a lower baud rate ?.
jensu
MAHL'-cheek wrote:
This keeps happening to me . I Flashed a braids and everything went fine. But with elements it keeps stopping at random times while writing.
I'm using the Vagrant environment.
If anyone has any tips I would really appreciate it.

vagrant@vagrant-ubuntu-trusty-64:/vagrant/eurorack-modules$ make -f elements/makefile upload_combo_serial
python stmlib/programming/serial/stm32loader.py \
-p /dev/ftdi-usbserial \
-b 115200 \
-e -v \
-w build/elements/elements_bootloader_combo.bin
Bootloader version 31
Chip id `['0x4', '0x13']'
Global mass erase; this may take a while
Write 256 bytes at 0x8000000
Write 256 bytes at 0x8000100
Write 256 bytes at 0x8000200
Write 256 bytes at 0x8000300
Write 256 bytes at 0x8000400
Write 256 bytes at 0x8000500
Write 256 bytes at 0x8000600
Write 256 bytes at 0x8000700
Write 256 bytes at 0x8000800
Write 256 bytes at 0x8000900
Write 256 bytes at 0x8000A00
Write 256 bytes at 0x8000B00
Write 256 bytes at 0x8000C00
Traceback (most recent call last):
File "stmlib/programming/serial/stm32loader.py", line 428, in <module>
cmd.writeMemory(conf['address'], data)
File "stmlib/programming/serial/stm32loader.py", line 307, in writeMemory
self.cmdWriteMemory(addr, data[offs:offs+256])
File "stmlib/programming/serial/stm32loader.py", line 188, in cmdWriteMemory
self._wait_for_ack("0x31 programming failed")
File "stmlib/programming/serial/stm32loader.py", line 69, in _wait_for_ack
raise CmdException("No response to %s" % info)
__main__.CmdException: No response to 0x31 programming failed
make: *** [upload_combo_serial] Error 1


I'm having the exact same problem atm. Did you figure out the reason?

Tried with lower baudrate, but no success.

EDIT:

The strange thing is, that it happens at diffrent time in the upload every time.
MUFF WIGGLER Forum Index -> Music Tech DIY Goto page 1, 2, 3, 4, 5, 6  Next [all]
Page 1 of 6
Powered by phpBB © phpBB Group