Announce Thread: Magpie Modular - uBraids - Braids in 8 HP.

[pld]

the 8 MHz crystal is for the STM32
the 16mhz resonator is for the atmega328

Ok, that's probably the detail I missed by not actually building one: I scanned for '16MHz' in the BOM, but "16MHz resonator" != "16MHz quarz" and IIRC needs different fuses.

[gimber]

For those who used the FTDI Friend and Vagrant Environment to flash the firmware, did the programmer need to be defined, as mentioned in this link?

If so, are the commands available anywhere to specify an FTDI Friend instead of AVR/JTAG etc?

Do any traces need to be modified on the FTDI Friend for this to work?

[Southfork]

For those who used the FTDI Friend and Vagrant Environment to flash the firmware, did the programmer need to be defined, as mentioned in this link?

If so, are the commands available anywhere to specify an FTDI Friend instead of AVR/JTAG etc?

Do any traces need to be modified on the FTDI Friend for this to work?

Not for me at least, the tool chain looks for usb serial. Just do the upload serial command in vagrant. Most importantly don't forget to solder the 3v jumper on the ftdi friend.

[diablojoy]

Well physical build is done it didn't go perfectly oh yeah that STM is a bitch to do had to do a repair to pin 9 VDDA and luckily pin 10 WKUP isn't used the rest was easy enough, but we shall see. now for programming
the bit I actually dreaded most from the start.

[$XxxxX$]

the next one I'm tackling is Frames.

Yesh!

double in a cart.

[gimber]

Not for me at least, the tool chain looks for usb serial. Just do the upload serial command in vagrant. Most importantly don't forget to solder the 3v jumper on the ftdi friend.

Thanks! That gets my FTDI talking to the module.

Now it gets though "Write 256 bytes at 0x8000000" to somewhere around "Write 256 bytes at 0x800E000" then gives these errors (it stops at a different point every time):

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

Tried on a mac (updated drivers per earlier in this thread) and windows, each the same. Anyone else run into this?

[ArguZ]

Any news on the display problem ?
I seen a video of someone flicking through the different modes and it acted much faster than mine.
I could not extract any useful information from him though,.
I wish the whole flashing process of the AVR would be a bit more documented.
By the way :
http://www.st.com/content/st_com/en/pro ... stm32.html
Nice GUI tool if you do not want to waste your life on command line stuff.

[gimber]

By the way :
http://www.st.com/content/st_com/en/pro ... stm32.html
Nice GUI tool if you do not want to waste your life on command line stuff.

That worked, first try - thank you!
I now have audio, but seem to be having the same screen issue as qual: example sketches work, but the microbraids sketch throws a noise pattern onto the screen for a second then goes black.

I'm using the Sparkfun Pocket AVR programmer.
In Arduino I have set:
Board: Arduino Pro or Pro Mini
Processor: ATmega328 (5v, 16mhz)
Programmer: USBtinyISP

[phidelity]

phidelity could you update the mouser BOM with the apparently missing parts as commented by qual, maybe check if other things are missing, and drop a line here afterwards?

Sorry, I've been pulled in a million directions at once in my life. I've been following this thread and updating the BOM as I see things that were incorrect.

[phidelity]

Where did you get those shiny aluminum knobs for these?

I stole that from a Noise Engineering module. I have plans to source these and have my own version made - when my life calms down a little, but of course you need to make sizable purchase in the thousands.

[phidelity]

You are absolutely right... Not exactly sure how this qualifies as "Share Alike"

Sorry, I am a total github newb and I thought I had uploaded the proper files and unfortunately I didnt merge the branches. This should be corrected now.

[phidelity]

I'm running El Capitan and was having an issue with my FTDI Friend (that sounds so sad) timing out in the middle of a load, but cured this by updating the drivers at Prolific - here's the link

http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=229&pcid=41

Hope that helps

I've had this issue when using the programmer through a USB hub, If you are using that definitely go straight from a port.

[phidelity]

Hi guys,

i just finished my first one and it is at 99% i think.
CV in and sound is all good, i uploaded my inverted encoder driver via aufio in, that is also good.
I flashed the 328 via Arduino IDE and i have a display but some parts of the letters seem to be unstable...fluctuating.
Solder error or firmware problem ?
The OLED also is kinda slow , from a personal point of view, not sure if that means anything.
-

Yeah the refresh rate is off on some of the ones I have built as well. Im in the middle of trouble shooting this and Should hopefully have a fix soon after I A/B it with working modules.

[phidelity]

Not for me at least, the tool chain looks for usb serial. Just do the upload serial command in vagrant. Most importantly don't forget to solder the 3v jumper on the ftdi friend.

Thanks! That gets my FTDI talking to the module.

Now it gets though "Write 256 bytes at 0x8000000" to somewhere around "Write 256 bytes at 0x800E000" then gives these errors (it stops at a different point every time):

I had this problem when I was trying to flash over a USB hub. Plugging the programmer directly into a port on the computer solved this for me.

[phidelity]

Hi Guys,
Sorry to be absent in this thread. I think the main culprit can be partially blamed on the horrible documentation. I will be rewriting this with better instructions. Ive solved the display problem on my end with these steps.

Basically it was forgetting to burn the Bootloader before uploading the code. So here are the updated instructions for flashing from the Arduino app

1) Install your 3 arduino libraries
2) Install the library for your programmer of choice
3) Select Arduino / Geniuno Uno in board
4) Select your programmer
5) Burn Bootloader - (via Tools/Burn Bootloader) I Got an error about the fuse usage being deprecated - we will fix this but for now it seems to work
6) Upload via programmer

and Voila! Your screen should be updating at a much faster speed, if you have crazy lines or glitches then check downstream for bad joints.

I will be looking at the footprint issue and trying to find a proper chip or redoing the board in a future revision.

[ArguZ]

Hi guys,

i just finished my first one and it is at 99% i think.
CV in and sound is all good, i uploaded my inverted encoder driver via aufio in, that is also good.
I flashed the 328 via Arduino IDE and i have a display but some parts of the letters seem to be unstable...fluctuating.
Solder error or firmware problem ?
The OLED also is kinda slow , from a personal point of view, not sure if that means anything.
-

Yeah the refresh rate is off on some of the ones I have built as well. Im in the middle of trouble shooting this and Should hopefully have a fix soon after I A/B it with working modules.

Hey, so you can confirm that this sounds like a software problem at this point ?

[Southfork]

Not for me at least, the tool chain looks for usb serial. Just do the upload serial command in vagrant. Most importantly don't forget to solder the 3v jumper on the ftdi friend.

Thanks! That gets my FTDI talking to the module.

Now it gets though "Write 256 bytes at 0x8000000" to somewhere around "Write 256 bytes at 0x800E000" then gives these errors (it stops at a different point every time):

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

Tried on a mac (updated drivers per earlier in this thread) and windows, each the same. Anyone else run into this?

As I mentioned earlier for me the new drivers didn't solve the connection problem with ftdi and mcu. I've tried everything and think it is a fault with drivers under el Capistan. Still using brute force method and keep trying upload and eventually it's successful, not ideal but I'm only using ftdi on ubraids, the rest of the mutable builds I use jtag :(

[phidelity]

Hi guys,

i just finished my first one and it is at 99% i think.
CV in and sound is all good, i uploaded my inverted encoder driver via aufio in, that is also good.
I flashed the 328 via Arduino IDE and i have a display but some parts of the letters seem to be unstable...fluctuating.
Solder error or firmware problem ?
The OLED also is kinda slow , from a personal point of view, not sure if that means anything.
-

Yeah the refresh rate is off on some of the ones I have built as well. Im in the middle of trouble shooting this and Should hopefully have a fix soon after I A/B it with working modules.

Hey, so you can confirm that this sounds like a software problem at this point ?

No, but what I can confirm is that if you don't burn your bootloader it will exhibit the slow refresh rate everyone is experiencing. I posted some instructions a few posts up and will be updating the build guide.

[phidelity]

Not for me at least, the tool chain looks for usb serial. Just do the upload serial command in vagrant. Most importantly don't forget to solder the 3v jumper on the ftdi friend.

Thanks! That gets my FTDI talking to the module.

Now it gets though "Write 256 bytes at 0x8000000" to somewhere around "Write 256 bytes at 0x800E000" then gives these errors (it stops at a different point every time):

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

Tried on a mac (updated drivers per earlier in this thread) and windows, each the same. Anyone else run into this?

As I mentioned earlier for me the new drivers didn't solve the connection problem with ftdi and mcu. I've tried everything and think it is a fault with drivers under el Capistan. Still using brute force method and keep trying upload and eventually it's successful, not ideal but I'm only using ftdi on ubraids, the rest of the mutable builds I use jtag :(

Can you confirm that you are NOT using a USB hub and programming directly from a port on the computer? I spent a while with the exact same issue and realize it stemmed from a USB hub.

[diablojoy]

Hi phidelity
can you list the correct fuse settings and clock setting for the atmega328
please

[Southfork]

Not for me at least, the tool chain looks for usb serial. Just do the upload serial command in vagrant. Most importantly don't forget to solder the 3v jumper on the ftdi friend.

Thanks! That gets my FTDI talking to the module.

Now it gets though "Write 256 bytes at 0x8000000" to somewhere around "Write 256 bytes at 0x800E000" then gives these errors (it stops at a different point every time):

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

Tried on a mac (updated drivers per earlier in this thread) and windows, each the same. Anyone else run into this?

As I mentioned earlier for me the new drivers didn't solve the connection problem with ftdi and mcu. I've tried everything and think it is a fault with drivers under el Capistan. Still using brute force method and keep trying upload and eventually it's successful, not ideal but I'm only using ftdi on ubraids, the rest of the mutable builds I use jtag :(

Can you confirm that you are NOT using a USB hub and programming directly from a port on the computer? I spent a while with the exact same issue and realize it stemmed from a USB hub.

Yes straight from the USB port (no hub), I've had this issue with using ftdi on all mutable builds on my Mac :(

[phidelity]

Hi phidelity
can you list the correct fuse settings and clock setting for the atmega328
please

I am not currently changing anything in the clock or fuse settings in order to flash the atmega. It *should* work right out of the box with the supplied instructions and the arduino app.

[ArguZ]

YYYESS !!

Now they work , crisp and stable

Let me post Kris's correct step by step guide

1) Install your 3 arduino libraries
2) Install the library for your programmer of choice
3) Select Arduino / Geniuno Uno in board
4) Select your programmer
5) Burn Bootloader - I Got an error about the fuse usage being deprecated - we will fix this but for now it seems to work
6) Upload via programmer

Without step 5 you end up having a sloppy one.

[greeensmaaan]

You are absolutely right... Not exactly sure how this qualifies as "Share Alike"

Sorry, I am a total github newb and I thought I had uploaded the proper files and unfortunately I didnt merge the branches. This should be corrected now.

No need to be sorry! I am sorry for coming off confrontational about the whole thing, I was just remembering the whole THC situation and was a bit skeptical... Glad to see you have gotten everything sorted and I am looking forward to building a few!

[ZZ Ardoz]

YYYESS !!

Now they work , crisp and stable

Let me post Kris's correct step by step guide

1) Install your 3 arduino libraries
2) Install the library for your programmer of choice
3) Select Arduino / Geniuno Uno in board
4) Select your programmer
5) Burn Bootloader - I Got an error about the fuse usage being deprecated - we will fix this but for now it seems to work
6) Upload via programmer

Without step 5 you end up having a sloppy one.

Hoorah!!!!! So snappy now - thanks a tone for this!