Hi, All

I modified config.bib to program nk.bin to the flash. But I got
checksum failure when eboot starts downloading the image. The error
msg is:
****** OEMVerfyMemory checking physical range [0x80000==>0xE16627]...
****** FLASH Address ******
ERROR: Checksum failure (expected=0x2EB computed = 0x2C6)
*******Checksum failure on record 1, ABORT!!! ******

The config.bib is as follows, the platform is PXA27x WinCE5.0. Did I
miss out anything?
MEMORY
; Name Start Size Type
; ------- -------- -------- ----
RSVD 80000000 000FF000 RESERVED
ARGS 800FF000 00001000 RESERVED
NK 9CA80000 01000000 RAMIMAGE
RAM 80100000 03F00000 RAM

; Reserve ZBANK virtual block (No physical memory
; is required to back this virtual range).
;
ZBANK 96500000 00100000 RESERVED

CONFIG
ROMSTART=9CA80000
ROMSIZE=01000000
ROMWIDTH=32
AUTOSIZE=OFF
KERNELFIXUPS=ON

Thanks a lot in advance

Tang

Re: Checksum failure when program image to the flash by Wang

Wang
Mon Jan 10 19:37:50 CST 2005

Do virtual address 9CA80000 map to physical flash address? If it is not,you
will use ROMOFFSET to enable nk.bin in flash.

--
Best wishes
Wang Yeqing
***********************************************************
Intelligent Grouping Research and Development Institute
Amoi Electronics Co., Ltd

Tel: 86-592-6516777-6515
***********************************************************

"Tang" <ymtang@gmail.com>
??????:8812976b.0501101636.5a0d321f@posting.google.com...
> Hi, All
>
> I modified config.bib to program nk.bin to the flash. But I got
> checksum failure when eboot starts downloading the image. The error
> msg is:
> ****** OEMVerfyMemory checking physical range [0x80000==>0xE16627]...
> ****** FLASH Address ******
> ERROR: Checksum failure (expected=0x2EB computed = 0x2C6)
> *******Checksum failure on record 1, ABORT!!! ******
>
> The config.bib is as follows, the platform is PXA27x WinCE5.0. Did I
> miss out anything?
> MEMORY
> ; Name Start Size Type
> ; ------- -------- -------- ----
> RSVD 80000000 000FF000 RESERVED
> ARGS 800FF000 00001000 RESERVED
> NK 9CA80000 01000000 RAMIMAGE
> RAM 80100000 03F00000 RAM
>
> ; Reserve ZBANK virtual block (No physical memory
> ; is required to back this virtual range).
> ;
> ZBANK 96500000 00100000 RESERVED
>
> CONFIG
> ROMSTART=9CA80000
> ROMSIZE=01000000
> ROMWIDTH=32
> AUTOSIZE=OFF
> KERNELFIXUPS=ON
>
> Thanks a lot in advance
>
> Tang



Re: Checksum failure when program image to the flash by K

K
Mon Jan 10 23:09:30 CST 2005

There is a bug in the OEMIsFlashAddr of flash.c(SRC\BOOTLOADER\EBOOT)

It only reconized the Unchached Flash Address(0xBCA80000) but NOT for cached
address(0x9CA80000).
You may fix this issue by patch the OEMIsFlashAddr as the following codes

BOOL OEMIsFlashAddr(DWORD dwAddr)
{
DWORD dwVirtFlashStart = (DWORD)
OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, FALSE);

dwAddr = (DWORD)OALCAtoUA(dwAddr); // <-- patch here

if ((dwAddr >= dwVirtFlashStart) && (dwAddr <= (dwVirtFlashStart +
MAINSTONEII_SIZE_BOOT_FLASH)))
{
return(TRUE);
}

return(FALSE);
}

"Tang" <ymtang@gmail.com>
???????:8812976b.0501101636.5a0d321f@posting.google.com...
> Hi, All
>
> I modified config.bib to program nk.bin to the flash. But I got
> checksum failure when eboot starts downloading the image. The error
> msg is:
> ****** OEMVerfyMemory checking physical range [0x80000==>0xE16627]...
> ****** FLASH Address ******
> ERROR: Checksum failure (expected=0x2EB computed = 0x2C6)
> *******Checksum failure on record 1, ABORT!!! ******
>
> The config.bib is as follows, the platform is PXA27x WinCE5.0. Did I
> miss out anything?
> MEMORY
> ; Name Start Size Type
> ; ------- -------- -------- ----
> RSVD 80000000 000FF000 RESERVED
> ARGS 800FF000 00001000 RESERVED
> NK 9CA80000 01000000 RAMIMAGE
> RAM 80100000 03F00000 RAM
>
> ; Reserve ZBANK virtual block (No physical memory
> ; is required to back this virtual range).
> ;
> ZBANK 96500000 00100000 RESERVED
>
> CONFIG
> ROMSTART=9CA80000
> ROMSIZE=01000000
> ROMWIDTH=32
> AUTOSIZE=OFF
> KERNELFIXUPS=ON
>
> Thanks a lot in advance
>
> Tang



Re: Checksum failure when program image to the flash by Wang

Wang
Tue Jan 11 08:06:22 CST 2005

I think you don't need to patch
dwAddr = (DWORD)OALCAtoUA(dwAddr); // <-- patch here

You modify like this:

OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, TRUE);

Modify FALSE to TRUE.



--
Best wishes
Wang Yeqing
***********************************************************
Intelligent Grouping Research and Development Institute
Amoi Electronics Co., Ltd

Tel: 86-592-6516777-6515
***********************************************************

"K. S. Huang" <ks_huang@AlphaNetworks.com_remove.this> дÈëÏûÏ¢ÐÂÎÅ:%23i788u59EHA.2700@TK2MSFTNGP14.phx.gbl...
> There is a bug in the OEMIsFlashAddr of flash.c(SRC\BOOTLOADER\EBOOT)
>
> It only reconized the Unchached Flash Address(0xBCA80000) but NOT for
> cached
> address(0x9CA80000).
> You may fix this issue by patch the OEMIsFlashAddr as the following codes
>
> BOOL OEMIsFlashAddr(DWORD dwAddr)
> {
> DWORD dwVirtFlashStart = (DWORD)
> OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, FALSE);
>
> dwAddr = (DWORD)OALCAtoUA(dwAddr); // <-- patch here
>
> if ((dwAddr >= dwVirtFlashStart) && (dwAddr <= (dwVirtFlashStart +
> MAINSTONEII_SIZE_BOOT_FLASH)))
> {
> return(TRUE);
> }
>
> return(FALSE);
> }
>
> "Tang" <ymtang@gmail.com>
> ???????:8812976b.0501101636.5a0d321f@posting.google.com...
>> Hi, All
>>
>> I modified config.bib to program nk.bin to the flash. But I got
>> checksum failure when eboot starts downloading the image. The error
>> msg is:
>> ****** OEMVerfyMemory checking physical range [0x80000==>0xE16627]...
>> ****** FLASH Address ******
>> ERROR: Checksum failure (expected=0x2EB computed = 0x2C6)
>> *******Checksum failure on record 1, ABORT!!! ******
>>
>> The config.bib is as follows, the platform is PXA27x WinCE5.0. Did I
>> miss out anything?
>> MEMORY
>> ; Name Start Size Type
>> ; ------- -------- -------- ----
>> RSVD 80000000 000FF000 RESERVED
>> ARGS 800FF000 00001000 RESERVED
>> NK 9CA80000 01000000 RAMIMAGE
>> RAM 80100000 03F00000 RAM
>>
>> ; Reserve ZBANK virtual block (No physical memory
>> ; is required to back this virtual range).
>> ;
>> ZBANK 96500000 00100000 RESERVED
>>
>> CONFIG
>> ROMSTART=9CA80000
>> ROMSIZE=01000000
>> ROMWIDTH=32
>> AUTOSIZE=OFF
>> KERNELFIXUPS=ON
>>
>> Thanks a lot in advance
>>
>> Tang
>
>



Re: Checksum failure when program image to the flash by K

K
Tue Jan 11 23:17:11 CST 2005

Well, that will be fine for the cachable address, but for uncachable address
(the ebbot.bin) will be failed!!

"Wang Yeqing" <wangyq@amoi.com.cn> ¼¶¼g©ó¶l¥ó·s»D
:#5D29Y#9EHA.2196@TK2MSFTNGP11.phx.gbl...
> I think you don't need to patch
> dwAddr = (DWORD)OALCAtoUA(dwAddr); // <-- patch here
>
> You modify like this:
>
> OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, TRUE);
>
> Modify FALSE to TRUE.
>
>
>
> --
> Best wishes
> Wang Yeqing
> ***********************************************************
> Intelligent Grouping Research and Development Institute
> Amoi Electronics Co., Ltd
>
> Tel: 86-592-6516777-6515
> ***********************************************************
>
> "K. S. Huang" <ks_huang@AlphaNetworks.com_remove.this> дÈëÏûÏ¢ÐÂÎÅ
:%23i788u59EHA.2700@TK2MSFTNGP14.phx.gbl...
> > There is a bug in the OEMIsFlashAddr of flash.c(SRC\BOOTLOADER\EBOOT)
> >
> > It only reconized the Unchached Flash Address(0xBCA80000) but NOT for
> > cached
> > address(0x9CA80000).
> > You may fix this issue by patch the OEMIsFlashAddr as the following
codes
> >
> > BOOL OEMIsFlashAddr(DWORD dwAddr)
> > {
> > DWORD dwVirtFlashStart = (DWORD)
> > OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, FALSE);
> >
> > dwAddr = (DWORD)OALCAtoUA(dwAddr); // <-- patch here
> >
> > if ((dwAddr >= dwVirtFlashStart) && (dwAddr <= (dwVirtFlashStart +
> > MAINSTONEII_SIZE_BOOT_FLASH)))
> > {
> > return(TRUE);
> > }
> >
> > return(FALSE);
> > }
> >
> > "Tang" <ymtang@gmail.com>
> > ???????:8812976b.0501101636.5a0d321f@posting.google.com...
> >> Hi, All
> >>
> >> I modified config.bib to program nk.bin to the flash. But I got
> >> checksum failure when eboot starts downloading the image. The error
> >> msg is:
> >> ****** OEMVerfyMemory checking physical range [0x80000==>0xE16627]...
> >> ****** FLASH Address ******
> >> ERROR: Checksum failure (expected=0x2EB computed = 0x2C6)
> >> *******Checksum failure on record 1, ABORT!!! ******
> >>
> >> The config.bib is as follows, the platform is PXA27x WinCE5.0. Did I
> >> miss out anything?
> >> MEMORY
> >> ; Name Start Size Type
> >> ; ------- -------- -------- ----
> >> RSVD 80000000 000FF000 RESERVED
> >> ARGS 800FF000 00001000 RESERVED
> >> NK 9CA80000 01000000 RAMIMAGE
> >> RAM 80100000 03F00000 RAM
> >>
> >> ; Reserve ZBANK virtual block (No physical memory
> >> ; is required to back this virtual range).
> >> ;
> >> ZBANK 96500000 00100000 RESERVED
> >>
> >> CONFIG
> >> ROMSTART=9CA80000
> >> ROMSIZE=01000000
> >> ROMWIDTH=32
> >> AUTOSIZE=OFF
> >> KERNELFIXUPS=ON
> >>
> >> Thanks a lot in advance
> >>
> >> Tang
> >
> >
>
>



Re: Checksum failure when program image to the flash by ymtang

ymtang
Wed Jan 12 00:06:40 CST 2005

Thanks you guys, after modifying something in flash.c, the flashing
can be completed successfully. And the OS can be started right after
the flashing. However, if I restart the platform, it hangs at the very
beginning. The following is what I captured from the serial port:
--------------------
System ready!
Preparing for download...
INFO: Using device name: 'MAINSTN0'
Download successful! Jumping to image at 0x9CB01000 (physicWindows CE
Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:25:00
ProcessorType=0411 Revision=4
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 9c
b05b14
--------------------
Any idea on this?

Thanks a lot in advance

Tang


"Wang Yeqing" <wangyq@amoi.com.cn> wrote in message news:<#5D29Y#9EHA.2196@TK2MSFTNGP11.phx.gbl>...
> You modify like this:
>
> OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, TRUE);
>
> Modify FALSE to TRUE.
>
>
>
> --
> Best wishes
> Wang Yeqing
> ***********************************************************
> Intelligent Grouping Research and Development Institute
> Amoi Electronics Co., Ltd
>
> Tel: 86-592-6516777-6515
> ***********************************************************
>
> "K. S. Huang" <ks_huang@AlphaNetworks.com_remove.this> дÈëÏûÏ¢ÐÂÎÅ:%23i788u59EHA.2700@TK2MSFTNGP14.phx.gbl...
> > There is a bug in the OEMIsFlashAddr of flash.c(SRC\BOOTLOADER\EBOOT)
> >
> > It only reconized the Unchached Flash Address(0xBCA80000) but NOT for
> > cached
> > address(0x9CA80000).
> > You may fix this issue by patch the OEMIsFlashAddr as the following codes
> >
> > BOOL OEMIsFlashAddr(DWORD dwAddr)
> > {
> > DWORD dwVirtFlashStart = (DWORD)
> > OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, FALSE);
> >
> > dwAddr = (DWORD)OALCAtoUA(dwAddr); // <-- patch here
> >
> > if ((dwAddr >= dwVirtFlashStart) && (dwAddr <= (dwVirtFlashStart +
> > MAINSTONEII_SIZE_BOOT_FLASH)))
> > {
> > return(TRUE);
> > }
> >
> > return(FALSE);
> > }
> >
> > "Tang" <ymtang@gmail.com>
> > ???????:8812976b.0501101636.5a0d321f@posting.google.com...
> >> Hi, All
> >>
> >> I modified config.bib to program nk.bin to the flash. But I got
> >> checksum failure when eboot starts downloading the image. The error
> >> msg is:
> >> ****** OEMVerfyMemory checking physical range [0x80000==>0xE16627]...
> >> ****** FLASH Address ******
> >> ERROR: Checksum failure (expected=0x2EB computed = 0x2C6)
> >> *******Checksum failure on record 1, ABORT!!! ******
> >>
> >> The config.bib is as follows, the platform is PXA27x WinCE5.0. Did I
> >> miss out anything?
> >> MEMORY
> >> ; Name Start Size Type
> >> ; ------- -------- -------- ----
> >> RSVD 80000000 000FF000 RESERVED
> >> ARGS 800FF000 00001000 RESERVED
> >> NK 9CA80000 01000000 RAMIMAGE
> >> RAM 80100000 03F00000 RAM
> >>
> >> ; Reserve ZBANK virtual block (No physical memory
> >> ; is required to back this virtual range).
> >> ;
> >> ZBANK 96500000 00100000 RESERVED
> >>
> >> CONFIG
> >> ROMSTART=9CA80000
> >> ROMSIZE=01000000
> >> ROMWIDTH=32
> >> AUTOSIZE=OFF
> >> KERNELFIXUPS=ON
> >>
> >> Thanks a lot in advance
> >>
> >> Tang
> >
> >

Re: Checksum failure when program image to the flash by K

K
Wed Jan 12 02:48:37 CST 2005

It might caused by the corrupted SDRAM data.
Try to call NKForceCleanBoot in your OEMInit() to force cold boot.

"Tang" <ymtang@gmail.com>
???????:8812976b.0501112206.83641a6@posting.google.com...
> Thanks you guys, after modifying something in flash.c, the flashing
> can be completed successfully. And the OS can be started right after
> the flashing. However, if I restart the platform, it hangs at the very
> beginning. The following is what I captured from the serial port:
> --------------------
> System ready!
> Preparing for download...
> INFO: Using device name: 'MAINSTN0'
> Download successful! Jumping to image at 0x9CB01000 (physicWindows CE
> Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:25:00
> ProcessorType=0411 Revision=4
> sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 9c
> b05b14
> --------------------
> Any idea on this?
>
> Thanks a lot in advance
>
> Tang
>
>
> "Wang Yeqing" <wangyq@amoi.com.cn> wrote in message
news:<#5D29Y#9EHA.2196@TK2MSFTNGP11.phx.gbl>...
> > You modify like this:
> >
> > OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, TRUE);
> >
> > Modify FALSE to TRUE.
> >
> >
> >
> > --
> > Best wishes
> > Wang Yeqing
> > ***********************************************************
> > Intelligent Grouping Research and Development Institute
> > Amoi Electronics Co., Ltd
> >
> > Tel: 86-592-6516777-6515
> > ***********************************************************
> >
> > "K. S. Huang" <ks_huang@AlphaNetworks.com_remove.this>
дÈëÏûÏ¢ÐÂÎÅ:%23i788u59EHA.2700@TK2MSFTNGP14.phx.gbl...
> > > There is a bug in the OEMIsFlashAddr of flash.c(SRC\BOOTLOADER\EBOOT)
> > >
> > > It only reconized the Unchached Flash Address(0xBCA80000) but NOT for
> > > cached
> > > address(0x9CA80000).
> > > You may fix this issue by patch the OEMIsFlashAddr as the following
codes
> > >
> > > BOOL OEMIsFlashAddr(DWORD dwAddr)
> > > {
> > > DWORD dwVirtFlashStart = (DWORD)
> > > OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, FALSE);
> > >
> > > dwAddr = (DWORD)OALCAtoUA(dwAddr); // <-- patch here
> > >
> > > if ((dwAddr >= dwVirtFlashStart) && (dwAddr <= (dwVirtFlashStart +
> > > MAINSTONEII_SIZE_BOOT_FLASH)))
> > > {
> > > return(TRUE);
> > > }
> > >
> > > return(FALSE);
> > > }
> > >
> > > "Tang" <ymtang@gmail.com>
> > > ???????:8812976b.0501101636.5a0d321f@posting.google.com...
> > >> Hi, All
> > >>
> > >> I modified config.bib to program nk.bin to the flash. But I got
> > >> checksum failure when eboot starts downloading the image. The error
> > >> msg is:
> > >> ****** OEMVerfyMemory checking physical range [0x80000==>0xE16627]...
> > >> ****** FLASH Address ******
> > >> ERROR: Checksum failure (expected=0x2EB computed = 0x2C6)
> > >> *******Checksum failure on record 1, ABORT!!! ******
> > >>
> > >> The config.bib is as follows, the platform is PXA27x WinCE5.0. Did I
> > >> miss out anything?
> > >> MEMORY
> > >> ; Name Start Size Type
> > >> ; ------- -------- -------- ----
> > >> RSVD 80000000 000FF000 RESERVED
> > >> ARGS 800FF000 00001000 RESERVED
> > >> NK 9CA80000 01000000 RAMIMAGE
> > >> RAM 80100000 03F00000 RAM
> > >>
> > >> ; Reserve ZBANK virtual block (No physical memory
> > >> ; is required to back this virtual range).
> > >> ;
> > >> ZBANK 96500000 00100000 RESERVED
> > >>
> > >> CONFIG
> > >> ROMSTART=9CA80000
> > >> ROMSIZE=01000000
> > >> ROMWIDTH=32
> > >> AUTOSIZE=OFF
> > >> KERNELFIXUPS=ON
> > >>
> > >> Thanks a lot in advance
> > >>
> > >> Tang
> > >
> > >



Re: Checksum failure when program image to the flash by Wang

Wang
Wed Jan 12 19:13:47 CST 2005

Why jump to 0x9CB01000? I think it should jump to 9CA81000 according to
your OEMAddressTable.

K. S. Huang,what's your opinion?

--
Best wishes
Wang Yeqing
***********************************************************
Intelligent Grouping Research and Development Institute
Amoi Electronics Co., Ltd

Tel: 86-592-6516777-6515
***********************************************************

"Tang" <ymtang@gmail.com>
??????:8812976b.0501112206.83641a6@posting.google.com...
> Thanks you guys, after modifying something in flash.c, the flashing
> can be completed successfully. And the OS can be started right after
> the flashing. However, if I restart the platform, it hangs at the very
> beginning. The following is what I captured from the serial port:
> --------------------
> System ready!
> Preparing for download...
> INFO: Using device name: 'MAINSTN0'
> Download successful! Jumping to image at 0x9CB01000 (physicWindows CE
> Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:25:00
> ProcessorType=0411 Revision=4
> sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 9c
> b05b14
> --------------------
> Any idea on this?
>
> Thanks a lot in advance
>
> Tang
>
>
> "Wang Yeqing" <wangyq@amoi.com.cn> wrote in message
> news:<#5D29Y#9EHA.2196@TK2MSFTNGP11.phx.gbl>...
>> You modify like this:
>>
>> OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, TRUE);
>>
>> Modify FALSE to TRUE.
>>
>>
>>
>> --
>> Best wishes
>> Wang Yeqing
>> ***********************************************************
>> Intelligent Grouping Research and Development Institute
>> Amoi Electronics Co., Ltd
>>
>> Tel: 86-592-6516777-6515
>> ***********************************************************
>>
>> "K. S. Huang" <ks_huang@AlphaNetworks.com_remove.this>
>> дÈëÏûÏ¢ÐÂÎÅ:%23i788u59EHA.2700@TK2MSFTNGP14.phx.gbl...
>> > There is a bug in the OEMIsFlashAddr of flash.c(SRC\BOOTLOADER\EBOOT)
>> >
>> > It only reconized the Unchached Flash Address(0xBCA80000) but NOT for
>> > cached
>> > address(0x9CA80000).
>> > You may fix this issue by patch the OEMIsFlashAddr as the following
>> > codes
>> >
>> > BOOL OEMIsFlashAddr(DWORD dwAddr)
>> > {
>> > DWORD dwVirtFlashStart = (DWORD)
>> > OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, FALSE);
>> >
>> > dwAddr = (DWORD)OALCAtoUA(dwAddr); // <-- patch here
>> >
>> > if ((dwAddr >= dwVirtFlashStart) && (dwAddr <= (dwVirtFlashStart +
>> > MAINSTONEII_SIZE_BOOT_FLASH)))
>> > {
>> > return(TRUE);
>> > }
>> >
>> > return(FALSE);
>> > }
>> >
>> > "Tang" <ymtang@gmail.com>
>> > ???????:8812976b.0501101636.5a0d321f@posting.google.com...
>> >> Hi, All
>> >>
>> >> I modified config.bib to program nk.bin to the flash. But I got
>> >> checksum failure when eboot starts downloading the image. The error
>> >> msg is:
>> >> ****** OEMVerfyMemory checking physical range [0x80000==>0xE16627]...
>> >> ****** FLASH Address ******
>> >> ERROR: Checksum failure (expected=0x2EB computed = 0x2C6)
>> >> *******Checksum failure on record 1, ABORT!!! ******
>> >>
>> >> The config.bib is as follows, the platform is PXA27x WinCE5.0. Did I
>> >> miss out anything?
>> >> MEMORY
>> >> ; Name Start Size Type
>> >> ; ------- -------- -------- ----
>> >> RSVD 80000000 000FF000 RESERVED
>> >> ARGS 800FF000 00001000 RESERVED
>> >> NK 9CA80000 01000000 RAMIMAGE
>> >> RAM 80100000 03F00000 RAM
>> >>
>> >> ; Reserve ZBANK virtual block (No physical memory
>> >> ; is required to back this virtual range).
>> >> ;
>> >> ZBANK 96500000 00100000 RESERVED
>> >>
>> >> CONFIG
>> >> ROMSTART=9CA80000
>> >> ROMSIZE=01000000
>> >> ROMWIDTH=32
>> >> AUTOSIZE=OFF
>> >> KERNELFIXUPS=ON
>> >>
>> >> Thanks a lot in advance
>> >>
>> >> Tang
>> >
>> >



Re: Checksum failure when program image to the flash by K

K
Wed Jan 12 22:30:42 CST 2005

Well, that's a bit strange.
Maybe Tang change the RAMIMAGE record value of config.bib ??

"Wang Yeqing" <wangyq@amoi.com.cn> ¼¶¼g©ó¶l¥ó·s»D
:uGeomyQ#EHA.2196@TK2MSFTNGP11.phx.gbl...
> Why jump to 0x9CB01000? I think it should jump to 9CA81000 according to
> your OEMAddressTable.
>
> K. S. Huang,what's your opinion?
>
> --
> Best wishes
> Wang Yeqing
> ***********************************************************
> Intelligent Grouping Research and Development Institute
> Amoi Electronics Co., Ltd
>
> Tel: 86-592-6516777-6515
> ***********************************************************
>
> "Tang" <ymtang@gmail.com>
> ??????:8812976b.0501112206.83641a6@posting.google.com...
> > Thanks you guys, after modifying something in flash.c, the flashing
> > can be completed successfully. And the OS can be started right after
> > the flashing. However, if I restart the platform, it hangs at the very
> > beginning. The following is what I captured from the serial port:
> > --------------------
> > System ready!
> > Preparing for download...
> > INFO: Using device name: 'MAINSTN0'
> > Download successful! Jumping to image at 0x9CB01000 (physicWindows CE
> > Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:25:00
> > ProcessorType=0411 Revision=4
> > sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 9c
> > b05b14
> > --------------------
> > Any idea on this?
> >
> > Thanks a lot in advance
> >
> > Tang
> >
> >
> > "Wang Yeqing" <wangyq@amoi.com.cn> wrote in message
> > news:<#5D29Y#9EHA.2196@TK2MSFTNGP11.phx.gbl>...
> >> You modify like this:
> >>
> >> OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, TRUE);
> >>
> >> Modify FALSE to TRUE.
> >>
> >>
> >>
> >> --
> >> Best wishes
> >> Wang Yeqing
> >> ***********************************************************
> >> Intelligent Grouping Research and Development Institute
> >> Amoi Electronics Co., Ltd
> >>
> >> Tel: 86-592-6516777-6515
> >> ***********************************************************
> >>
> >> "K. S. Huang" <ks_huang@AlphaNetworks.com_remove.this>
> >> дÈëÏûÏ¢ÐÂÎÅ:%23i788u59EHA.2700@TK2MSFTNGP14.phx.gbl...
> >> > There is a bug in the OEMIsFlashAddr of flash.c(SRC\BOOTLOADER\EBOOT)
> >> >
> >> > It only reconized the Unchached Flash Address(0xBCA80000) but NOT for
> >> > cached
> >> > address(0x9CA80000).
> >> > You may fix this issue by patch the OEMIsFlashAddr as the following
> >> > codes
> >> >
> >> > BOOL OEMIsFlashAddr(DWORD dwAddr)
> >> > {
> >> > DWORD dwVirtFlashStart = (DWORD)
> >> > OALPAtoVA(MAINSTONEII_BASE_PA_BOOT_FLASH, FALSE);
> >> >
> >> > dwAddr = (DWORD)OALCAtoUA(dwAddr); // <-- patch here
> >> >
> >> > if ((dwAddr >= dwVirtFlashStart) && (dwAddr <= (dwVirtFlashStart +
> >> > MAINSTONEII_SIZE_BOOT_FLASH)))
> >> > {
> >> > return(TRUE);
> >> > }
> >> >
> >> > return(FALSE);
> >> > }
> >> >
> >> > "Tang" <ymtang@gmail.com>
> >> > ???????:8812976b.0501101636.5a0d321f@posting.google.com...
> >> >> Hi, All
> >> >>
> >> >> I modified config.bib to program nk.bin to the flash. But I got
> >> >> checksum failure when eboot starts downloading the image. The error
> >> >> msg is:
> >> >> ****** OEMVerfyMemory checking physical range
[0x80000==>0xE16627]...
> >> >> ****** FLASH Address ******
> >> >> ERROR: Checksum failure (expected=0x2EB computed = 0x2C6)
> >> >> *******Checksum failure on record 1, ABORT!!! ******
> >> >>
> >> >> The config.bib is as follows, the platform is PXA27x WinCE5.0. Did I
> >> >> miss out anything?
> >> >> MEMORY
> >> >> ; Name Start Size Type
> >> >> ; ------- -------- -------- ----
> >> >> RSVD 80000000 000FF000 RESERVED
> >> >> ARGS 800FF000 00001000 RESERVED
> >> >> NK 9CA80000 01000000 RAMIMAGE
> >> >> RAM 80100000 03F00000 RAM
> >> >>
> >> >> ; Reserve ZBANK virtual block (No physical memory
> >> >> ; is required to back this virtual range).
> >> >> ;
> >> >> ZBANK 96500000 00100000 RESERVED
> >> >>
> >> >> CONFIG
> >> >> ROMSTART=9CA80000
> >> >> ROMSIZE=01000000
> >> >> ROMWIDTH=32
> >> >> AUTOSIZE=OFF
> >> >> KERNELFIXUPS=ON
> >> >>
> >> >> Thanks a lot in advance
> >> >>
> >> >> Tang
> >> >
> >> >
>
>