Re: bootloader issue for XIP on NAND flash
- From: "WangYeqing" <yeqingwang@xxxxxxxxx>
- Date: Fri, 6 Nov 2009 18:48:15 +0800
Do you have correct mbr?
Could you pls print the os debug message?
"David" <davidhqwang@xxxxxxxxx> дÈëÏûÏ¢ÐÂÎÅ:uheYPssXKHA.4688@xxxxxxxxxxxxxxxxxxxxxxx
YES, I have created one binfs and one extended partition.
See my log file:
ODYSSEY> load /odyssey/eboot.sre
About to load tftp://192.168.1.141/odyssey/eboot.sre
Press Ctrl-C to break
....
Start = 0x8f0e0004, range = (0x8f0e0000,0x8f0f28ab), format = SREC
?YSSEY> go
Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built
Jun 24 2004 18:33:02
Bsquare Loader (EBOOT)
Build Timestamp Fri Nov 6 10:38:40 2009
RMI Alchemy MID50(Au1250)
Au1250 AD (PRId 04030202) @ 600MHZ
BootArgs are at A00FFC00, SIG = 544F4F42
Free Memory starts at 0x00059FFC
HeapBase = 0x80019FFC, Size=262144
Setting up TOY completed
+FlashInit
FMD: ReadID (Mfg=EC, Dev=D3)
-FlashInit
System ready!
Preparing for download...
+OEMEthernetDownload
+LAN911xInit
LAN9118: Chip Id 9210 Revision 0
Auto Negotiation done
-LAN911xInit(mac = 00:fc:0f:a0:00:00, rc = 1)
Using DHCP
Device Name: MID50_04000
InitDHCP():: Calling ProcessDHCP()
ProcessDHCP()::DHCP_INIT
Got Response from DHCP server, IP address: 192.168.1.125
ProcessDHCP()::DHCP IP Address Resolved as 192.168.1.125, netmask:
255.255.255.0
Lease time: 604800 seconds
Got Response from DHCP server, IP address: 192.168.1.125
No ARP response in 2 seconds, assuming ownership of 192.168.1.125
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Locked Down Link 1
Src IP 192.168.1.125 Port 0800 Dest IP 192.168.1.141 Port 0FB6
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp
EbootInitEtherTransport completed.
Writing bootargs @ A00FFC00
Setting bootarg IP address: 192.168.1.125
-OEMEthernetDownload
Download file information:
-----------------------------------------------------
[0]: Address=0x83000000 Length=0x2000528 Name=800800C0
ROMHDR at Address 83000044h
NAND_FLASH with g_bDownloadImage=1 , pBootArgs->ucLoaderFlags=80
NAND_FLASH do image backup
Found chain information (pChainInfo=0x833FD5CC Extensions=0x3).
Create Partition flash blocks [0x83000000 through 0x85000528] - this is
the maximum size of all BIN regions.
CreateBINFSPartition: Start =0 length =33555752
-CreateBINFSPartition:
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
CreateExtendedPartition
ImgStart 83000000, ImgLen 02000528 LaunchAddr 83000004
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
Download successful! image Start Address is 83000004
"WangYeqing" <yeqingwang@xxxxxxxxx> wrote in message
news:uiQRGlsXKHA.3720@xxxxxxxxxxxxxxxxxxxxxxx
I am now working on binfs
First you should use bootpart function to create partition for binfs and
fat.
"David" <davidhqwang@xxxxxxxxx> дÈëÏûÏ¢ÐÂÎÅ:eKIIAnrXKHA.408@xxxxxxxxxxxxxxxxxxxxxxx
I am do the job for adding XIP support for NAND booted Au1200 device.
Now, I can get four bin files, that is kerl.bin, chain.bin, nk.bin and
xip.bin.
with config.bib settings
KERL 83000000 02000000 RAMIMAGE
CHAIN $(XIPLOC_PHYSICAL) 00002000 RESERVED
NK 85002000 02000000 NANDIMAGE
RAM 87002000 07000000 RAM
pdwXIPLoc 00000000 $(XIPLOC_PHYSICAL) FIXUPVAR
Can somebody tell me how wince kernel fetch the module which is resiend
in NAND flash?
give an example, we have put pm.dll to NK.bin and NK section is a
NAMDIMAGE section, so the data of pm.dll is located in NAND not RAM,
how ce kernel get to know where is the image of pm.dll be put and fetch
that image to RAM?
that in advance.
.
- Follow-Ups:
- Re: bootloader issue for XIP on NAND flash
- From: David
- Re: bootloader issue for XIP on NAND flash
- References:
- bootloader issue for XIP on NAND flash
- From: David
- Re: bootloader issue for XIP on NAND flash
- From: WangYeqing
- Re: bootloader issue for XIP on NAND flash
- From: David
- bootloader issue for XIP on NAND flash
- Prev by Date: Re: why fatfs.dll is loaded two times?
- Next by Date: Re: bootloader issue for XIP on NAND flash
- Previous by thread: Re: bootloader issue for XIP on NAND flash
- Next by thread: Re: bootloader issue for XIP on NAND flash
- Index(es):
Relevant Pages
|
