Re: Release build
From: Stuart (stuart_at_stopspam.com)
Date: 08/11/04
- Next message: Bud Cookson: "Medical Devices"
- Previous message: Dean Ramsier: "Re: Passing Data between an ISR and an IST"
- In reply to: Sujith: "Re: Release build"
- Next in thread: Sujith: "Re: Release build"
- Reply: Sujith: "Re: Release build"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 11 Aug 2004 09:13:25 -0500
What is your board? Is it similar to any of the ARM boards that ship with
Windows CE? I would stick with the plan to work with the ARM Integrator BSP
and modify that as necessary. I didn't install it, so I'm not sure what
those constants are for.
How are you loading the sboot.nb0 onto your hardware? You say you are using
tera term. That implies to me that you have some type of a loader on your
system already? I may be mistaken, but I think that nb0 files are raw files
whereas the bin files have record headers and such which make them more
appropriate for loading into flash using a bootloader.
I would think that you need to burn the bootloader into your flash (either
using some in system programmer such as JTAG etc. or using a chip programmer
and then soldering it to your board). All this would need to be working
before you can start working with tera term, but maybe I'm missing
something.
I would imagine poeple would agree that developing a bootloader from scratch
is a fairly tough thing to do unless you have some type of hardware debugger
for your system (like something that works over JTAG), and even then it will
take some time to get working.
As a suggestion, I would think that most people would advocate working with
an ethernet bootloader as opposed to a serial one these days, but I'm sure
that people are still using serial bootloaders.
"Sujith" <sujithss@hotmail.com> wrote in message
news:e9zj3e1fEHA.3292@TK2MSFTNGP10.phx.gbl...
> hi,
> thanks for the replay.
> my target processor is ARM.
> i said, i have not mentioned any options like release/debug.
> also, i don't have a BSP also. i created a directory under\platform, as
> myplatform
> and i am working as per the PB help file only(updated on NOV 2003).
> i build a Serial Boot loader. it seems to be working. i am in the process
of
> building the NK.BIN.
> how do i set the constants?
> NK 88070000 00600000 RAMIMAGE
> RAM 88670000 00890000 RAM
> i know that the NK runs on only after the 2GB memory space, but still is
> there anything
> to be taken in to consideration from processor specific point?
> the problem here is my USB map start addredd is 80000000 to 64 M.
> i saw in ARMINTEGRETOR BSP, the NK has the following configuration
> NK 80040000 01F80000 RAMIMAGE. what exactly is the criteria to
> select the virtual address for the kernel, as well as these constants
> VA_HDR_BASE,
> VA_CT_BASE,VA_IC_BASE ,VA_UART0_BASE,
> VA_UART1_BASE,VA_DBG_BASE,VA_RTC_BASE.
> also, how do i download the image to the board?
> first, i download the sboot.nb0 through teraterm, then i start it
manually,
> after from the PB,
> when i try to connect to remote platform, it is not getting connected.
> i configured the remote connection as serial with following setting.
>
> PORT : COM1
> BAUD RATE : 115200
> FLOW Control : None
> Data Bits : 8
> Parity : None
> Stop Bits : 1
>
> how do i move further? please advise.
> Regards
> Sujith
>
>
> "Stuart" <stuart@stopspam.com> wrote in message
> news:%23QEDdhtfEHA.3964@TK2MSFTNGP12.phx.gbl...
> > What processor are you targeting?
> >
> > Are you able to do a debug build right now?
> >
> > I would imagine that you would first want to at least create a BSP, even
> if
> > it hardly does anything and doesn't actually work right, but at least
> > builds. Then I think you would create a project based on that BSP. If
your
> > bootloader relies on any system libraries or headers then they would
have
> > hopefully been built already. Also when you open up a command prompt,
the
> > directories would be set up as to where the output of the build goes.
> >
> > But actually this is a topic that I've wondered about as well, because I
> > have only started with existing BSPs. So someone else would have to say
> > whether that is the right order of operations or not.
> >
> > Anyway, if you open a command prompt from the PB IDE using:
> > Build | Open Build Release Directory
> > I think it basically calls cmd.exe to open a command prompt, and it also
> > calls wince.bat with the appropriate platform, processor, and project
name
> > parameters. Also it will have set a variable as either:
> >
> > WINCEDEBUG=debug
> >
> > or
> >
> > WINCEDEBUG=retail
> >
> > depending on if you have set a debug or release build in
> >
> > Build | Set Active Configuration
> >
> >
> > "Sujith" <sujithss@hotmail.com> wrote in message
> > news:O0htscqfEHA.3632@TK2MSFTNGP09.phx.gbl...
> > > hi all,
> > > how to make a release build for a boot loader?
> > > I don't have a BSP as of now.
> > > I am trying to build it in command line.
> > > also I am not specifying any command line options as of now.
> > > thanks in advance.
> > > regards
> > > sujith
> > >
> > >
> >
> >
>
>
- Next message: Bud Cookson: "Medical Devices"
- Previous message: Dean Ramsier: "Re: Passing Data between an ISR and an IST"
- In reply to: Sujith: "Re: Release build"
- Next in thread: Sujith: "Re: Release build"
- Reply: Sujith: "Re: Release build"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
