Home    Forum    Search    FAQ    Register    Log in


Post new topic  Reply to topic 
Page 1 of 3
Goto page 1, 2, 3  Next
 
BAD FIRMWARE UPGRADE
Author Message
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Hi Scisci,

Yes, I noticed you were successful with HWGuru. I got a little bit lost reading through.

I'd be gratefull if you could explain what wire goes where and any links etc. (English of course)

I am an extreme novice so it needs to be simple.. Smile

Although I was please I got as far as a working led test.

Cheers
 



 
View user's profileSend private message 
Back to topPage bottom
Thanks for the useful Topic Gilberto74:
frankteb (21 March) 
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Hello,
I try to resume what I did with the strong help of hwguru (almost all here is his deserve Wink ) in order to debrick my NAS DUAL SATA.
Please look at below links too in order to get the original post where we tracked the issue and the Installation procedure too.

Basically,
first of all I bought a jtag adapter on ebay (I bought (no advertisement for sure) Wink the kuzito one , check one like this :
http://cgi.ebay.it/JTAG-Programmato...8QQcmdZViewItem )
it worked perfectly for the NAS.

Then I had to solder a 20 pin connector at JP1 position, please check the upper left corner of figure

http://www.flickr.com/photos/[email protected]/2216009985/sizes/o/

Have a look at the R36 resistor near the left side of the storlink cpu...it is important too.
Basically it has the same rule of R160 for nas2000 equipment.

In order to reload redboot , you have to enable debug mode on this cpu, so you need to manage this resistor as I will explain shortly.

Take a look at http://forum.nas-forum.org/thread.php?threadid=22

here it is described how to connect jtag adapter cable at JP1 pins.

Basically you just need to connect:

1,2,17 = VDD =VREF = 3,3V
4 - GND
5 - TDI
7 - TMS
9 - TCK
13 - TDO

with the same connectors on jtag adapter.
About the R36, you have to connect the cpu side of it (let me say, the pin of resistor right near the cpu) short to VREF throuh a 100Ohm resistor in order to enable debug mode.
I attach two very bad pictures (sorry for that) to resume the connection of JTAG Adapter +B (in short with VREF) to R36 through the 100 Ohm resistor and very confused picture of this connection.

(jtag adapter red cable VREF goes to...


 Image


... R36 resistor connection through a 100Ohm resistor , see from left side of picture the red cable with resistor attached)


  Image
  
Then you have to follow the below link in order to program the flash.

http://www.nas-2000.org/mwiki/index...sh_through_JTAG (fro redboot procedure)

http://forum.nas-forum.org/thread.php?threadid=23  (for programming tool , thanks to hwguru again Wink )

Please note that I connected jtag cable to adapter only after start of nas. IT IS IMPORTANT because otherwise debug mode does not work!

About redboot, I used the version kindly given to me by lord scaffald. Please check this forum to get it too:

http://storlinkdevices.memoriedigitali.com/viewtopic.php?t=5


After redboot is ok, I followed the usual procedure to upload zImage, rd and hddapp of tinky-ls.

I hope this helps (for sure I cannot assure anything , Hope I was right Wink ...let me know if it works for you too.




http://forum.nas-forum.org/thread.php?threadid=72 (my thread with hwguru)
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Thanks scisci,

I will need to buy that jtag adapter and give it a shot.
Does it have to be that way or would making the cable work like it's shown at: http://forum.nas-forum.org/thread.php?threadid=12

Also, the 100Ohm resistor soldered to R36, does it have to be wired to the adapter like your pics show or can it go to R35 like : http://forum.nas-forum.org/thread.php?postid=406

Thx
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Hello,
as far as I know, the buffered should also protect you by any damages.
About the resistor, I tried R35&R36 connection but it didn't work. For sure it works on R36 to +B of jtag adpater with 100Ohm.

Bye! Smile
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
@ Gilberto74

I had a similar problem by pressing CTRL C and device not responding. Try to press it more than once while booting and it should work.
I suggest you to newly install any parts of the firmware before pressing 1.

Id did just install the Zimage and after this my device didnīt respond to telnet anymore.

The following procedure to debrick via jtag adapter was very annoying :lol:....

For me connecting R36 with R35 worked quite fine, even though I was really feeling uncomfortably for soldering right next to the CPU.

 I used this wiggler (18 €):
http://elmicro.com/files/olimex/arm-usb-ocd.pdf

and additionally used this free software tool:

http://www.olimex.com/dev/soft/arm/H-JTAG%20V0.2.rar

The NAS2000 flashtool didnīt show any response without the additional software but worked well with the H-Jtag running.

I started flashing, went into the kitchen to get me a beer and my cat jumped onto the working table and dropped the whole NAS straight to the ground.

 Shocked  Life is very bitter!!!  Shocked  

Hope you havenīt got a cat! Good luck

Chris
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Hi,

Even though I've ordered a jtag adapter, I thought I'd have another attempt at making a cable:

I've got a bit further as now in the FlashTool, I have:
Testing cabletype 1
JTAG-IDCODE: 0x00526fa1 - OK
Bypass-test: 0xaaab5554 - OK

Cable type 1 detected.
Error: Device is NOT in debug-mode.

I thought linking 1 and 17 should enable debug-mode.

So close yet so far away.  Sad
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Ok, I've now got it in debug-mode, BUT:

Refering to: http://nas-2000.org/mwiki/index.php...sh_through_JTAG

My details are:
Flash-Device_ID: 22cb-0000-0008
Flash type Bottom boot - OK

What's the difference between Top boot and Bottom boot?
Shall go ahead with flashing the bootloader?
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Another step further.
I'm now to the point that I can telnet and Press X to upgrade boot, etc.

Now I'm stuck.
I enter the tftfp server Ip address, then the location of the image file.
Then it sits there with 'waiting to retrieve file' then it times out.

I've tried loads of variations to the path but I just can't get it to find it, what am I doing wrong?
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Hi,
there are flash chips that have smaller sectors at the top or bottom.
eg top boot = 8x8k sectors at top, other sectors are 64k
That has to be considered by the flash software.
This message is only for information.

The easiest wat to use tftp is to have the files where you start the tftp server.
The filename must be typed in exactly! It is case sensitive I think!

May the flash be with you  Wink
  HWguru
 



 
View user's profileSend private messageVisit poster's website 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
I think I've got it now.

Do I have to pload each file, i.e zImage, hddapp.tgz, rd.gz or do I upload the file as downloaded from the MRT support site?

Thanks
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Dear Gilberto. These are correct steps:

    *  Install a tftp server (i use tftpd32 on windows)
    * Download firmware image you want to flash on your NAS
    * Extract files from that package and put into the tftp server directory
    * Press Y on the bootloader menu, then press 2, enter your tftp server IP, press enter, enter 'zImage' and press enter
    * Press R on the bootloader menu, then press 2, enter your tftp server IP, press enter, enter 'rd.gz' and press enter
    * Press A on the bootloader menu, then press 2, enter your tftp server IP, press enter, enter 'hddapp.tgz' and press enter
    * Press 1 on the bootloader menu or manually shutdown/restart the NAS
    * Now you should have your NAS booting fine (check your DHCP server log for its IP)

I hope this helps!
 



 
View user's profileSend private messageVisit poster's website 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Hooray!!!!!

It's risen from the dead.  Very Happy  Smile

I actually done it by re-creating each image as explained at: http://haukap.net/2007/05/13/enabli...way/#comment-33
A bit longer to do than how you've explained lordscaffard but I guess it's the end result that counts.

Well, I'd like to thank ALL that have helped me in this forum, plus ALL the other sources including how to make the cable, it's much appreciated.
I hope I can cancel the order for the Jtag adapter now, don't think I'll be needing it now.  Laughing
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
good - but a little more complicated - job. you've seen the light at the tunnel end!
 



 
View user's profileSend private messageVisit poster's website 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Hi,

I've bought the kuzito JTAG Cable on ebay. But I'm worried about the next steps. I've "installed" a 100Ohm connetion between R36 and 35 as shown in the wiki. But how have I to connect the cables of the JTAG.


Plug (JTAG X1)
TCK   |---|  GND
TDO   |---|  Vref
TMS   |---|  TRST
VDD   |---|  nRST
TDI    |---|  GND


the cable has on the right side a red cable, does it mean

red cable (1. cable) = TCK ?
2. cable = GND ?
3. cable = TDO ?
4. cable = Vref ? and so on is this right ????


so I have to connect (beginning with the red cable as 1.cable)

1,2,17 = VDD =VREF = 3,3V         (4. +7. + ?. cable)
4 - GND                                       (2. cable)
5 - TDI                                         (9. cable)
7 - TMS                                      (5. cable)
9 - TCK                                      (1.cable)
13 - TDO                                    (3.cable)

Hope you understand what I mean and that you can help me.

Thanks !!!


Greetings
frankteb
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Hi,
yes you are nearly right!

Note: if you look at the bottom of the JTAG connector X1 you will see that Vref is not connected.
You need VDD which is the same as B+ at X3 and X2.

you have to connect (beginning with the red cable as 1.cable)

1,2,17 =VDD = 3,3V   (7. cable)
4 - GND                     (2. cable)
5 - TDI                      (9. cable)
7 - TMS                     (5. cable)
9 - TCK                     (1.cable)
13 - TDO                   (3.cable)

Good luck,
  HWguru
 



 
View user's profileSend private messageVisit poster's website 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Thanks HWguru!!!

I will give it a try this afternoon !!!!



frankteb
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
I've connected LPT 5 and 11 with a simple cable as shown in the wiki and I got the message 'Short plug detected'. But when I'm connecting the JTAG at the LPT and connect TDI (9.cable) with TDO (3.cable) of X1 and start the NAS2000FlashTool_1.0.4.191 I didn't get the message.


What's wrong ???


Thanks again.


frankteb
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
So,

I've connect TDO and TDI of X2 and test it with the flashtool. But I didn't get the 'Short plug detected'.

I also tried to begin with GND as 1.cable and TCK as 2.cable but it doesn't work

Please help.

greetings
frankteb
 



 
View user's profileSend private message 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
Hi, it must work.
For the shortplug test the adapter board needs Power applied.
You could also try the LED test.
Could be a wrong bios setting for the LPT port.
 



 
View user's profileSend private messageVisit poster's website 
Back to topPage bottom
Reply with quote Download Post 
Post Re: BAD FIRMWARE UPGRADE 
 
I didn't have any LEDs. I've bought the JTAG at ebay from kuzito.

Quote:
For the shortplug test the adapter board needs Power applied.


That means the JTAG needs Power? Where did I get the power from ?

greetings
frankteb
 



 
View user's profileSend private message 
Back to topPage bottom
Display posts from previous:   
 

Post new topic  Reply to topic  Page 1 of 3
Goto page 1, 2, 3  Next

Users browsing this topic: 0 Registered, 0 Hidden and 1 Guest
Registered Users: None


 
Permissions List
You cannot post new topics
You cannot reply to topics
You cannot edit your posts
You cannot delete your posts
You cannot vote in polls
You cannot attach files
You cannot download files
You can post calendar events