Page 1 of 4

firmware update problem 1.017 -> 1.0xx

Posted: Dec 15th, '16, 03:45
by junk16
hello,

I have finished assemble Nava, and I tried to update firmware because my Nava firmware is 1.017.
however, its still 1.017, it seems Nava firmware is not updated.

I have only mac, so I used 'sysex librarian' and 'C6', interfaces I used are 'roland UA25' and 'RME fireface 400'
these are my procedures.
・turn on power with holding 1, 3 and 5 switches.
・send sysex data through midi in directory from my mac.
・waiting finish sending data. while sending data, Nava switch led blink up to 9 switch led.
・nava restarted, but lcd display Nava 1.017.

I tried 1.0.18, 1.019 and 1.020, and change sending speed to slow,
and changing softwares, and change interfaces .
however, it same state.

I confirmed 'mid in' operation, its works fine, Nava is synced with x0xb0x and ableton live.

anyone knows what is the cause of this problem? its bootloader issue?

regards.

Re: firmware update problem 1.017 -> 1.0xx

Posted: Dec 28th, '16, 06:12
by junk16
I borrowed windows PC, and tried it.
however, firmware has still been 1.017. I can not update firmware.
I used MidiOx with setting buffer to 64 byte. I also used SendSX. but these do not help this issue.

EEprom is Micropchip 24LC1025.

I don't know what is happen. I suspect that is cause of boot loader.

Re: firmware update problem 1.017 -> 1.0xx

Posted: Dec 28th, '16, 17:25
by e-licktronic
Junk16,

do you have a ICSP burner to re-burn the bootloader ?

Best regards,
e-licktronic

Re: firmware update problem 1.017 -> 1.0xx

Posted: Dec 29th, '16, 00:55
by pistrix
I am really eager for a fix for this as well. One of my two Nava's updated successfully but the other would not after dozens of attempts of all different settings and software.

I have an Arduino Uno R3 which I believe can be used as an I(C)SP. I attempted to follow online directions to use Arduino Uno to burn a new bootloader to the Nava ATMEGA chip on a breadboard, but I couldn't get it to work. I could access the chip but couldn't successfully write anything to it, how to set the fuse bits and accomplish this is not very clear.

Your help would be very appreciated e-licktronic! Please help..

Re: firmware update problem 1.017 -> 1.0xx

Posted: Dec 29th, '16, 03:04
by junk16
e-licktronic

unfortunately, I don't have ICSP burner. but I found holes are described ICSP on nava main board, these are useful?
and I have Arduino Duemilanove, but this old one would work fine or not with ArduinoISP I don't know.

if using ArduinoISP, I should operate like following topic?
viewtopic.php?f=17&t=436

and which boot loader do I take? mighty-1284p?
https://github.com/maniacbug/mighty-1284p

please help.

regards.

Re: firmware update problem 1.017 -> 1.0xx

Posted: Dec 29th, '16, 16:24
by e-licktronic
Dear,

To burn the bootloader in your atmega1284p follow this instruction (only on Window):
-Open Arduino IDE and open the sketch "ArduinoISP" (file > example > ArduinoISP)
-Select the right serial port and Board then burn this sketch in your Arduino Board.
-Connect the Arduino ICSP connector to the Nava MainBoard ICSP connector (+5v to +5V, MISO to MISO...). You have to connect Nava ICSP RST pin to the Arduino digital pin 10. Do not connect Nava power supply !
More information about how to use Arduino as an ICSP programmer
-Download the "tools" Rar file provide in this topic
-Unrar in C:\
-Open the file "Nava_V1_020_All" in a text editor (notepad++ or others)
-By default the serial port is "COM4" but maybe yours is different. Write your serial port number on each line and save the file
-Now double click on the Nava_V1_020_All.bat file, a windows command window will open with the statue of burning process.
-Wait until the end
That's it ;)

Best regards,
e-licktronic
tools.rar (485.16 KiB)
Downloaded 1059 times

Re: firmware update problem 1.017 -> 1.0xx

Posted: Dec 29th, '16, 20:50
by Reggiechacha
can I use AVRISP mkII directly to the ICSP on the nava board?

http://www.atmel.com/tools/AVRISPMKII.aspx

I'm Totally new to this stuff...

Re: firmware update problem 1.017 -> 1.0xx

Posted: Dec 30th, '16, 01:12
by junk16
e-licktronic

Thank you for your informations!
I will try it later :D

Re: firmware update problem 1.017 -> 1.0xx

Posted: Dec 30th, '16, 04:18
by e-licktronic
Reggiechacha wrote:can I use AVRISP mkII directly to the ICSP on the nava board?

http://www.atmel.com/tools/AVRISPMKII.aspx

I'm Totally new to this stuff...

Of course you can, maybe you must change the programmer "avrisp" name in the *.bat file by "avrispmk2".
More information on how to use avrdude

Best regards,
e-licktronic

Re: firmware update problem 1.017 -> 1.0xx

Posted: Jan 4th, '17, 23:26
by pistrix
I'm still having problems.

My Nava firmware is 1.018 but also will not update.

When running the "Nava_v1_020_All.bat" file, avrdude has verification errors during two steps.

I have an Arduino Uno R3.

I have it connected to a Windows 7 64bit system, powered by the USB connection. It is set to COM 6.

Using Arduino IDE 1.0.1, I set "Arduino Uno" as my board, and selected my COM port (6). I loaded "Examples>ArduinoISP" and then selected "Upload".

My Arduino Uno has two sets of ICSP pins. I connected my Arduino ICSP to the Nava ICSP using the Arduino ICSP pins by the lower edge of the Arduino board. I connected 5v to 5v, MISO to MISO, MOSI to MOSI, GND to GND, and SCK to SCK. I connected Nava's "RST" pin to the digital pin 10 on the Arduino (& nowhere else).

After connecting the ICSP pins, the Nava LCD and sequencer powers on.

I unzipped the "Tools" file (to "c:\tools..), and edited the .bat file to reference my Arduino's com port. I then ran the .bat file, but it failed -- I had to add libusb0.dll (from the Arduino IDE folder) to the "tools" folder in order to get avrdude to function.

After adding the libusb0.dll file to the "c:\tools" folder, I ran the edited .bat file and avrdude gives me results.

The first step (lock data) fails verification. It also fails the verification of the Nava_v1_020.hex file. The other steps verify successfully.

Any help or further instructions very much appreciated...
C:\tools>C:\tools\bin\avrdude.exe -c avrisp -p m1284p -P COM6 -b 19200 -u -e -U
lock:w:0x3F:m -v

avrdude.exe: Version 6.1, compiled on Mar 13 2014 at 00:09:49
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

System wide configuration file is "C:\tools\bin\avrdude.conf"

Using Port : COM6
Using Programmer : avrisp
Overriding Baud Rate : 19200
AVR Part : ATmega1284P
Chip Erase delay : 55000 us
PAGEL : PD7
BS2 : PA0
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :

Block Poll Page
Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW
MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ -----
----- ---------
eeprom 65 10 128 0 no 4096 8 0 9000
9000 0xff 0xff
flash 65 10 256 0 yes 131072 256 512 4500
4500 0xff 0xff
lock 0 0 0 0 no 1 0 0 9000
9000 0x00 0x00
lfuse 0 0 0 0 no 1 0 0 9000
9000 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 9000
9000 0x00 0x00
efuse 0 0 0 0 no 1 0 0 9000
9000 0x00 0x00
signature 0 0 0 0 no 3 0 0 0
0 0x00 0x00
calibration 0 0 0 0 no 1 0 0 0
0 0x00 0x00

Programmer Type : STK500
Description : Atmel AVR ISP
Hardware Version: 2
Firmware Version: 1.18
Topcard : Unknown
Vtarget : 0.0 V
Varef : 0.0 V
Oscillator : Off
SCK period : 0.1 us

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.11s

avrdude.exe: Device signature = 0x1e9705
avrdude.exe: erasing chip
avrdude.exe: reading input file "0x3F"
avrdude.exe: writing lock (1 bytes):

Writing | | 0% 0.00s ***faile
d;
Writing | ################################################## | 100% 0.16s

avrdude.exe: 1 bytes of lock written
avrdude.exe: verifying lock memory against 0x3F:
avrdude.exe: load data lock data from input file 0x3F:
avrdude.exe: input file 0x3F contains 1 bytes
avrdude.exe: reading on-chip lock data:

Reading | ################################################## | 100% 0.02s

avrdude.exe: verifying ...
avrdude.exe: verification error, first mismatch at byte 0x0000
0x0f != 0x3f
avrdude.exe: verification error; content mismatch