Mac Tutorial: How to compile and upload the firmware of MIs eurorack modules


#181

Where does “/dev/cu.Bluetooth-Incoming-Port” come from?

It doesn’t look like a serial adapter device at all!


#182

from
3.3. Enter: ls /dev/cu.*


#183

That bluetooth thing is some other built-in device.
On my Mac the FTDI adapter device looks like this: /dev/cu.usbserial-A703X3BL


#184

yes… but it’s nothing else starting with cu. is present on my dev folder


#185

Check the documentation for the USB serial adapter. Maybe it needs drivers to be installed on your computer?


#186

What adapter is it?


#187

this one:


#188

I don’t have this one but maybe try this: FTDI Virtual COM Port Drivers ?
But as understand OSX ships with FTDI drivers?


#189

yes… I tried several times with FTDI VCP drivers:
http://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriver_v2_3.dmg

but no success


#190

I have had problem with some of the FTDI drivers before, when running usb-dmx interfaces. This little tool sometimes work, http://www.dmxis.com/macdriverfix/. If it doesnt work, remember to re/enable the driver again.


#191

Mmm I work with 10.9… Maybe the more recent versions have built-in drivers that do not register the device in /dev?

Check this…


#192

after several hours of struggle… It finally worked!

I first I had to disable kext signing on El Capitan:

  • Rebooted and pressed CMD+R immediately after reboot to enter in Recovery Mode
  • Open Terminal from Recovery mode
  • Run the command csrutil enable --without kext
  • Reboot
  • Install following driver:

http://www.wch.cn/download/CH341SER_MAC_ZIP.html


#193

@denoise Apple strongly recommend you don’t do that, though, as you’ve just turned off part of their system security.

a|x


#194

And I wouldn’t install something from that URL. It doesn’t look that safe… (No https and .cn is not that great combination)


#195

well, too late.

at least 36.000 persons already installed the drivers:
https://www.youtube.com/results?search_query=http%3A%2F%2Fwww.wch.cn%2Fdownload%2FCH341SER_MAC_ZIP.html

for me the real security problem comes from Apple, restricting and taking control over important os aspects, forcing the user to open vulnerability holes.


#196

That reasoning doesn’t make sense to me but I agree that it sometimes can be painful to run unsupported, old software.
But modern operating systems are not designed to run old software. And it looks like the trend continues. Nowadays everyone just delivers “services”, not software. I realised this post went off topic. Sorry.


#197

I tried to get the toolchain working on a Macbook with OS 10.10 and Xcode 7.2 with no succes. I then switched to another Mac with 10.8 and xcode 4.6.3 (had to manually install/download the command line tools) and then it worked. I am suspecting my xcode/cmd lines tools was causing a problem, maybe somebody can confirm ?

There was still some confusion in the TOOLCHAIN_PATH. The first topic suggests /Users/§username§/arm-cs-tools/ but I had to remove the last /.


#198

Hi!
I get following error:
openocd -f stmlib/programming/jtag/interface_stlink-v2.cfg -f stmlib/programming/jtag/stm32f10x_hla.cfg -f stmlib/programming/jtag/prelude_f10x.cfg -f stmlib/programming/jtag/erase_f10x.cfg -c “flash write_bank 0 build/streams/streams_bootloader_combo.bin 0x0” -c “verify_image build/streams/streams_bootloader_combo.bin” -f stmlib/programming/jtag/postlude.cfg || openocd -f stmlib/programming/jtag/interface_stlink-v2.cfg -f stmlib/programming/jtag/stm32f10x_hla.cfg -f stmlib/programming/jtag/prelude_f10x.cfg -f stmlib/programming/jtag/erase_f10x.cfg -c “flash write_bank 0 build/streams/streams_bootloader_combo.bin 0x0” -c “verify_image build/streams/streams_bootloader_combo.bin” -f stmlib/programming/jtag/postlude.cfg
Open On-Chip Debugger 0.9.0 (2015-11-15-05:39)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
hla_jtag
adapter speed: 1000 kHz
adapter_nsrst_delay: 200
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v25 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.222543
Info : stm32.cpu: hardware has 6 breakpoints, 4 watchpoints
target state: halted
target halted due to debug-request, current mode: Handler SysTick
xPSR: 0x6100000f pc: 0x08005948 msp: 0x20000198
Info : device id = 0x20036410
Info : ignoring flash probed value, using configured bank size
Info : flash size = 128kbytes
stm32x mass erase complete
target state: halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x01000003 pc: 0xfffffffe msp: 0xffffffdc
target state: halted
target halted due to breakpoint, current mode: Handler HardFault
xPSR: 0x61000003 pc: 0x2000003a msp: 0xffffffdc
wrote 44188 bytes from file build/streams/streams_bootloader_combo.bin to flash bank 0 at offset 0x00000000 in 1.478076s (29.195 KiB/s)
target state: halted
target halted due to breakpoint, current mode: Handler HardFault
xPSR: 0x61000003 pc: 0x2000002e msp: 0xffffffdc
verified 44188 bytes in 0.658012s (65.580 KiB/s)
in procedure ‘reset’ called at file “stmlib/programming/jtag/postlude.cfg”, line 24
in procedure ‘ocd_bouncer’

Open On-Chip Debugger 0.9.0 (2015-11-15-05:39)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
hla_jtag
adapter speed: 1000 kHz
adapter_nsrst_delay: 200
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v25 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.224115
Info : stm32.cpu: hardware has 6 breakpoints, 4 watchpoints
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x81000000 pc: 0x0800648e msp: 0x20000200
Info : device id = 0x20036410
Info : ignoring flash probed value, using configured bank size
Info : flash size = 128kbytes
stm32x mass erase complete
target state: halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x01000003 pc: 0xfffffffe msp: 0xffffffdc
target state: halted
target halted due to breakpoint, current mode: Handler HardFault
xPSR: 0x61000003 pc: 0x2000003a msp: 0xffffffdc
wrote 44188 bytes from file build/streams/streams_bootloader_combo.bin to flash bank 0 at offset 0x00000000 in 1.476860s (29.219 KiB/s)
target state: halted
target halted due to breakpoint, current mode: Handler HardFault
xPSR: 0x61000003 pc: 0x2000002e msp: 0xffffffdc
verified 44188 bytes in 0.656230s (65.758 KiB/s)
in procedure ‘reset’ called at file “stmlib/programming/jtag/postlude.cfg”, line 24
in procedure ‘ocd_bouncer’

make: ***** [upload_combo_jtag] Error 1

the st-link cant be found with ls /dev/tty* either. Any suggestions?

However the module worked in the end :slight_smile:


#199

Can anyone help with that please? Stuck when making wav file, here’s the output:

python stm_audio_bootloader/qpsk/encoder.py
-t stm32f4 -s 48000 -b 12000 -c 6000 -p 256
build/clouds/clouds.bin
Traceback (most recent call last):
File “stm_audio_bootloader/qpsk/encoder.py”, line 35, in
from stm_audio_bootloader import audio_stream_writer
ImportError: No module named stm_audio_bootloader
make: *** [wav] Error 1

Thanks!


#200

Hey Hal,
What hardware are you trying to run this on? I only ask because after a system update about 6 months ago, my 2013 MBAir just stopped talking to my ftdi friend all together. It had been working before, I gave up for a long time, tried on a newer machine and boom, it just worked first go. I haven’t had any problems outputting a .wav though. Are you using the current mutable cozy environment?

also, what command are you feeding to build the .wav file?

“ImportError: No module named stm_audio_bootloader” is throwing me