Re: problem in downloading nk.bin

Sorry, but that's no debug output, that's just the bootloader's
"normal" output so It's pretty much useless. In the OP say you've
"developed" the bootloader. Have you actually written any code for the
bootloader, or do you simply mean you've compiled and flashed it? If
you've actually done development, you probably have access to a JTAG
debugger. Do you have access to a JTAG debugger? If you don't you must
instrument the code to output more information of what it's doing (or
better yet, get a JTAG debugger).

Henrik Viklund
http://www.addlogic.se

Chitra skrev:

HI Bruce,
Thank you for your reply. My debug info is at hyperterminal
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
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Locked Down Link 1
Src IP 172.16.5.35 Port 0400 Dest IP 172.16.5.31 Port 0C62
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp

I don't whether the above debug message are right, since I am new to
wince

After this, I found in ethereal the development workstation sends UDP
packets which has 516 bytes of data and my target sends UDP packet
which has 4 bytes of data alternatively. After downloading 1.9MB the
target stops sending UDP packet and the development workstation also
stops after sending 4 UDP packets. And there are no further debug
message on my hyperterminal and I think in the bootloader it stops
while receiving network packets and the code crashes and no information
such as PC is available in AXD debugger. Please reply

Thanks & Regards,
Chitra









Bruce Eitman [eMVP] wrote:
You really need to provide some debug information. You haven't told us much
other than it stops after 13%. What happens in the bootloader? Where does
it stop, in the bootloader?

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Chitra" <chitrar25@xxxxxxxxxxx> wrote in message
news:1169195963.312440.164100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi Henrik,

Thank you very much for your reply. I am not flashing the image I
am storing in SDRAM. Here is my boot.bib and config.bib files
MEMORY
; Name Start Size Type
; ------- -------- -------- ----
IF MX21TO11 !
EBOOT 80040000 00040000 RAMIMAGE
ELSE
EBOOT 80040000 00040000 RAMIMAGE
ENDIF

RAM 80080000 00080000 RAM

; Driver globals area (used to pass config info to kernel, don't change
unless
; you update config.bib) NOTE: We're using physical addresses here.
DRV_GLB 80000000 00001000 RESERVED
STACK 80001000 0003B000 RESERVED
PAGE_TABLE 8003C000 00004000 RESERVED
FRAMEBUFFER 80100000 00100000 RESERVED
; Flash cache (used to store eboot.bin or nk.bin before flashing)
FCACHE 80200000 01F00000 RESERVED

CONFIG
COMPRESSION=OFF
KERNELFIXUPS=OFF


IF MX21TO11 !
ROMSTART=80040000
ROMSIZE=00040000
ELSE
ROMSTART=80040000
ROMSIZE=00040000
ENDIF
ROMWIDTH=32


; Flash starts at 0x10000000 == 0x8FFB0000 + 0x80040000
; For TO1.1, Flash starts at 0x80004000 == 0xF7FC4000 + 0x88040000
ROMOFFSET=0X8FFB0000


confib.bib
MEMORY
; OEM specific reserved ram areas
DRVGLOBAL 80000000 00001000 RESERVED
RESERVED1 80001000 0000F000 RESERVED
DMA 80030000 000D0000 RESERVED
FRAMEBUFFER 80100000 00200000 RESERVED

NK 80300000 02300000 RAMIMAGE ; 35 MB
RAM 82600000 01A00000 RAM ; 26 MB
EDBG 80010000 00020000 RESERVED



; ** Configuration **
CONFIG

AUTOSIZE=ON
ROMSTART=80300000
ROMWIDTH=32
ROMSIZE=02300000


COMPRESSION=OFF


KERNELFIXUPS=ON

My eboot is in location 80040000 to 80080000 and my nk.bin is at loc
80300000. According to me it won't overwrite the bootloader. But I
don't know why code crashes after downloading 13% of image. Any clue
what could be wrong. Please reply.



Henrik Viklund wrote:
Chitra skrev:
Thank you for your reply.
Now the transfer rate is increased to 47kb/sec and it downloads till
13% i.e, 1.9MB and then gets disconnected.

OK. That's still slow. Are you flashing the image on-the-fly, or are
you just storing it to RAM?

I checked in ethereal during download process,
I found UDP packets sent by target and development workstation. The
development workstation sends UDP packet which has 516 bytes and then
target sends UDP packet which has 4 bytes of data alternately. I found

PB uses the TFTP protocol (on port 980) so if you want to you can let
ethereal map that protocol onto the frames. 512+4 out and 4 in is just
as expected. No resends indicate that the device atleast dosn't seem to
drop random frames.

that after downloading 1.9MB, my target doesn't send any packet,
whereas development workstation sends 4 UDP packet and then it stops
sending the UDP packets. I am not able to find out why the target
stopped sending packets. Can anybody help. Please reply.

Well, this is where it gets tricky. Had you provided any sort of debug
info it would be a lot easier. You could be overwriting someting
important (like the bootloader itself), you've got a rotten ethernet
lib, the watchdog kicks in etc, etc, etc. There are *endless*
possibilities!

You say you've developed the bootloader, so you must have a JTAG
debugger? Debug output over serial? LEDs?

Henrik Viklund
http://www.addlogic.se

Thanks & regards,
Chitra

Henrik Viklund wrote:
7 kb/s ?!? You got a *serious* performance issue here. Not knowing
exactly what your board is capable of, I'd expect at least a couple
of
hundred kb/second download rates. Are you using a debug built
bootloader?

The syptom you describe may happen if PB thinks it lost contact with
the device. What happens is probably that PB don't get acks fast
enough
(or that it did too many retries), or that your device has stopped
responding alltogether. Use a software ethernet analyzer such as
ethereal to see what communication takes place between the device and
host during download, if there are lots of resends, if the device is
allways slow to respond etc.

Henrik Viklund
http://www.addlogic.se

Chitra skrev:

Hi all,

I am developing BSP for MC9328MXL litekit. I have developed
the
bootloader. I am not able to download nk.bin. The board has CS8900A
ethernet controller. Platform Builder recognizes the target device
and
download window pops up and it displays downloading nk.bin at a
rate of
7KB/SEC but after 7% is complete, the dialog box closes and in
platform
builder I get the message as
The Kernel Debugger has been successfully disconnected.
I don't know what the problem could be. Please reply.

Thanks & Regards,
Chitra


.

Relevant Pages

  • Re: problem in downloading nk.bin
    ... Sent BOOTME to 255.255.255.255 ... I don't whether the above debug message are right, ... target stops sending UDP packet and the development workstation also ... RESERVED1 80001000 0000F000 RESERVED ...
    (microsoft.public.windowsce.platbuilder)
  • Re: problem in downloading nk.bin
    ... You really need to provide some debug information. ... What happens in the bootloader? ... RESERVED1 80001000 0000F000 RESERVED ... hundred kb/second download rates. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: problem in downloading nk.bin
    ... Thank you very much, Now I can download the nk.bin, the problem was ... bootloader, or do you simply mean you've compiled and flashed it? ... target stops sending UDP packet and the development workstation also ... RESERVED1 80001000 0000F000 RESERVED ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Debugging Interrupt Vector Tables (IVTs)
    ... A more useful question would be centred on why you want to "debug IVT". ... able to debug using the debugger without loosing any control if i debug ... within the bootloader /application. ...
    (comp.os.linux.embedded)
  • Re: Debug works, Release hangs
    ... I am certain I am building my image with KITL disabled. ... Does the bootloader need to disable KITL somehow? ... Are there Build Options I need to change between Debug and Release builds ... >> Hit space to enter configuration menu 5... ...
    (microsoft.public.windowsce.embedded)