Re: Problem while downloading the FLASH.BIN
- From: voidcoder <voidcoder@xxxxxxxxx>
- Date: Tue, 26 Dec 2006 02:29:16 +0100
You may want to tell us what device is it, how much
RAM/FLASH is installed on it, what is "Flash.bin"
image etc.
Leon zhang wrote:
Well, there is a strange problem here while I downloading the.
"Flash.bin".
Here is the Log :
=======================================================
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
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.100.66 Port 0400 Dest IP 192.168.100.55 Port 0B3B
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp
Download file information:
-------------------------------------------------------------------------------
[0]: Address=0x9AAC0000 Length=0x1F40000 Name=
****** OEMVerifyMemory checking physical range [ 0x40C0000 ==>
0x5FFFFFF ]...
****** OEMVerifyMemory FAILED - Invalid Memory Area ******
!OEMVERIFYMEMORY: Invalid image
=======================================================
Well, the question is the "physical range" seems like a "virtual
address", 0x40C0000.
And I read through the code(blcommon.c). I found that the address is
*OEMReadData()* from *Host*.
But, I don't know how to deal with the *.BIN file.
So, thanks for your any comments.
Thanks in advance.
- References:
- Problem while downloading the FLASH.BIN
- From: Leon zhang
- Problem while downloading the FLASH.BIN
- Prev by Date: Re: ActiveSync performance
- Next by Date: Re: 8 to 18 look up
- Previous by thread: Problem while downloading the FLASH.BIN
- Next by thread: ActiveSync performance
- Index(es):