Trouble updating the Firmware (v1.019)

Discuss use it and firmware update
  • I may have found the culprit, and it is not with the NAVA.

    I believe the problem stems from the garbage USB/MIDI cable that I purchased. I figured that since I never use MIDI, and would only be using the adapter for intermittent firmware updates, I bought one of those cheap interfaces off of evilbay.

    I finally found this website. Took apart my so called "interface", and it looks EXACTLY the same. :roll:

    http://www.arvydas.co.uk/2013/07/cheap- ... -required/

    Even though the little egg has a blue light blinking as it "Sends" the sysex, I believe it is being corrupted somehow or not being sent in the correct format. As a result the NAVA knows something is happening, but does not understand it. That explains while it still knows to reboot when the data ceases uploading, but doesn't know what to do with said data.

    Chinese knockoffs +1

    Me +0

    Don't make the same mistake.

    I feel like an idiot. :|
  • I thought I was having the same issue and so upgraded my USB/midi cable. The Nava flashes when the new firmware is loading but when done it still says v1.018 and there are no changes. I've tried midiox, mios and c6 but no joy.
    Anyone have any ideas why the firmware doesn't change/upload?
  • Similar problem, very strange symptoms.

    I have two Nava's, each was running firmware 1.018.

    One Nava was successfully updated to 1.020 using Bome's SendSX, with the sending speed set to the slowest speed, using an EMU USB to MIDI adaptor with both MIDI In & MIDI Out connected to the Nava. It succeeded on the 2nd or 3rd try.

    The other Nava I have tried sending the latest firmware (1.020) repeatedly -- dozens of times now, using all sorts of settings in Midi OX and Bome's SendSX. It refuses to update -- it completes the sysex send successfully (it resets after led's for steps 9,6,5, and 3 are lit), but remains 1.018 version.

    I have been attempting to send the sysex from both the EMU adaptor that previously worked, as well as a PreSonus Firewire interface. Nothing seems to work.

    I thought perhaps there is some error somehow with the Nava that wouldn't update. So I swapped the ATMega1284P's. The 1.020 version ATmega chip was successfully transplanted into the Nava that wouldn't update. The 1.018 Atmega chip that wouldn't update was transplanted to the Nava that successfully updated the other Atmega to 1.020. But the remaining 1.018 Atmega still won't update in either Nava. It doesn't make any sense.

    Could it be that one ATmega chip is missing a bootloader or some such thing, and the other was not?
  • interesting, so it looks like the Atmega is the cause, or the boot loader isn't there.
    I've tried and tried again using different sysex software. Very frustrating.
  • I strongly suspect that there is something wrong with our ATMEGA1284p, but I'm not experienced enough to be certain.

    I have an Arduino Uno I've been trying to use as an ISP, to erase and re-program the 1284P that won't accept the sysex firmware update, but I have had no success. I'm using Arduino IDE 1.0.1. I've got the 1284P properly set-up on a breadboard and wired to the Arduino as directed on the maniacbug 1284p page here: https://maniacbug.wordpress.com/2011/11 ... ga1284p-4/ -- except that I have no separate FTDI or USB to TTL interface, and am unclear if I need one? With the ArduinoISP sketch loaded on the Arduino, I can use avrdude and read the 1284P and see it's current fuse settings. But the IDE won't burn the Mighty1284p bootloader (fails verification). Attempts with avrdude to manually change fuse bytes fail verification and they simply remain the same. Attempts to upload the 1.017 firmware source files with Arduino IDE 1.0.1 throws up loads of errors just during the code compile, before even attempting upload. Any tips appreciated...very new to Arduino..
  • Im here to say that i successfully updated nava firmware via "cheap chinease usb-midi cable" with the following settings:

    1. Latest Linux OS
    2. Increasing sysex interval to 20ms.

    So the command line should looks like this (you can list your devices with "amidi -l" command):

    amidi -p hw:1,0,0 -i 20 -s Nava_v1_023.syx

    The nava was flashed successfully after increasing "sysex interval" to 20ms. (I tried also 5ms.. 10ms.. and all that fails).
    Just wanted to share this "upload firmware" instruction to make life easier for everyone.
  • There are a few, to not say a lot of, MIDI/USB interfaces which can fail to transmit SysEx. I specifically use a Midiman/M-audio Midisport for all SysEx firmware shits because I'm sure it works.