Remote Rig
RRC 1258 Support in English => General discussion forum => Topic started by: ea3in on 2011-01-05, 16:23:30
-
Can't upload formware 2.32
I get message: "Wrong file type, got 36, expected 35"
I have RCC's v1
Same behaviour in both the radio and control unit
I have downloaded the file twice.
Any idea?
HNY from Marcel, EA3IN
-
I got that when I selected "bootloader" rather than "application" to update. It updated properly, though, even with the error.
Joe, W4WT
-
Can't upload formware 2.32
I get message: "Wrong file type, got 36, expected 35"
I have RCC's v1
Same behaviour in both the radio and control unit
I have downloaded the file twice.
Any idea?
HNY from Marcel, EA3IN
Are you using the web interface? What is the name/URL of the file you are attempting to use?
36 is the bootloader's type, 35 is the main application firmware's type. So it looks like you are attempting to upgrade the main application firmware using a file which contains the bootloader.
-
The URl is
javascript:change_frames('update.htm','empty.htm')
I think I'm selecting application upgrade (as usual)
-
Sorry I miss the following
Yes, I am usin the wb interface
The downloaded file is:
http://www.remoterig.com/firmwares/RRC-1258-CRC_v2.32_2011-01-04.zip
-
That file is OK, as long as you select "Application upgrade" I can't see why it should fail. Which firmware version do you have now?
-
Current firmware is 2.30
-
I also tried to update the firmware using the setup manager utility. An error appears saying invalid file
I tried to re-load version 2.30. diiferent error code: Wrong file type, got 144, expected 35
Info on the RRC is:
Company Microbit
Product 1258
PID 0
Hardware 3
Software 2.30
Bootloader <= 1.7
Compiler 4.1.2 (WinARM 4/2007)
Build Dec 16 2010 14:37:11
ROM/RAM 343436/52960
ETH-RAM 2944 (max 3kB!)
ResetSrc 0 [3]
Uptime 113
Serial number 1548
MAC address 00:50:c2:11:8d:dc
IP address 192.168.0.227
Netmask 255.255.255.0
Gateway 192.168.1.1
DNS 213.27.248.53
-
I am now going to ask you a question that you might feel is stupid and unnecessary, so please don't consider me rude, but I want to rule out every possibility of errors here as this behaviour is something I haven't heard of before. Also since you get errors on both 2.30 and 2.32, both web and USB, the probability of both files being corrupt for you alone seems low: ;)
You have extracted the bin file inside the zip file and used that file(bin) when trying to update? On the download page 2.28 was the last file using the raw bin file format, from 2.30 we put the bin file inside a zip file as zip files have crc(checksum) which assures you download a non corrupted file.
-
Rude?
NOOOO, you right.
It was my mistake.
It is working now