Sonntag, 27. Mai 2018, 17:24 UTC+2
Sie sind nicht angemeldet.
Lieber Besucher, herzlich willkommen bei: NAS Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.
Mittwoch, 12. Januar 2011, 14:52
unknown flash! could someone help me ?
with the help of the new version nas_flash_tool, my board has been recognized with the following information.
yes, the flash may be strange to the nas_flash_tool.Does it matter ?
and I try to write boot to the flash ,but it progresses very slowly. here is output ;
it seems to it will take a very long time to end it .i think there must be something wrong .
could anyone help me?
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
Testing cabletype 1 JTAG-IDCODE: 0x00526fa1 - OK Bypass-test: 0xaaab5554 - OK Testing cabletype 2 JTAG-IDCODE: 0xffffffff - not OK Expected: 0x00526fa1 Bypass-test: 0xffffffff - not OK Expected: 0xaaab5554 Cable type 1 detected. Device is in debug-mode - OK Reading CPU-Type (SL3516) CPU-ID: 0x003512 - OK CPU-Rev.: 0xc3 Flash-Manufacturer: 0xffff Flash-Device-ID: 227e-2221-2201 Flash type - unknown! Some errors detected! |
yes, the flash may be strange to the nas_flash_tool.Does it matter ?
and I try to write boot to the flash ,but it progresses very slowly. here is output ;
|
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 |
Filesize: 126kB (129900 Bytes) Bootblock: 128kB (131072 Bytes) Erasing Flash. Please wait Sector 0x30000000: Erase time: 380 [ms] Sector 0x2fffffff: Erase time: 10000 [ms] Sector 0x2ffffffe: Erase time: 10000 [ms] Sector 0x2ffffffd: Erase time: 10000 [ms] Sector 0x2ffffffc: Erase time: 9300 [ms] Sector 0x2ffffffb: Erase time: 10000 [ms] Sector 0x2ffffffa: Erase time: 10000 [ms] Sector 0x2ffffff9: Erase time: 1260 [ms] Sector 0x2ffffff8: Erase time: 510 [ms] Sector 0x2ffffff7: Erase time: 10000 [ms] Sector 0x2ffffff6: Erase time: 10000 [ms] Sector 0x2ffffff5: Erase time: 10 [ms] Sector 0x2ffffff4: Erase time: 10 [ms] Sector 0x2ffffff3: Erase time: 10000 [ms] Sector 0x2ffffff2: Erase time: 10000 [ms] Sector 0x2ffffff1: Erase time: 10 [ms] Sector 0x2ffffff0: Erase time: 10 [ms] Sector 0x2fffffef: Erase time: 10000 [ms] Sector 0x2fffffee: Erase time: 10000 [ms] Sector 0x2fffffed: Erase time: 230 [ms] Sector 0x2fffffec: Erase time: 80 [ms] Sector 0x2fffffeb: Erase time: 10000 [ms] Sector 0x2fffffea: Erase time: 10000 [ms] Sector 0x2fffffe9: Erase time: 10000 [ms] Sector 0x2fffffe8: Erase time: 10000 [ms] Sector 0x2fffffe7: Erase time: 10000 [ms] Sector 0x2fffffe6: Erase time: 10000 [ms] Sector 0x2fffffe5: Erase time: 10000 [ms] Sector 0x2fffffe4: Erase time: 10000 [ms] Sector 0x2fffffe3: Erase time: 10000 [ms] Sector 0x2fffffe2: Erase time: 10000 [ms] Sector 0x2fffffe1: Erase time: 10 [ms] Sector 0x2fffffe0: Erase time: 10 [ms] Sector 0x2fffffdf: Erase time: 10000 [ms] Sector 0x2fffffde: Erase time: 10000 [ms] Sector 0x2fffffdd: Erase time: 10000 [ms] Sector 0x2fffffdc: Erase time: 10000 [ms] Sector 0x2fffffdb: Erase time: 10000 [ms] Sector 0x2fffffda: Erase time: 10000 [ms] Sector 0x2fffffd9: Erase time: 10000 [ms] Sector 0x2fffffd8: Erase time: 10000 [ms] Sector 0x2fffffd7: Erase time: 10000 [ms] Sector 0x2fffffd6: Erase time: 10000 [ms] Sector 0x2fffffd5: Erase time: 10000 [ms] Sector 0x2fffffd4: Erase time: 10000 [ms] Sector 0x2fffffd3: Erase time: 10000 [ms] |
it seems to it will take a very long time to end it .i think there must be something wrong .
could anyone help me?
Mittwoch, 12. Januar 2011, 21:26
You are absolutely right! It takes a very long time. All You can do is wait and 
And when finished:
Greetz
Snoopy
And when finished:
Greetz
Snoopy
--------------------------------------------------------------------------
Der Mensch ist das wichtigste und kostbarste Peripheriegerät einer Computeranlage.
myStuff: NAS2001+4220(1000Gb-ext3)+Dlink524+KabelD. (120 Mbit)
Der Mensch ist das wichtigste und kostbarste Peripheriegerät einer Computeranlage.
myStuff: NAS2001+4220(1000Gb-ext3)+Dlink524+KabelD. (120 Mbit)
Mittwoch, 12. Januar 2011, 21:31
Hi,
no, waiting for a long time will not solve the problem
1. What hardware are you using?
2. What type of flash is on the board?
It could be an electrical problem with your adapter, too - because this message is not good:
HWguru
no, waiting for a long time will not solve the problem
1. What hardware are you using?
2. What type of flash is on the board?
It could be an electrical problem with your adapter, too - because this message is not good:
|
|
Quellcode |
1 |
Flash-Manufacturer: 0xffff |
HWguru
Leute ohne Laster haben oft wenige Tugenden...
NAS2000 2.3.2.IB.2.RS.1+Lüfterabschaltung+SSH+do_it+zusätzliche commandline tools+changed root password
1. suchen - lesen - Google - lesen - 1. Fragen gehören ins Forum, dann profitieren alle davon!
NAS2000 2.3.2.IB.2.RS.1+Lüfterabschaltung+SSH+do_it+zusätzliche commandline tools+changed root password
1. suchen - lesen - Google - lesen - 1. Fragen gehören ins Forum, dann profitieren alle davon!
Donnerstag, 13. Januar 2011, 04:00
Hi,
no, waiting for a long time will not solve the problem ;-)
1. What hardware are you using?
2. What type of flash is on the board?
It could be an electrical problem with your adapter, too - because this message is not good:
Quellcode
HWguru
thanks for your reply and excuse me for my replying so late.
I'm a newbie .
I've read your previous post, it said that it would take about 8 minutes . My experiment obviously takes much longer time .
the hardware is a NAS demo borad . it uses cortina 3512 cpu (previously known as stormlink).
the flash's cover has been abrased. type info can't be read.
I can see something like
ST
NAND010W332BN6
|
|
Quellcode |
1 |
Flash-Manufacturer: 0xffff |
before I operate the erase boot, the above info is 0x20.
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »nanjifeng« (13. Januar 2011, 06:17)
Donnerstag, 13. Januar 2011, 08:33
http://www.flexcomm.com.cn/products/TinaGarden-EB.html
this is the provider's website,but I find nothing about flash .
this is the provider's website,but I find nothing about flash .
Donnerstag, 13. Januar 2011, 08:52
Ok, I see.
If you run "JTAG Test" you must receive a valid Flash-Manufacturer!
Flash_tool knows the flash size and sector organization from the type.
There are 8M or 16M devices with top, bottom or no boot sector organization being used.
There seems to be a software bug because the sector addresses in the log are wrong.
And "10000 [ms]" is the maximum time which equals to a timeout.
It should look like this:
There has been a similar Problem in the past. A user received "Flash-Manufacturer: 0xffff" sometimes if he ran "JTAG Test".
In this case there was a problem with the adapter.
Check your GND connection. If it is too long you will run into troubles.
As there are 4 signals (TCK, TMS, TDI, TDO) toggling a good GND return path is required.
If you are using a LPT adapter with a Printer cable between you have to use more (best=all available) than one GND pin from the connector.
Otherwise the signal quality may be too bad.
Regards,
HWguru
If you run "JTAG Test" you must receive a valid Flash-Manufacturer!
Flash_tool knows the flash size and sector organization from the type.
There are 8M or 16M devices with top, bottom or no boot sector organization being used.
There seems to be a software bug because the sector addresses in the log are wrong.
|
|
Quellcode |
1 2 3 |
Erasing Flash. Please wait Sector 0x30000000: Erase time: 380 [ms] Sector 0x2fffffff: Erase time: 10000 [ms] |
And "10000 [ms]" is the maximum time which equals to a timeout.
It should look like this:
|
|
Quellcode |
1 2 |
Sector 0x30000000: Erase time: 810 [ms] Sector 0x30010000: Erase time: 780 [ms] |
There has been a similar Problem in the past. A user received "Flash-Manufacturer: 0xffff" sometimes if he ran "JTAG Test".
In this case there was a problem with the adapter.
Check your GND connection. If it is too long you will run into troubles.
As there are 4 signals (TCK, TMS, TDI, TDO) toggling a good GND return path is required.
If you are using a LPT adapter with a Printer cable between you have to use more (best=all available) than one GND pin from the connector.
Otherwise the signal quality may be too bad.
Regards,
HWguru
Leute ohne Laster haben oft wenige Tugenden...
NAS2000 2.3.2.IB.2.RS.1+Lüfterabschaltung+SSH+do_it+zusätzliche commandline tools+changed root password
1. suchen - lesen - Google - lesen - 1. Fragen gehören ins Forum, dann profitieren alle davon!
NAS2000 2.3.2.IB.2.RS.1+Lüfterabschaltung+SSH+do_it+zusätzliche commandline tools+changed root password
1. suchen - lesen - Google - lesen - 1. Fragen gehören ins Forum, dann profitieren alle davon!
ok. 
snoopy 
Ähnliche Themen
-
Hardware related »-
JTAG and serial cable adaptor compatibility
(28. November 2010, 11:24)