Author |
ADDAC207 - Firmware Upgrade Process: Issues / Questions |
br>ADDAC System |
br>Dear all,
Hope everyone is well.
Following up the 207 threads we decided to create 2 threads for these matters!
This thread has to do only with Firmware upgrades related issues, errors, doubts, connections, etc.
For us to be able to help please keep your posts informative, tell us which platform you're using (win/mac), which serial-usb device you're using and how you're making your connections.
Also created another thread for any bug reporting on the latest Firmware.
https://www.muffwiggler.com/forum/viewtopic.php?p=1689585#1689585
With these 2 threads we can separate any issues that may arise from these processes.
RELATED LINKS (edited July 5th, 2017):
Version K_4
Here's the direct link for our current Firmware Upgrade Guide:
http://addacsystem.com/firmwares/ADDAC207_Firmware_Rev4.pdf
All other download links can be found in the pdf.
K_4 updates:
.Corrected issue with saving and loading presets.
all the very best
andre br> br> |
|
br>meatbeatz |
br>Excellent! Andre, could you please give us an idiot proof rundown on the upgrade procedure via the Mac app? The instructions for the app aren't included in the firmware guide. Is it as simple as making the connections, following the prompts on the app, then powering up at the precise moment as pressing 'upgrade firmware' button?
Also the link to the Mac app appears to be broken. EDIT: Fixed br> br> |
|
br>ADDAC System |
br>Yes, the Mac App is self-explanatory.
Just make all connections like described in the .pdf guide, click through the App, power the synth when the App tells you to and that should be it!
all the very best
andre br> br> |
|
br>stega |
br>Ok I think I have done the update procedure properly.. Is there any way to tell what firmware is loaded by looking at the module??
The text below is what the updater read...
+ ------------------------------------------------------- +
#### ### ### #### ####
# # # # # # # # #
#### # # # # #### #
# # # # # # # # #
# # ### ### # # ####
#### # # #### ##### #### ### ###
# # # # # # # # #
#### #### #### # ## # # #
# # # # # # # #
#### #### #### # #### # # #
+ ------------------------------------------------------- +
ADDAC207 Firmware Update . version : I3
USB-Serial Device Found: /dev/tty.usbserial-A9G7R95D
+ ------------------------------------------------------- +
Starting Check List:
Arduino Installed
Double Checked connections!
Initializing the upgrade process:
Burning new Firmware!
(USB-Serial Board Leds should be blinking by now)
+ ------------------------------------------------------- +
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x1e950f
avrdude: reading input file "ADDAC207_L_3.hex"
avrdude: input file ADDAC207_L_3.hex auto detected as Intel Hex
avrdude: writing flash (30074 bytes):
Writing | ################################################## | 100% 15.02s
avrdude: 30074 bytes of flash written
avrdude: verifying flash memory against ADDAC207_L_3.hex:
avrdude: load data flash data from input file ADDAC207_L_3.hex:
avrdude: input file ADDAC207_L_3.hex auto detected as Intel Hex
avrdude: input file ADDAC207_L_3.hex contains 30074 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 12.73s
avrdude: verifying ...
avrdude: 30074 bytes of flash verified
avrdude done. Thank you.
+ ------------------------------------------------------- +
All Done!
Happy Patching!
+ ----------------------------------- + ADDAC System.2014 + br> br> |
|
br>meatbeatz |
br>I get the same as I got previously:
Quote: | avrdude: ser open (): can't open device "-b": No such file or directory
ioctl("TIOCMGET"): Operation not supported by device
avrdude done. Thank you. |
I'm using the Mac app with an Arduino UNO. I've installed the Arduino App and selected the Board (Arduino UNO) and Serial Port (/dev/tty.usbmodem3d11) so the device is showing up on the Arduino App. I've tried both TX>RX/RX>TX and RX>RX/TX>TX.
I wonder if I've messed with something in the Mac Terminal when I originally tried updating manually on the same computer.. I'm not a Mac person so I don't know enough about it. There's obviously something missing in the upgrade process if I'm getting the above message as I've done everything to the letter a dozen or so times.
stega since updating have you noticed an improvement with triggering all four channels simultaneously? br> br> |
|
br>Hirsbro |
br>I not tried the latest firmware but can you confirm that I did it the right way last time I did it please.. see vid of how I did it.
I would like to know before I try the latest firmware and get my hopes up.
br> br> |
|
br>Hirsbro |
br>so..? br> br> |
|
br>Refund |
br>all the documentation makes complete sense to me, but if it's possible for someone to make a video showing an example of the 'timing' showing how the the "upload then 'immediately' turn on of the module" step is done, that would make me feel a whole lot more comfortable with the process
I probably won't have the usb/serial adapter for another week so I'm hoping someone can do a video before then br> br> |
|
br>Hirsbro |
br> Refund wrote: | all the documentation makes complete sense to me, but if it's possible for someone to make a video showing an example of the 'timing' showing how the the "upload then 'immediately' turn on of the module" step is done, that would make me feel a whole lot more comfortable with the process
I probably won't have the usb/serial adapter for another week so I'm hoping someone can do a video before then |
did you watch my video? it shows when I turn on the module and my upload was successful br> br> |
|
br>__ag |
br>Hello,
Thanks for the video Hirsbro!
all the very best
andre br> br> |
|
br>Refund |
br> Hirsbro wrote: | Refund wrote: | all the documentation makes complete sense to me, but if it's possible for someone to make a video showing an example of the 'timing' showing how the the "upload then 'immediately' turn on of the module" step is done, that would make me feel a whole lot more comfortable with the process
I probably won't have the usb/serial adapter for another week so I'm hoping someone can do a video before then |
did you watch my video? it shows when I turn on the module and my upload was successful  |
cheers! br> br> |
|
br>overjoid |
br>Hello -
As I understand it, with the new firmware, using "trig.R" menu - button 2, you can turn off CV-detection/interval-creation. Fantastic.
Waiting on a serial adapter, I'm wondering exactly what's changed about gate detection.
With the new firmware, will it be able to handle exceedingly slow music without switching over to un-triggered operation? (. . . without it "thinking" there are no gates coming?)
I'd like some of my notes to last several minutes before the next trigger. Ideally shouldn't be a problem with a digital quantizer.
cheers br> br> |
|
br>Refund |
br>the firmware seemed to update just fine
but I can't seem to get the button 2 (assuming this means the c# button) to toggle on and off to indicate whether it is/isn't tracking channels 234 from channel 1
edit:
I figured it out
in the windows software section of the firmware update pdf, there is a link to the hex file you're supposed to use, but it links to an older version of the hex file (this is an error in the document)
the version you need to upload is the one linked in the post, and not the one erronously listed in the step by step document, they should fix it so that other people don't have the same problem down the line
edit 2:
also, the trigger repeat and ch234-slaved-to-1 options don't save between power cycles (have already tried saving it to preset 1 and it doesn't work)
it would be nice if it was able to be saved on startup br> br> |
|
br>__ag |
br>Hello,
I read through the last comments and made a new update (J_6) to save the CH234 slave to 1 setting in overall memory, so now it should keep your pre-defined setting after startup.
So with that setting off channels 234 will never be listening to channel one, with this long intervals between gates will not be a problem.
all the very best
andre br> br> |
|
br>Refund |
br>thank you! I'll try it now
edit: just updated to the windows hex j6 firmware and confirmed it went through, but it's still not saving ch234>1 settings
(also note that I saved settings to preset 1 just like before (and thanks for the quick reply)) br> br> |
|
br>Audio Dependent |
|
br>NS4W |
|
br>NS4W |
br>The manual of the module should be updated accordingly to the changes made. I think people are getting confused about where to get coherent and updated information about how the module works with the latest firmware. Just a suggestion! br> br> |
|
br>NS4W |
br>In other words, on the addac homepage the latest manual revision is dated July 2013 - please make a manual for J9 firmware br> br> |
|
br>Hirsbro |
br> NS4W wrote: | In other words, on the addac homepage the latest manual revision is dated July 2013 - please make a manual for J9 firmware |
Yes please br> br> |
|
br>JJCarr |
br>yesssssssss, doing this tonight! br> br> |
|
br>Riggar |
br>Well I've spent a whole afternoon with this and got nowhere.
I've used 2 PCs and both a usb serial adapter and an arduino uno board (minus chip) - so that's 4 permutations and zilch, nader, nothing. Xloader just sits there saying uploading - and never changes.
Very frustrating.
Is there anyway of telling what version is in the machine? There seems to be various flashing lights etc. when I switch on.
No sure where I go from here? br> br> |
|
br>Riggar |
br>Sorted!
As I was thinking about it as I drifted off to sleep (as you do!) - this morning I thought I'd just check those leads from usb device to the addac 207 AND they were the wrong way around. Doh! If you do it check ya tx's and your rx's carefully!
Now up and fully loaded.
Now I know - the process is actually quite easy. br> br> |
|
br>meatbeatz |
br>Can anyone that has installed J9 firmware please confirm whether this has solved the issues with triggering all four channels simultaneously? br> br> |
|
br>meatbeatz |
br>In the first post on this thread it says:
Quote: | Here's the direct link to our Firmware Upgrade OSX App (vs: J9) - last update March 2nd, 2015: |
Yet this post was last updated on:
Quote: | Last edited by ADDAC System on Fri Oct 10, 2014 2:24 am; edited 2 times in total |
How can that be? Am I going crazy? If not, I'm about to!!!!!
So I download the J9 firmware via the above link, open in Mac OSX Finder to find that J9 firmware file was created was 6/8/2014.
There is no documentation for J9 but I have been told by Andre that all gate issues have been fixed with J9. Can somebody please set me straight? br> br> |
|