All posts by moshang

MB firmware compatibility with Arduino 1.6.0

I’ve discovered to my shock that the type definition “prog_uchar” that I’ve been using to place data in SRAM has been deprecated in the latest version of the IDE (Arduino 1.6.0). It means that most of the firmware for the MB won’t compile in the latest IDE!

While I update the code, the work-around is to not use Arduino 1.6.0, but instead to use the version before – Arduino 1.0.6.  I’m working on a fix as we speak.

UPDATE

Done! 2015-03-13

And the latest IDE versio is no 1.6.1

Golf Firmware Update

I’ve made significant improvements to the Golf firmware for the MB.

The V026 firmware gives the Golf a heart transplant with a new interrupt based internal clock that is a lot more stable than before.

As MIDI slave the Golf also now responds promptly and reliably to incoming MIDI start messages.

The sequencer’s time division is now seperate from the clock (as slave or master). You can choose for the sequencer to to treat steps as 16th, 15th triplets, or 32nds.

Time divisions are save on a per pattern basis – when linking patterns, it’s possible to have patterns play back with different dime divisions.

Fire up the Golf with the V026 firmware and let me know if I’ve messed it up, or missed something.

Can’t find COM port for Arduino Due

It seems to be a common issue with the Arduino Due that after uploading firmware perfectly normally for a while, the computer suddenly can’t find the COM port for the Arduino Due anymore. It had me tearing out my hair at the start, but I think I’ve got it figured out.

First off, check which port is available in the Tools/Port drop down menu of the Arduino IDE, and see if it’s selected (on my machine the port sometimes changes). If there’s nothing there, try the following: if you’ve been using the programming port, try plugging the usb cable into the native port (or vice versa). It should pick it up on a different com port. Just remember to select the different board type from the drop down list at Tools/BoardArduino Due (Programming Port) vs Arduino Due (Native USB Port). And also make sure the port is selected in theTools/Port drop down menu.

Uploading firmware seems to jog the Due’s memory, so once you’ve uploaded the firmware using the different port, you should be able to go back to the port you used before if you prefer. I always use the native port since I don’t need serial communications with the PC and uploading is much faster. The only downside is that you often have to reset the board manually – you can hit the reset switch without removing the board (it’s next to the contrast trimmer for the LCD), so it’s not a big problem.