Trouble uploading firmware image
Jim Halfpenny
I uploaded a copy of the V2 firmware before I compiled in minixfs support. I can't seem to upload firmware any more, from the web console or via tftp. Does anyone have any tips or tricks for getting around this?
It's worth noting that syslogd dies when I try to upload firmware via http. I don't know if this is a clue as to the problems I'm seeing.
Regards,
Jim
jim.ha...@gmail.com
firmware image is missing the upgrade_firmware binary! All is not
lost, as I used netcat to install the missing files and upgraded the
firmware manually. This is a trick worth knowing, so I'll document
this when I get a minute.
Needless so say I've found this pretty big bug in the V2 firmware. You
might want to wait for the next build before testing!
Regards,
Jim
Marco Vedovati
Il giorno 24/mag/07, alle ore 19:27, jim.ha...@gmail.com ha scritto:
>
> Bad form to reply to your own posts, but I got round this issue.
> ...
> Needless so say I've found this pretty big bug in the V2 firmware. You
> might want to wait for the next build before testing!
Hi Jim, sorry but I wasn't able to answer you before than now.
So, have u solved your problems?
Some useful infos:
- there are 2 levels of code pattern in the firmware. One is just at
the in the first bytes of the upgrade_code.bin binary. This pattern
is being added by addpattern.
The other, is hardcoded in upgrade_firmware and in tftpd.
In this cases you need to use the binaries from the original v2
firmware. You have to pay attention at this.
- things about wireless are in router/lib/modules/.../drivers/net and
in router/ti_ap, and in the linux/... folder there are no binary
drivers.
-you should use the mksquashfs from neptune354 (in tools/) because it
is updated to version 3 and provide a better compression. You need to
change also these files in kernel tree(by memory):
linux/include/linux/squashfs*
linux/fs/squashfs
Just a question: what are the other differences of the 2 kernel
versions?
If your firmware is working, I will make it available on my site,
just tell me.
Finally, if you have some knowledge of svn, or u wanna learn it, you
could add to neptune354 the ability to build v2 images.
cheers
marco
Jim Halfpenny
I managed to fix my problem, I used nc to copy the firmware and upgrade_image to /tmp and ran the update manually. The V2 code works great, I've tested most of the major functions. You can get a copy from here.
http://wiki.techesolution.com/neptune354/upgrade_code.bin
I can work on getting the V2 code into subversion. Should we create a new svn repository?
Regards,
Jim
Marco Vedovati
Hi Marco,
I managed to fix my problem, I used nc to copy the firmware and upgrade_image to /tmp and ran the update manually. The V2 code works great, I've tested most of the major functions. You can get a copy from here.
http://wiki.techesolution.com/neptune354/upgrade_code.bin
I can work on getting the V2 code into subversion. Should we create a new svn repository?
Jim Halfpenny
Hi,Have you tested the firmware upgrade both from web interface and tftpd?
Yes. I've upgraded via HTTP and I just bought 5 bricked V2s and unbricked them using tftp. I am going to sell some of them on eBay with Neptune354 pre-installed. Would it be rude to advertise the eBay auction on the Neptune354 mailing list?
no! Just add the folders containing drivers for the V2, and then do some changes in the Makefiles, in orders to use the proper drivers and tools to build the firmware...
Of course! No need to create more work for us, maintaining two codebases. I've also got some additional tips for unbricking WAG354G routers, another thing to document....
cheersmarco
Cheers!
Jim
Marco Vedovati
> Yes. I've upgraded via HTTP and I just bought 5 bricked V2s and unbricked
> them using tftp. I am going to sell some of them on eBay with Neptune354
> pre-installed. Would it be rude to advertise the eBay auction on the
> Neptune354 mailing list?
Well, this is a developers mailing list, and since here developers
work for free, they are happy if at least the hardware they are
working on is free or cheap too :)
Anyway, if you put on ebay wag354 with neptune354, please write that
neptune354 is available for free, and add a link for it.
> >
> > no! Just add the folders containing drivers for the V2, and then do some
> changes in the Makefiles, in orders to use the proper drivers and tools to
> build the firmware...
>
> Of course! No need to create more work for us, maintaining two codebases.
> I've also got some additional tips for unbricking WAG354G routers, another
> thing to document....
>
ok, if you have any guide, I can put them on my site if u want!
Thank you for your work
cheers,
Marco
Jim Halfpenny
I've done a lot of work merging the source code for my build of the V2 firmware. I've got a small issue with the makefile for httpd but other than that the only problem I have is the kernel source. The avalanche chipset driver is installed under the kernel source tree and is different for V1 and V2. I don't really want to add another kernel source to the svn respository as it's pretty big.
I've got the latest versions of the V1 and V2 firmware from my source tree on my site. It contains some bug fixes and I've added dmesg to busybox so I can see kernel log messages.
http://wiki.techesolution.com/neptune354/neptune354_version1.bin
http://wiki.techesolution.com/neptune354/neptune354_version2.bin
Regards,
Jim
Marco Vedovati
> I've done a lot of work merging the source code for my build of the
> V2 firmware. I've got a small issue with the makefile for httpd but
> other than that the only problem I have is the kernel source. The
> avalanche chipset driver is installed under the kernel source tree
> and is different for V1 and V2. I don't really want to add another
> kernel source to the svn respository as it's pretty big.
>
Ok, at the moment I have uniformed the addpattern for the different
platforms. Read howto-target.txt for understand how to compile for
the right platform.
I have seen the kernel differences: the different folders are arch,
drivers and include. I think now the easiest solution is to add the
kernel tree for v2, even if source tree gets bigger.
>
> I've got the latest versions of the V1 and V2 firmware from my
> source tree on my site. It contains some bug fixes and I've added
> dmesg to busybox so I can see kernel log messages.
Ok, please track any change you do, so that it's easier to get a
changelog.
cheers
marco