friendlyarm Mini6410 a Mini2440 - zkusenosti

Jaroslav Buchta jaroslav.buchta na gmail.com
Středa Říjen 6 11:27:07 CEST 2010


Ano, presne takto jsem postupoval -ted zkousim a mam tam stepldr.nb1 + 
EBOOT_64_MB_A70 (mam teda verzi 128MB ale to by snad nemelo vadit?)

Initiating image launch in 1 seconds.
Ethernet Boot Loader Configuration:

0) IP address: 192.168.1.6
1) Subnet mask: 255.255.255.0
2) DHCP: Disabled
3) Boot delay: 1 seconds
4) Reset to factory default configuration
5) Startup image: LAUNCH EXISTING
6) Program disk image into SmartMedia card: Enabled
7) Program DM9000 MAC address (10:23:45:67:89:AB)
8) Kernel Debugger: ENABLED
9) Format Boot Media for BinFS
E) Erase Reserved Block
B) Mark Bad Block at Reserved Block
F) Low-level format the Smart Media card
D) Download image now(USE TFTP)
L) LAUNCH existing Boot Media image
R) Read Configuration
U) Download image now(USE USB)
W) Write Configuration Right Now

Enter your selection:

 >>>> ted dam U a vysledek: (problem vidim v Format TQ2440 Nand Flash: 
found a bad block (0x18) - skipping...)

U
System ready!
Preparing for download...
Please send the Image through USB.

USB host is connected. Waiting a download.

Addr: 0x30000000 ; Size: 0x1D27421
Read Bin Files StartAddr:0x80200000 ; Length: 0x1D81E98

Download BIN file information:
-----------------------------------------------------
[0]: Base Address=0x80200000 Length=0x1d81e98
-----------------------------------------------------
+=OEMVerifyMemory+ dwStartAddr:0x80200000 dwLength:0x1d81e98
RAM image 0xa 0x81f81e97
rom_offset=0x0.
ROMHDR at Address 80200044h
Writing single region/multi-region update, dwBINFSPartLength: 30940824
IsValidMBR: MBR sector = 0x0
OpenPartition: Invalid MBR. Formatting flash.
Enter TQ2440 FastLowLevelFormat [0x0, 0x1fff].
Format TQ2440 Nand Flash: found a bad block (0x18) - skipping...
Format TQ2440 Nand Flash: ...erase complete.
WriteMBR: MBR block = 0x0.
BP_FastLowLevelFormat: Done.

OpenPartition: Partition Exists=0x0 for part 0x21.
CreatePartition: Enter CreatePartition for 0x21.
LastLogSector: Last log sector is: 0x1ffeff.
CreatePartition: Start = 0x8100, Num = 0xed00.
Log2Phys: Logical 0x8100 -> Physical 0x8200
WriteMBR: MBR block = 0x0.
BP_SetDataPointer at 0x0
WriteData: Start = 0x0, Length = 0x1d81e98.
Log2Phys: Logical 0x8100 -> Physical 0x8200
Updateded TOC!
IsValidMBR: MBR sector = 0x0
OpenPartition: Partition Exists=0x0 for part 0xb.
CreatePartition: Enter CreatePartition for 0xb.
FindFreeSector: FreeSector is: 0x16e00 after processing part 0x21.
CreatePartition: Num sectors set to 0x1e7d00 to allow for compaction blocks.
CreatePartition: Start = 0x16e00, Num = 0x1e7d00.
WriteMBR: MBR block = 0x0.
TOC {
dwSignature: 0x434F544E
BootCfg {
ConfigFlags: 0x2830
BootDelay: 0x1
ImageIndex: 1
IP: 192.168.1.6
MAC Address: 10:23:45:67:89:AB
Port: 0.0.0.0
SubnetMask: 255.255.255.0
}
ID[0] {
dwVersion: 0x20004
dwSignature: 0x45424F54
String: 'eboot.nb0'
dwImageType: 0x2
dwTtlSectors: 0x400
dwLoadAddress: 0x80038000
dwJumpAddress: 0x80038000
dwStoreOffset: 0x0
sgList[0].dwSector: 0x2000
sgList[0].dwLength: 0x400
}
ID[1] {
dwVersion: 0x1
dwSignature: 0x43465348
String: ''
dwImageType: 0x2
dwTtlSectors: 0xEC10
dwLoadAddress: 0x80200000
dwJumpAddress: 0x802C25EC
dwStoreOffset: 0x0
sgList[0].dwSector: 0x8200
sgList[0].dwLength: 0xEC10
}
chainInfo.dwLoadAddress: 0X00000000
chainInfo.dwFlashAddress: 0X00000000
chainInfo.dwLength: 0X00000000
}
waitforconnect
INFO: OEMLaunch: Jumping to Physical Address 0x302C25ECh (Virtual 
Address 0x802C25ECh)...

ÿCÀ

 >>>>> od teto chvile nejde do NAND nahrat ani u-boot, vivi test a 
cokoli jineho, musim ji natvrdo zformatovat s odstranenim oznaceni 
vadnych bloku, protoze to pak po prikazu nand bad signalizuje vadne 
bloky od 0...


Dne 6.10.2010 10:30, Pajpach napsal(a):
> Tak na toto je reseni toto:
> Nabootovat z NOR flash, zformatovat celou NAND, nahrat do NAND stepldr 
> (myslim, ze volba 1) pak bez restartu nahrat do NAND eboot, pak 
> vypnout, nastartovat do NAND bootloaderu (mezernikem), a nahrat OS jak 
> jsem popsal v predchozim e-mailu. Presny postup krok za krokem (pokud 
> je potreba) je na CDcku. Toto by melo odstranit problem s vadnym 1. 
> blokem.
>
> MP
>
> --------------------------------------------------
> From: "Jaroslav Buchta" <jaroslav.buchta na gmail.com>
> Sent: Wednesday, October 06, 2010 9:31 AM
> To: "HW-news" <hw-list na list.hw.cz>
> Subject: Re: friendlyarm Mini6410 a Mini2440 - zkusenosti
>
>> Tak uz jsem zkousel vsechno mozne... Kdyz tak sem hodim log - eboot 
>> skutecne natahne CE a spusti je, bohuzel pritom podela konfiguraci 
>> NAND (pri zapisu skutecne detekuje nejaky bad block...)
>> Takze jsem zkousel nove verze u-boot, ktere by snad mely byt schopny 
>> NAND nejak diagnostikovat a hlavne vytvorit tabulku bbt, coz skutecne 
>> vytvori ale vysledek je stejny.
>> No budu zkouset dal...
>>
>> Dne 6.10.2010 8:56, Pajpach napsal(a):
>>> Dobry den,
>>>
>>> Pokud deska bootuje (funguje eboot) tak pri zapnuti mejte pripojeny 
>>> seriovy terminal (rychlost 115200bd) a drzte zmacknuty mezernik.
>>> Vybehne menu bootloaderu. Postupne dejte volby "9" pak "F" a pak "U" 
>>> Prvni zformatuje NAND, druha vytvori filesystem a treti se bude 
>>> dozadovat nahrani image OS pres USB port. Plati pro nahrani WINCE. 
>>> Pokud "jen" prehrajete OS bez predchoziho formatovani, bude to delat 
>>> to co popisujete.
>>> Je to celkem obsahle napsane i v manualu, jen je nutne ten postup 
>>> dodrzet. :-)
>>> Pokud nefunguje ani eboot, da se prepnout prepinacem na bootovani z 
>>> NOR flash a prehrat i zavadec, ale to uz bych resil mimo konferu.
>>>
>>> MP
>>>
>>> --------------------------------------------------
>>> From: "Jaroslav Buchta" <jaroslav.buchta na gmail.com>
>>> Sent: Wednesday, October 06, 2010 8:40 AM
>>> To: "HW-news" <hw-list na list.hw.cz>
>>> Subject: Re: friendlyarm Mini6410 a Mini2440 - zkusenosti
>>>
>>>> Zrovna mam 2440 na stole, vcera prisel a spat jsem sel ve 3h...
>>>> Byly tam predinstalovane WinCE5 docela funkcni a necinske, po 
>>>> nejakych pokusech jsem je v NAND flash odrovnal a od te doby se mi 
>>>> nepovedlo nahodit funkcni system (ane CE, ani Linux) kdyz vychazim 
>>>> z dodaneho DVD. CE je celkem jeste pozitivni, ze aspon po instalaci 
>>>> nabehne (5 i 6) ale nejak poskodi tabulku vadnych bloku NAND a 
>>>> reboot uz se nekona (oznaci jako vadny 1. blok NAND z ktereho se ma 
>>>> bootovat...) Aspon tusim dle vypisu na konzole, ze chyba je tady.
>>>> To se ale snad vhodnou kombinaci SW podda, no Linux ma sve kouzlo - 
>>>> spousta verzi SW (zde boot loadery) kazdy funguje jinak a zadny 
>>>> poradne ;-)
>>>> Kazdopadne by me zajimalo - lze prelozit tyto produkty pod Win nebo 
>>>> budu muset hloubeji proniknout do Linuxu? Staci nejaka live 
>>>> distribuce? Ktera nejlepe?
>>>>
>>>> Dik za nakopnuti nez se rozkoukam :-)
>>>> _______________________________________________
>>>> HW-list mailing list - sponsored by www.HW.cz
>>>> Hw-list na list.hw.cz
>>>> http://list.hw.cz/mailman/listinfo/hw-list
>>>>
>>> _______________________________________________
>>> HW-list mailing list - sponsored by www.HW.cz
>>> Hw-list na list.hw.cz
>>> http://list.hw.cz/mailman/listinfo/hw-list
>>>
>>
>> _______________________________________________
>> HW-list mailing list - sponsored by www.HW.cz
>> Hw-list na list.hw.cz
>> http://list.hw.cz/mailman/listinfo/hw-list
>>
> _______________________________________________
> HW-list mailing list - sponsored by www.HW.cz
> Hw-list na list.hw.cz
> http://list.hw.cz/mailman/listinfo/hw-list
>



Další informace o konferenci Hw-list