Re: Problems with Serial Downloader for PXA255

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Brian Price (brianp_at_appliedcs.com.au)
Date: 05/18/04 

Date: 17 May 2004 21:31:33 -0700

Thanks Oliver, The retail build works.

spinelliolivier@yahoo.fr (SPINELLI Olivier) wrote in message news:<5271c3d4.0405170003.553ce373@posting.google.com>...
> Hello,
>
> try to build your boot loader in "Retail", it works fine for me.
>
> brianp@appliedcs.com.au (Brian Price) wrote in message news:<83ae2378.0405132115.77c54974@posting.google.com>...
> > Hi all,
> >
> > Environment: WinCE V4.2 + QFEs, PXA255 400MHz custom target
> >
> > I have ported the SBOOT code from CEPC source to the PXA255 target.
> > Our target has two serial ports, so I am using one as a debug output
> > and the other for the connection to the Platform Builder PC.
> >
> > When I attempt a download, the PC and the target exchange data packets
> > and eventually the Platform Builder pops up a "Download OS Image"
> > dialog that reports - Download failed. Review your download service
> > selection and configuration.
> >
> > I then modified the debug output to report the content of the packets
> > so I could capture and analyse them (listing below)
> >
> > My analysis of the packets indicates that the Platform Builder is not
> > attempting to download any data but just sending KITL messages which
> > the boot loader knows nothing about. I have tried modifying the Remote
> > Connection settings but this makes no difference.
> >
> > Does Platform Builder support serial download (and debugging) on an
> > XScale (ARMV4I) target?
> >
> > Is there some configuration I have missed on the Platform Builder?
> >
> > Any suggestions.
> >
> >
> > Note:
> > ==> outgoing frame from device
> > <== incoming frame from PB
> > ----- BEGIN DEBUG LOG ---------------------------------------------
> > System ready!
> > Preparing for download...
> > Configure BTUART
> > Download Port initialized BlueTooth UART
> > Sending boot request...
> > ==> Frame 46 bytes: 6B 49 54 4C BB 00 24 00 2B 5E 53 43 35 30 30 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > Waiting for boot ack...
> > <== Frame 1 bytes: 6B
> > <== Frame 1 bytes: 49
> > <== Frame 1 bytes: 54
> > <== Frame 1 bytes: 4C
> > <== Frame 6 bytes: AA 01 20 00 20 3F
> > <== Frame 32 bytes: 45 44 42 47 FF 00 00 06 01 50 50 53 48 00 6F 01
> > 14 07 00 00 08 29 6F 01 90 FF 09 02 08 FF 00 00
> >
> > received non-download packet type
> > Sending boot request...
> > ==> Frame 46 bytes: 6B 49 54 4C BB 00 24 00 2B 5E 53 43 35 30 30 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > Waiting for boot ack...
> > <== Frame 1 bytes: 6B
> > <== Frame 1 bytes: 49
> > <== Frame 1 bytes: 54
> > <== Frame 1 bytes: 4C
> > <== Frame 6 bytes: DD AC 04 00 00 E1
> > <== Frame 4 bytes: 00 00 00 00
> > Received boot ack
> > ==> Frame 14 bytes: 6B 49 54 4C DD 00 04 00 8A BF 00 00 11 79
> > Received boot request ack... starting download
> > <== Frame 1 bytes: 6B
> > <== Frame 1 bytes: 49
> > <== Frame 1 bytes: 54
> > <== Frame 1 bytes: 4C
> > <== Frame 6 bytes: AA 52 08 00 1B 73
> > <== Frame 8 bytes: 45 44 42 47 FF 00 00 0A
> > received non-download packet type
> > <== Frame 1 bytes: 6B
> > <== Frame 1 bytes: 49
> > <== Frame 1 bytes: 54
> > <== Frame 1 bytes: 4C
> > <== Frame 6 bytes: AA 01 20 00 29 48
> > <== Frame 32 bytes: 45 44 42 47 FF 00 00 06 01 44 42 47 4D 53 47 00
> > 14 07 00 00 08 29 6F 01 90 FF 09 02 08 FF 00 00
> >
> > received non-download packet type
> > <== Frame 1 bytes: 6B
> > <== Frame 1 bytes: 49
> > <== Frame 1 bytes: 54
> > <== Frame 1 bytes: 4C
> > <== Frame 6 bytes: AA 01 20 00 F7 16
> > <== Frame 32 bytes: 45 44 42 47 FF 00 00 06 01 50 50 53 48 00 47 00
> > 14 07 00 00 08 29 6F 01 90 FF 09 02 08 FF 00 00
> >
> > received non-download packet type
> > <== Frame 1 bytes: 6B
> > <== Frame 1 bytes: 49
> > <== Frame 1 bytes: 54
> > <== Frame 1 bytes: 4C
> > <== Frame 6 bytes: AA 01 20 00 29 48
> > <== Frame 32 bytes: 45 44 42 47 FF 00 00 06 01 44 42 47 4D 53 47 00
> > 14 07 00 00 08 29 6F 01 90 FF 09 02 08 FF 00 00
> >
> > received non-download packet type
> >
> > ----- END DEBUG LOG ---------------------------------------------
> >
> > Thanks
> > Brian Price
> > Senior Design Engineer
> > Applied Controls

Relevant Pages

  • Re: serial communication with tcl
    ... I'd like to program with tcl language the serial ports of my arm ... On my target when i tried to execute the following ...
    (comp.lang.tcl)
  • Re: Windows CE image download
    ... Kernel debugger failed to connect with target. ... Hi Mishooax, ... doesn't make any debug output to the attached display. ...
    (microsoft.public.windowsce.embedded)
  • serial communication with tcl
    ... I'd like to program with tcl language the serial ports of my arm ... On my target when i tried to execute the following ...
    (comp.lang.tcl)
  • Re: Newbie - CEPC Adding a network card
    ... You should *get* some debug output. ... OS, something should be coming out one of the serial ports, COM1 on CEPC. ... Prev by Date: ...
    (microsoft.public.windowsce.platbuilder)