Discussion:
recovering firmware on TS2100
(too old to reply)
Anton Kapela
2013-12-26 20:07:05 UTC
Permalink
Fellow nuts,

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
equivalent.

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?

Best,

-Tk
Scott McGrath
2013-12-28 02:40:11 UTC
Permalink
Check out

Srecord.sourceforge.net. Version 1.62 is current. You will need to build it as this is provided as source code only. It can be built for windows using Cygwin

Sent from my iPhone
Post by Anton Kapela
Fellow nuts,
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
equivalent.
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?
Best,
-Tk
_______________________________________________
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Azelio Boriani
2013-12-27 23:28:29 UTC
Permalink
You can use an EPROM programmer utility: usually these utilities can
load a binary file then you can save in Motorola SREC format. I use
the ELNEC software to translate from/to binary/HEX.
Post by Anton Kapela
Fellow nuts,
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
equivalent.
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?
Best,
-Tk
_______________________________________________
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Robert Watzlavick
2013-12-29 05:00:21 UTC
Permalink
Are you talking about the archive named DatumET-6000TS-2100.zip and the
file named Tymserve.bin? If so, I uploaded that file last year. It's a
direct ROM image from a flash reader/programmer. That's why I included
the device type (AMD 29F040B-120JC) in the readme.txt. You should be
able to restore your image using a flash programmer.

-Bob
Post by Anton Kapela
Fellow nuts,
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
equivalent.
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?
Best,
-Tk
_______________________________________________
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Anton Kapela
2013-12-29 15:09:41 UTC
Permalink
Rob,

On Sat, Dec 28, 2013 at 11:00 PM, Robert Watzlavick
Are you talking about the archive named DatumET-6000TS-2100.zip and the file
named Tymserve.bin?
Indeed, that's the file.
If so, I uploaded that file last year. It's a direct
ROM image from a flash reader/programmer.
Makes perfect sense.
That's why I included the device
type (AMD 29F040B-120JC) in the readme.txt. You should be able to restore
your image using a flash programmer.
Another list user had directed me to a SREC format of the same data;
TFTP transfer (using an IOS router as a host...fbsd/linux/osx tftpd's
weren't compatible w/ TS2100 v1.x tftp client) and update worked out
cleanly. I'll convert the binary to SREC for grins, see if it matches
;)

Thanks for the clarification,

-Tk
Robert Watzlavick
2013-12-29 21:44:25 UTC
Permalink
Glad to hear it worked out for you! That's also good to know about the
TFTP client compatibility with the TS2100.

-Bob
Post by Anton Kapela
Rob,
On Sat, Dec 28, 2013 at 11:00 PM, Robert Watzlavick
Are you talking about the archive named DatumET-6000TS-2100.zip and the file
named Tymserve.bin?
Indeed, that's the file.
If so, I uploaded that file last year. It's a direct
ROM image from a flash reader/programmer.
Makes perfect sense.
That's why I included the device
type (AMD 29F040B-120JC) in the readme.txt. You should be able to restore
your image using a flash programmer.
Another list user had directed me to a SREC format of the same data;
TFTP transfer (using an IOS router as a host...fbsd/linux/osx tftpd's
weren't compatible w/ TS2100 v1.x tftp client) and update worked out
cleanly. I'll convert the binary to SREC for grins, see if it matches
;)
Thanks for the clarification,
-Tk
_______________________________________________
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Didier Juges
2013-12-29 19:28:45 UTC
Permalink
Feel free to upload the srec file if it works :)

Didier KO4BB
Post by Anton Kapela
Rob,
On Sat, Dec 28, 2013 at 11:00 PM, Robert Watzlavick
Post by Robert Watzlavick
Are you talking about the archive named DatumET-6000TS-2100.zip and
the file
Post by Robert Watzlavick
named Tymserve.bin?
Indeed, that's the file.
Post by Robert Watzlavick
If so, I uploaded that file last year. It's a direct
ROM image from a flash reader/programmer.
Makes perfect sense.
Post by Robert Watzlavick
That's why I included the device
type (AMD 29F040B-120JC) in the readme.txt. You should be able to
restore
Post by Robert Watzlavick
your image using a flash programmer.
Another list user had directed me to a SREC format of the same data;
TFTP transfer (using an IOS router as a host...fbsd/linux/osx tftpd's
weren't compatible w/ TS2100 v1.x tftp client) and update worked out
cleanly. I'll convert the binary to SREC for grins, see if it matches
;)
Thanks for the clarification,
-Tk
_______________________________________________
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
--
Sent from my Motorola Droid Razr 4G LTE wireless tracker while I do other things.
Loading...