Re: startup.s --> main.c (boot loader problem)
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Wed, 19 Apr 2006 09:23:04 -0400
You just have to initialize the stack pointer to use an area of memory that
isn't otherwise used. You can look at your eboot.bib file to see what
memory regions are used by eboot, pick something that doesn't conflict.
Usually, you use an area that is just before or just after the bootloader
RAMIMAGE area, but it could be anywhere.
--
Dean Ramsier - eMVP
BSQUARE Corporation
"waltershao" <waltershao@xxxxxxxxx> wrote in message
news:1145414368.744608.186430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks. Could you tell me how to check if the stack is set up
properly? My startup.s is modified based on the existing linux's start
up code. The stack initial code is almost the same. I don't know why
Linux's boot loader can work fine, but mine will get that trouble. Is
there any difference I should take care? Is something to do with
eboot.bib?
.
- Follow-Ups:
- Re: startup.s --> main.c (boot loader problem)
- From: Steve Maillet \(eMVP\)
- Re: startup.s --> main.c (boot loader problem)
- References:
- startup.s --> main.c (boot loader problem)
- From: waltershao
- Re: startup.s --> main.c (boot loader problem)
- From: Dean Ramsier
- Re: startup.s --> main.c (boot loader problem)
- From: waltershao
- startup.s --> main.c (boot loader problem)
- Prev by Date: Re: TRACE output on COM1
- Next by Date: Re: Stream
- Previous by thread: Re: startup.s --> main.c (boot loader problem)
- Next by thread: Re: startup.s --> main.c (boot loader problem)
- Index(es):
Relevant Pages
|