Re: [LinuxBIOS] Digital Logic msm800sel
[Please always reply to the mailing list, not individual developers] On Mon, May 21, 2007 at 12:00:37PM -0300, Otávio Alcântara wrote:
I'm using a JTAG debugger and I can't see the initial jmp of bios. It seems like the linuxbios.rom is not well formatted, I mean with the original bios I can debug instruction by instruction, see the bios booting the machine and so on. Flashing the linuxbios.rom seems there is no valid instruction on reset vector.
Hm, sounds bad. You didn't answer my question, though. Did you try using a null-modem cable to see if you get serial debug output? Maybe something's wrong with your jtag (or other) setup? Which code exactly are you using? Please send a patch if it's modified from what is in svn. How are you building LinuxBIOS? How big is your ROM chip? How big is your linuxbios.rom? What's the contents of your targets/.../Config.lb file? Which payload are you using? How did you flash linuxbios.rom on the chip? Are you sure that worked ok? Do you have a POST card? What does it show? Does it "hang" with a certain value at some point? Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Sorry, I'm not using null-modem cable only JTAG interface, and it's okay because works with the original bios. I'm using the last msm800sel version from svn, my flash is 521 Kb, my linuxbios rom plus payload (FILO) is less than 64 Kb, I'm not using fallback, and I use a universal program to flash the rom and it's okay too because a program the original bios with it. On 5/21/07, Uwe Hermann <uwe@hermann-uwe.de> wrote:
[Please always reply to the mailing list, not individual developers]
On Mon, May 21, 2007 at 12:00:37PM -0300, Otávio Alcântara wrote:
I'm using a JTAG debugger and I can't see the initial jmp of bios. It seems like the linuxbios.rom is not well formatted, I mean with the original bios I can debug instruction by instruction, see the bios booting the machine and so on. Flashing the linuxbios.rom seems there is no valid instruction on reset vector.
Hm, sounds bad.
You didn't answer my question, though. Did you try using a null-modem cable to see if you get serial debug output? Maybe something's wrong with your jtag (or other) setup?
Which code exactly are you using? Please send a patch if it's modified from what is in svn. How are you building LinuxBIOS? How big is your ROM chip? How big is your linuxbios.rom? What's the contents of your targets/.../Config.lb file? Which payload are you using? How did you flash linuxbios.rom on the chip? Are you sure that worked ok?
Do you have a POST card? What does it show? Does it "hang" with a certain value at some point?
Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGUbrmXdVoV3jWIbQRAhsLAJoCv6AiAmvmWM5x4HD+m+ersrkHeQCgl0BX hgt61WWpjlI7/YaH/ioM1yg= =vYIw -----END PGP SIGNATURE-----
-- Otávio Alcântara "I'll never cross to the Dark Side."
* Otávio Alcântara <otavio.junior@gmail.com> [070521 18:52]:
Sorry, I'm not using null-modem cable only JTAG interface, and it's okay because works with the original bios. I'm using the last msm800sel version from svn, my flash is 521 Kb, my linuxbios rom plus payload (FILO) is less than 64 Kb, I'm not using fallback, and I use a universal program to flash the rom and it's okay too because a program the original bios with it.
did you pad the image to the flash size? You have to have fallback. If you want only one image you need to drop normal. Normal alone cannot work. -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info@coresystems.de • http://www.coresystems.de/
The linuxbios.rom is 521 Kb, just like the flash. I didn't know fallback is a must to, I'll try a new rom with fallback. Thanks, Otávio On 5/21/07, Stefan Reinauer <stepan@coresystems.de> wrote:
* Otávio Alcântara <otavio.junior@gmail.com> [070521 18:52]:
Sorry, I'm not using null-modem cable only JTAG interface, and it's okay because works with the original bios. I'm using the last msm800sel version from svn, my flash is 521 Kb, my linuxbios rom plus payload (FILO) is less than 64 Kb, I'm not using fallback, and I use a universal program to flash the rom and it's okay too because a program the original bios with it.
did you pad the image to the flash size?
You have to have fallback. If you want only one image you need to drop normal. Normal alone cannot work.
-- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info@coresystems.de • http://www.coresystems.de/
-- Otávio Alcântara "I'll never cross to the Dark Side."
Hello, I tried to build a new linuxbios.rom with fallback and the file size ( 1 Mb ) got larger than flash size (512Kb). Follows the /targets/digitallogic/msm8sel/Config.lb content, I set ROM_SIZE to 521 Kb . target msm800sev mainboard digitallogic/msm800sev option CONFIG_COMPRESSED_PAYLOAD_NRV2B=0 option ROM_SIZE = 1024*512 ## ROM_IMAGE_SIZE is the maximum number of bytes allowed for a LinuxBIOS image, ## not including any payload. option ROM_IMAGE_SIZE=64*1024 option DEFAULT_CONSOLE_LOGLEVEL = 11 option MAXIMUM_CONSOLE_LOGLEVEL = 11 romimage "normal" option USE_FALLBACK_IMAGE=0 option ROM_IMAGE_SIZE=64*1024 option LINUXBIOS_EXTRA_VERSION=".0Normal" payload /home/otavio/Filo/filo-0.5/filo.elf end romimage "fallback" option USE_FALLBACK_IMAGE=1 option ROM_IMAGE_SIZE=64*1024 option LINUXBIOS_EXTRA_VERSION=".0Fallback" payload /home/otavio/Filo/filo-0.5/filo.elf end buildrom ./linuxbios.rom ROM_SIZE "normal" "fallback" Otávio On 5/21/07, Otávio Alcântara <otavio.junior@gmail.com> wrote:
The linuxbios.rom is 521 Kb, just like the flash. I didn't know fallback is a must to, I'll try a new rom with fallback. Thanks,
Otávio
On 5/21/07, Stefan Reinauer <stepan@coresystems.de> wrote:
* Otávio Alcântara <otavio.junior@gmail.com> [070521 18:52]:
Sorry, I'm not using null-modem cable only JTAG interface, and it's okay because works with the original bios. I'm using the last msm800sel version from svn, my flash is 521 Kb, my linuxbios rom plus payload (FILO) is less than 64 Kb, I'm not using fallback, and I use a universal program to flash the rom and it's okay too because a program the original bios with it.
did you pad the image to the flash size?
You have to have fallback. If you want only one image you need to drop normal. Normal alone cannot work.
-- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info@coresystems.de • http://www.coresystems.de/
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Otávio Alcântara "I'll never cross to the Dark Side."
The first thing I ever do with problems of this type is simple: hexdump romimage and see if I see a jump at end. ron
I used a dissambly and there is no jump in the reset vector. I've tried other board (amd rumba, using the same tools JTAG and memory programmer) and it starts normaly the boot process, just don't finish it because the processor is a Geode GX and my board is a LX one. I'll try the norwich board that is similar to mine. The problem I saw with msm800 is that linuxbios.rom is not on a valid format, the file doesn't size like the ROM_SIZE option of targets/../../Config.lb. Thanks, Otávio On 5/23/07, ron minnich <rminnich@gmail.com> wrote:
The first thing I ever do with problems of this type is simple: hexdump romimage
and see if I see a jump at end.
ron
-- Otávio Alcântara "I'll never cross to the Dark Side."
Otávio Alcântara wrote:
I used a dissambly and there is no jump in the reset vector. I've tried other board (amd rumba, using the same tools JTAG and memory programmer) and it starts normaly the boot process, just don't finish it because the processor is a Geode GX and my board is a LX one. I'll try the norwich board that is similar to mine. The problem I saw with msm800 is that linuxbios.rom is not on a valid format, the file doesn't size like the ROM_SIZE option of targets/../../Config.lb.
Thanks,
Otávio
Are you using buildrom? http://linuxbios.org/Buildrom It is recommended to use it for LX systems. It should handle putting the VSA image with the LB binary to make the complete image. Marc
On 5/23/07, *ron minnich* <rminnich@gmail.com <mailto:rminnich@gmail.com>> wrote:
The first thing I ever do with problems of this type is simple: hexdump romimage
and see if I see a jump at end.
ron
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto:Marc.Jones@amd.com http://www.amd.com/embeddedprocessors
Thanks Marc, I will try buildrom. Regards, Otavio On 5/23/07, Marc Jones <marc.jones@amd.com> wrote:
Otávio Alcântara wrote:
I used a dissambly and there is no jump in the reset vector. I've tried other board (amd rumba, using the same tools JTAG and memory programmer) and it starts normaly the boot process, just don't finish it because the processor is a Geode GX and my board is a LX one. I'll try the norwich board that is similar to mine. The problem I saw with msm800 is that linuxbios.rom is not on a valid format, the file doesn't size like the ROM_SIZE option of targets/../../Config.lb.
Thanks,
Otávio
Are you using buildrom?
It is recommended to use it for LX systems. It should handle putting the VSA image with the LB binary to make the complete image. Marc
On 5/23/07, *ron minnich* <rminnich@gmail.com <mailto:rminnich@gmail.com>> wrote:
The first thing I ever do with problems of this type is simple: hexdump romimage
and see if I see a jump at end.
ron
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto:Marc.Jones@amd.com http://www.amd.com/embeddedprocessors
-- Otávio Alcântara "I'll never cross to the Dark Side."
Hello, I used the buildrom tool, but the norwich board uses the companion serial and my board uses SUPERIO WINBOND w83267hf. So, I modified the code of /mainboar/amd/norwich/cache_as_ram_auto.c to work with this chip. It worked fine, but the boot process stop with : Before VSA: do_vsmbios I'm not including the vsa in the linuxbios.rom, is that the problem? And how can I concatenate the two files correctly? Regards, Otávio Alcântara On 5/24/07, Otávio Alcântara <otavio.junior@gmail.com> wrote:
Thanks Marc,
I will try buildrom.
Regards,
Otavio
On 5/23/07, Marc Jones < marc.jones@amd.com > wrote:
Otávio Alcântara wrote:
I used a dissambly and there is no jump in the reset vector. I've tried other board (amd rumba, using the same tools JTAG and memory programmer) and it starts normaly the boot process, just don't finish it because the processor is a Geode GX and my board is a LX one. I'll try
the norwich board that is similar to mine. The problem I saw with msm800 is that linuxbios.rom is not on a valid format, the file doesn't size like the ROM_SIZE option of targets/../../Config.lb.
Thanks,
Otávio
Are you using buildrom?
It is recommended to use it for LX systems. It should handle putting the
VSA image with the LB binary to make the complete image. Marc
On 5/23/07, *ron minnich* < rminnich@gmail.com <mailto: rminnich@gmail.com>> wrote:
The first thing I ever do with problems of this type is simple: hexdump romimage
and see if I see a jump at end.
ron
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto: Marc.Jones@amd.com http://www.amd.com/embeddedprocessors
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Otávio Alcântara "I'll never cross to the Dark Side."
Ühel kenal päeval (kolmapäev 30 mai 2007 3:31 pm) kirjutas Otávio Alcântara:
Hello,
I used the buildrom tool
Did you have trouble with buildrom-devel? I mean building the packages etc. Currently I can't get it to work. sed tool can be sensitive to locale (in bad way). I have seen that several times and the solution is that my estonian default needs "export LC_ALL=en" and things start working (especiell configure scripts ). What is your default locale and did you have similar trouble? thanks, Indrek
, but the norwich board uses the companion serial and my board uses SUPERIO WINBOND w83267hf. So, I modified the code of /mainboar/amd/norwich/cache_as_ram_auto.c to work with this chip. It worked fine, but the boot process stop with :
Before VSA: do_vsmbios
I'm not including the vsa in the linuxbios.rom, is that the problem? And how can I concatenate the two files correctly?
Regards,
Otávio Alcântara
On 5/24/07, Otávio Alcântara <otavio.junior@gmail.com> wrote:
Thanks Marc,
I will try buildrom.
Regards,
Otavio
On 5/23/07, Marc Jones < marc.jones@amd.com > wrote:
Otávio Alcântara wrote:
I used a dissambly and there is no jump in the reset vector. I've
tried
other board (amd rumba, using the same tools JTAG and memory programmer) and it starts normaly the boot process, just don't finish
it
because the processor is a Geode GX and my board is a LX one. I'll try
the norwich board that is similar to mine. The problem I saw with msm800 is that linuxbios.rom is not on a valid format, the file doesn't size like the ROM_SIZE option of targets/../../Config.lb.
Thanks,
Otávio
Are you using buildrom?
It is recommended to use it for LX systems. It should handle putting the
VSA image with the LB binary to make the complete image. Marc
On 5/23/07, *ron minnich* < rminnich@gmail.com <mailto: rminnich@gmail.com>> wrote:
The first thing I ever do with problems of this type is simple: hexdump romimage
and see if I see a jump at end.
ron
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto: Marc.Jones@amd.com http://www.amd.com/embeddedprocessors
-- Otávio Alcântara "I'll never cross to the Dark Side."
Hi Indrek, I didn't get problems with buildrom, the only problem is that it gets the files from svn and I needed modify some files, so I compiled the linuxbios by hand. My Locale is pt_BR and char set is UTF-8. Regards, Otávio On 5/30/07, Indrek Kruusa <indrek.kruusa@artecdesign.ee> wrote:
Ühel kenal päeval (kolmapäev 30 mai 2007 3:31 pm) kirjutas Otávio Alcântara:
Hello,
I used the buildrom tool
Did you have trouble with buildrom-devel? I mean building the packages etc. Currently I can't get it to work.
sed tool can be sensitive to locale (in bad way). I have seen that several times and the solution is that my estonian default needs "export LC_ALL=en" and things start working (especiell configure scripts ). What is your default locale and did you have similar trouble?
thanks, Indrek
, but the norwich board uses the companion serial and my board uses SUPERIO WINBOND w83267hf. So, I modified the
code
of /mainboar/amd/norwich/cache_as_ram_auto.c to work with this chip. It worked fine, but the boot process stop with :
Before VSA: do_vsmbios
I'm not including the vsa in the linuxbios.rom, is that the problem? And how can I concatenate the two files correctly?
Regards,
Otávio Alcântara
On 5/24/07, Otávio Alcântara <otavio.junior@gmail.com> wrote:
Thanks Marc,
I will try buildrom.
Regards,
Otavio
On 5/23/07, Marc Jones < marc.jones@amd.com > wrote:
Otávio Alcântara wrote:
I used a dissambly and there is no jump in the reset vector. I've
tried
other board (amd rumba, using the same tools JTAG and memory programmer) and it starts normaly the boot process, just don't finish
it
because the processor is a Geode GX and my board is a LX one. I'll try
the norwich board that is similar to mine. The problem I saw with msm800 is that linuxbios.rom is not on a valid format, the file doesn't size like the ROM_SIZE option of targets/../../Config.lb.
Thanks,
Otávio
Are you using buildrom?
It is recommended to use it for LX systems. It should handle putting the
VSA image with the LB binary to make the complete image. Marc
On 5/23/07, *ron minnich* < rminnich@gmail.com <mailto: rminnich@gmail.com>> wrote:
The first thing I ever do with problems of this type is simple: hexdump romimage
and see if I see a jump at end.
ron
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto: Marc.Jones@amd.com http://www.amd.com/embeddedprocessors
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Otávio Alcântara "I'll never cross to the Dark Side."
On 30/05/07 10:33 -0300, Otávio Alcântara wrote:
Hi Indrek,
I didn't get problems with buildrom, the only problem is that it gets the files from svn and I needed modify some files, so I compiled the linuxbios by hand. My Locale is pt_BR and char set is UTF-8.
You can change buildrom to use a local LB directory: select CONFIG_ADVANCED select CONFIG_LB_USE_BUILD and for CONFIG_LBBUILDDIR specify the full path to your linuxBIOS tree. This is from my .config: CONFIG_ADVANCED=y CONFIG_LB_USE_BUILD=y CONFIG_LB_BUILDDIR="/home/jcrouse/linuxbios" We are in some serious need of documentation - but I'm pretty busy. Any volunteers are gratefully accepted. Jordan -- Jordan Crouse Senior Linux Engineer Advanced Micro Devices, Inc. <www.amd.com/embeddedprocessors>
On 30/05/07 16:23 +0300, Indrek Kruusa wrote:
sed tool can be sensitive to locale (in bad way). I have seen that several times and the solution is that my estonian default needs "export LC_ALL=en" and things start working (especiell configure scripts ). What is your default locale and did you have similar trouble?
Ouch - I admit I don't often seen those problems. What is happening exactly, and where is it breaking? Jordan
Ühel kenal päeval (kolmapäev 30 mai 2007 6:16 pm) kirjutas Jordan Crouse:
On 30/05/07 16:23 +0300, Indrek Kruusa wrote:
sed tool can be sensitive to locale (in bad way). I have seen that several times and the solution is that my estonian default needs "export LC_ALL=en" and things start working (especiell configure scripts ). What is your default locale and did you have similar trouble? Otávio Ouch - I admit I don't often seen those problems. What is happening exactly, and where is it breaking?
Fortunately it was a wrong alarm. I just expected that buildrom is not broken in svn :) In other hand I saw that Otávio can be someone who can tell something about troubles due to locale settings. Sry, it's time to go home :) thanks, Indrek
Otávio, Otávio Alcântara wrote:
Hello,
I used the buildrom tool, but the norwich board uses the companion serial and my board uses SUPERIO WINBOND w83267hf. So, I modified the code of /mainboar/amd/norwich/cache_as_ram_auto.c to work with this chip. It worked fine, but the boot process stop with :
Before VSA: do_vsmbios
I'm not including the vsa in the linuxbios.rom, is that the problem? And how can I concatenate the two files correctly?
Regards,
Otávio Alcântara
Yes you need VSA2 in the ROM. You can use buildrom in advance mode to set a local linuxbios tree. Buildrom pulls the VSA binary from here: http://www.amd.com/us-en/ConnectivitySolutions/ProductInformation/0,,50_2330... un-zip it "cat lx_vsa.36k.bin norwich.rom > lb_norwich.rom" You should end up with a 512KB ROM image. Marc
On 5/24/07, *Otávio Alcântara* <otavio.junior@gmail.com <mailto:otavio.junior@gmail.com>> wrote:
Thanks Marc,
I will try buildrom.
Regards,
Otavio
On 5/23/07, *Marc Jones* < marc.jones@amd.com <mailto:marc.jones@amd.com>> wrote:
Otávio Alcântara wrote: > I used a dissambly and there is no jump in the reset vector. I've tried > other board (amd rumba, using the same tools JTAG and memory > programmer) and it starts normaly the boot process, just don't finish it > because the processor is a Geode GX and my board is a LX one. I'll try > the norwich board that is similar to mine. > The problem I saw with msm800 is that linuxbios.rom is not on a valid > format, the file doesn't size like the ROM_SIZE option of > targets/../../Config.lb. > > Thanks, > > Otávio >
Are you using buildrom?
http://linuxbios.org/Buildrom <http://linuxbios.org/Buildrom>
It is recommended to use it for LX systems. It should handle putting the VSA image with the LB binary to make the complete image. Marc
> On 5/23/07, *ron minnich* < rminnich@gmail.com <mailto:rminnich@gmail.com> > <mailto: rminnich@gmail.com <mailto:rminnich@gmail.com>>> wrote: > > The first thing I ever do with problems of this type is simple: > hexdump romimage > > and see if I see a jump at end. > > ron > > > > > -- > Otávio Alcântara > "I'll never cross to the Dark Side." >
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto: Marc.Jones@amd.com <mailto:Marc.Jones@amd.com> http://www.amd.com/embeddedprocessors
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto:Marc.Jones@amd.com http://www.amd.com/embeddedprocessors
I should clarify, buildrom can automatically do the LB image + VSA2 concatenate for you. Follow the instructions to do it by hand. Marc Jones wrote:
Otávio,
Otávio Alcântara wrote:
Hello,
I used the buildrom tool, but the norwich board uses the companion serial and my board uses SUPERIO WINBOND w83267hf. So, I modified the code of /mainboar/amd/norwich/cache_as_ram_auto.c to work with this chip. It worked fine, but the boot process stop with :
Before VSA: do_vsmbios
I'm not including the vsa in the linuxbios.rom, is that the problem? And how can I concatenate the two files correctly?
Regards,
Otávio Alcântara
Yes you need VSA2 in the ROM. You can use buildrom in advance mode to set a local linuxbios tree. Buildrom pulls the VSA binary from here: http://www.amd.com/us-en/ConnectivitySolutions/ProductInformation/0,,50_2330...
un-zip it "cat lx_vsa.36k.bin norwich.rom > lb_norwich.rom" You should end up with a 512KB ROM image.
Marc
On 5/24/07, *Otávio Alcântara* <otavio.junior@gmail.com <mailto:otavio.junior@gmail.com>> wrote:
Thanks Marc,
I will try buildrom.
Regards,
Otavio
On 5/23/07, *Marc Jones* < marc.jones@amd.com <mailto:marc.jones@amd.com>> wrote:
Otávio Alcântara wrote: > I used a dissambly and there is no jump in the reset vector. I've tried > other board (amd rumba, using the same tools JTAG and memory > programmer) and it starts normaly the boot process, just don't finish it > because the processor is a Geode GX and my board is a LX one. I'll try > the norwich board that is similar to mine. > The problem I saw with msm800 is that linuxbios.rom is not on a valid > format, the file doesn't size like the ROM_SIZE option of > targets/../../Config.lb. > > Thanks, > > Otávio >
Are you using buildrom?
http://linuxbios.org/Buildrom <http://linuxbios.org/Buildrom>
It is recommended to use it for LX systems. It should handle putting the VSA image with the LB binary to make the complete image. Marc
> On 5/23/07, *ron minnich* < rminnich@gmail.com <mailto:rminnich@gmail.com> > <mailto: rminnich@gmail.com <mailto:rminnich@gmail.com>>> wrote: > > The first thing I ever do with problems of this type is simple: > hexdump romimage > > and see if I see a jump at end. > > ron > > > > > -- > Otávio Alcântara > "I'll never cross to the Dark Side." >
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto: Marc.Jones@amd.com <mailto:Marc.Jones@amd.com> http://www.amd.com/embeddedprocessors
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto:Marc.Jones@amd.com http://www.amd.com/embeddedprocessors
Thanks to all, I've got concatened both files by hand, I'll try use buildrom next time, it looks easier. The boot got normal until the southbridge setup, it seems to stop on the usart setup. I'll investigate more later. Best Regards, Otávio Alcântara On 5/30/07, Marc Jones <marc.jones@amd.com> wrote:
I should clarify, buildrom can automatically do the LB image + VSA2 concatenate for you. Follow the instructions to do it by hand.
Marc Jones wrote:
Otávio,
Otávio Alcântara wrote:
Hello,
I used the buildrom tool, but the norwich board uses the companion serial and my board uses SUPERIO WINBOND w83267hf. So, I modified the code of /mainboar/amd/norwich/cache_as_ram_auto.c to work with this chip. It worked fine, but the boot process stop with :
Before VSA: do_vsmbios
I'm not including the vsa in the linuxbios.rom, is that the problem? And how can I concatenate the two files correctly?
Regards,
Otávio Alcântara
Yes you need VSA2 in the ROM. You can use buildrom in advance mode to set a local linuxbios tree. Buildrom pulls the VSA binary from here:
http://www.amd.com/us-en/ConnectivitySolutions/ProductInformation/0,,50_2330...
un-zip it "cat lx_vsa.36k.bin norwich.rom > lb_norwich.rom" You should end up with a 512KB ROM image.
Marc
On 5/24/07, *Otávio Alcântara* <otavio.junior@gmail.com <mailto:otavio.junior@gmail.com>> wrote:
Thanks Marc,
I will try buildrom.
Regards,
Otavio
On 5/23/07, *Marc Jones* < marc.jones@amd.com <mailto:marc.jones@amd.com>> wrote:
Otávio Alcântara wrote: > I used a dissambly and there is no jump in the reset vector. I've tried > other board (amd rumba, using the same tools JTAG and
memory
> programmer) and it starts normaly the boot process, just
don't
finish it > because the processor is a Geode GX and my board is a LX
one.
I'll try > the norwich board that is similar to mine. > The problem I saw with msm800 is that linuxbios.rom is not
on
a valid > format, the file doesn't size like the ROM_SIZE option of > targets/../../Config.lb. > > Thanks, > > Otávio >
Are you using buildrom?
http://linuxbios.org/Buildrom <http://linuxbios.org/Buildrom>
It is recommended to use it for LX systems. It should handle putting the VSA image with the LB binary to make the complete image. Marc
> On 5/23/07, *ron minnich* < rminnich@gmail.com <mailto:rminnich@gmail.com> > <mailto: rminnich@gmail.com <mailto:rminnich@gmail.com>>>
wrote:
> > The first thing I ever do with problems of this type is
simple:
> hexdump romimage > > and see if I see a jump at end. > > ron > > > > > -- > Otávio Alcântara > "I'll never cross to the Dark Side." >
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto: Marc.Jones@amd.com <mailto:Marc.Jones@amd.com> http://www.amd.com/embeddedprocessors
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Otávio Alcântara "I'll never cross to the Dark Side."
-- Marc Jones Senior Software Engineer (970) 226-9684 Office mailto:Marc.Jones@amd.com http://www.amd.com/embeddedprocessors
-- Otávio Alcântara "I'll never cross to the Dark Side."
participants (7)
-
Indrek Kruusa -
Jordan Crouse -
Marc Jones -
Otávio Alcântara -
ron minnich -
Stefan Reinauer -
Uwe Hermann