2013-12-26 20:07:05 UTC
I've got a TS2100 that failed to install/write a flash image of v 4.1
(using firmware from http://ko4bb.com/). Looking at the tcpdump of the
packets in flight, I get the sense that the TS2100 isn't liking what
I've got to offer it (I'm assuming it's checking for SREC format, not
finding it, and aborts the transfer). After several failed attempts
to copy the image over (tried atftpd on linux, tftpd on fbsd and
osx...), I lost power and the unit is now setting on console port
only, using the v1.x recovery rom image. So, access is there, network
stack is up, etc. I tried again from the recovery image to copy over v
4.1 to flash -- to avail.
Of course, after this failed to work, I noticed that ko4bb's archive
of v 4.1 isn't SREC format (and I see many ref'x to the .HEX files as
having been provided in SREC format). It looks like what I've got is
an actual raw binary image of the executable code, not the SREC
So, does a guy have to covert this binary to SREC himself, or is there
something I can nab right-quick online?
...better yet: can anyone confirm the zip archive on kobb.com is
legit, and not corrupt?