Hi
I started porting LinuxBIOS to IWill dk8-htx board. I used the dk8s2 to start
from. After some smaller changes to the Config.lb I could compile it and
flash it with flashrom. Unfortunately it seems that the default_resource_map
is not working.
This is what I get when I debug a little.
LinuxBIOS-1.1.8_Fallback Wed Mar 22 16:32:37 CET 2006 starting...
i386 console_init
report_bist_failure
setup_default_resource_map
setting up resource map....
0000c14c <-00000001
0000c154 <-00000002
0000c15c <-00000003
0000c164 <-00000004
0000c16c <-00000005
0000c174 <-00000006
0000c17c <-00000007
0000c140 <-00000000
0000c148 <-00000000
0000c150 <-00000000
0000c158 <-00000000
0000c160 <-00000000
0000c168 <-00000000
0000c170 <-00000000
0000c178 <-00000000
0000c184 <-00000000
0000c18c <-00000000
0000c194 <-00000000
0000c19c <-00000000
0000c1a4 <-00000000
0000c1ac <-00000000
0000c1b4 <-00000000
0000c1bc <-00ffff00
0000c180 <-00000000
0000c188 <-00000000
0000c190 <-00000000
0000c198 <-00000000
0000c1a0 <-00000000
0000c1a8 <-00000000
0000c1b0 <-00000000
0000c1b8 <-00fc0003
0000c1c4 <-01fff000
0000c1cc <-00000000
0000c1d4 <-
Is there any documentation or specification that can help me setting up this
resourcemap?
phil
Probally need to start doing a checkout and rebuild to a clean
directory after you commit since I suspect you will be adding a lot of
files in near future.
gcc -m32 ... -o crt0.o crt0.s
make[1]: *** No rule to make target
`/projects/LinuxBIOSv2/src/cpu/amd/model_gx2/vsmsetup.c', needed by
`vsmsetup.o'. Stop.
make[1]: Leaving directory
`/projects/LinuxBIOSv2/targets/lippert/frontrunner/frontrunner/normal'
make: *** [normal/linuxbios.rom] Error 1
rsmith@richlap:/projects/LinuxBIOSv2/targets/lippert/frontrunner/frontrunner$
--
Richard A. Smith
I got my eval board today. The bios chip is a sst 49LF002A which is a
firmware hub part.
My ROM emulator won't work. :(
My programmer will program the parts but that means I'm swapping chips
every cycle which sucks.
Do all the GX2 parts use firmware hubs?
What are my non-programmer options for flashing this part?
--
Richard A. Smith
2 years ago I lucked out and picked up a copy of MSVC 1.52 on ebay for a
couple of bucks. It might be worth checking ebay.
Rod
-----Original Message-----
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Richard Smith
Sent: Friday, March 17, 2006 7:31 PM
To: jardel(a)lesc.ufc.br
Cc: LinuxBIOS
Subject: Re: [LinuxBIOS] GX eval board
> > MASM 6.11 + Ms Visual C++ 1.52 (MSVC 1.52) + SLIBC7.LIB works fine.
I
> > tried it.
>
> I think my tools may be too _new_. Even the cl that comes with VC 6
is pukeing
>
Ok. So I read the docs... Yep. You need MSVC 1.52. I don't have
that. Bummer.
--
Richard A. Smith
--
linuxbios mailing list
linuxbios(a)linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
ok, gx2 bios for lippert will now call vsm, and then ... lockup.
for those of you who want to experiment with this ... we're waiting on
our jtag debugger.
ron
>
> just work with what is there, we have a batch of patches due to come in
> by monday.
So pretty much just report back what fails and try to fix it?
Do we have some sort of target feature set?
I don't wan't to spend my efforts on things that someone else is
already in the middle of working on or not relevant to the project.
--
Richard A. Smith
--
Richard A. Smith
Ok.. I got our AMD vendor rep to send me a GX533 board. Probably be
here Monday or Tuesday.
Whats the status of stuff and the TODO list?
--
Richard A. Smith
Hi,
I would like to reduce the address output during flashing, verifying etc
in the flashrom utility. Instead of printing each address, it would be
sufficient to write every 256th address or even every 4096th address:
so we could write
if (verbose && ((i&0xfff)==0))
printf("0x%08x", i);
instead of
if (verbose)
printf("0x%08x", i);
The reason is if you are writing/verifying flash on a reasonably slow
serial console it will take several hours (and hopefully not mess with
the flash timing)
any vetos?
Stefan
--
coresystems GmbH · Brahmsstr. 16 · D-79104 Freiburg i. Br.
Tel.: +49 761 7668825 · Fax: +49 761 7664613
Email: info(a)coresystems.de · http://www.coresystems.de/
Nope. News to me of its existence. Have any idea of the ub driver's
size?
The trick is to get at least restore from USB storage able to be in the
boot flash; I don't mind so much if we have to put TCP/IP and wireless
modules into a partition on the regular flash. And if we can get it
all to fit into less than 512K bytes (BIOS + Linux as bootloader), then
we get to save $.3 to $.5, which over the number of units we're
building, is more than small change.
Thanks,
- Jim
On Wed, 2006-03-15 at 08:45 -0500, Alan Cox wrote:
> On Wed, Mar 15, 2006 at 07:22:57AM -0500, Jim Gettys wrote:
> > The biggest headache we have here is the size of the USB modules for usb
> > storage and wireless,
> and the drivers themselves. This is why we're
>
> Have you looked at Pete Zaitcev's 'ub' driver instead of the full scsi
> stack ?
>
> --
> olpc-software mailing list
> olpc-software(a)redhat.com
> https://www.redhat.com/mailman/listinfo/olpc-software
--
Jim Gettys
One Laptop Per Child
Hi all,
At last... Finally I have had time to look at LinuxBIOS...
I have been playing around with Etherboot and Filo for booting a
development target, making good progress.
Up to now I have managed to add Etherboot to the original BIOS and have
it working fine.
But now I want to LinuxBIOS my system ;-)
I have a Lippert Cool Roadrunner II with 64MB memory and a 128MB
CompactFlash for disk, and I have tried to use LinuxBIOS v1 with its
support for this board, but no success.
The serial port is very quite, and unfortunately I have no POST card. I
have verified the serial connection: Linux on target "$ echo Hello
>/dev/ttyS0" gives a nice "Hello" on the receiving end (no handshakes),
so something seems odd with the LinuxBIOS image...
Host is i686-Linux using gcc-4.0.3
--- config ------------
target /home/pdj/tuxway/builds/roadrunner2
mainboard lippert/roadrunner2
# Enable Serial Console for debugging
option SERIAL_CONSOLE=1
option TTYS0_BAUD=57600
option DEFAULT_CONSOLE_LOGLEVEL=9
option DEBUG=1
option RAMTEST=1
option USE_GENERIC_ROM=1
option USE_ELF_BOOT=1
option ROM_SIZE=262144
option STD_FLASH=1
payload ~/tuxway/etherboot-5.0.6/src/bin32/eepro100.elf
option PAYLOAD_SIZE=196608
---------------
I've hexdump'd the resulting romimage, and it looks fine as far as I can
tell: (jmp far 0xf000:0x0004 at address 0x0003fff0, and payload image
starting at 0x00000000).
I've used the flashrom from LinuxBIOSv2-2191 for burning:
"# flashrom -w romimage"
Anyone able to give me a clue of what I've missed?
Anyone had success with LinuxBIOSv2 on a Roadrunner2 ?
~Per
-----------------
PS:
---
My ultimate goal is fast boot to either a remote image (through
Etherboot) or a local linux on CompactFlash (filo and ext2).
My plan was to use LinuxBIOS with a combined filo and etherboot image as
payload.
Like this:
0x000000 FILO
0x010000 ETHERBOOT
0x030000 LINUXBIOS
0x040000
---
I have already modified filo so an external switch can select the
boot-method.
