[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] Please, I need your help about petalinux and the U-boot bootloader
Hi Kevin,
Thanks for your answer. Yes, I'm using EDK 9.1 SP2.
I'm actually using the Rev A board, I must have missed that John used a
different board in his original mail. Does the same solution apply to the
Rev A board?
Regards,
Kristoffer Hedberg
> Hi, Kristoffer
>
> Are you using EDK 9.1.2?
>
> Please make sure your DDR test passed before doing any application
> development.
> The hardware generated with 9.1.2 BSB will not have a working DDR.
> Please add the following into your UCF (data/system.ucf)
>
> For Rev D board;
> NET fpga_0_DDR_SDRAM_32Mx16_DDR_DQ_pin<*> NODELAY;
> NET fpga_0_DDR_SDRAM_32Mx16_DDR_DQS_pin<*> NODELAY;
>
> For Rev C board:
> NET fpga_0_DDR_SDRAM_16Mx16_DDR_DQ_pin<*> NODELAY;
> NET fpga_0_DDR_SDRAM_16Mx16_DDR_DQS_pin<*> NODELAY;
>
> B.R.
> Kevin
>
>
> -----Original Message-----
> From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
> [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Kristoffer
> Hedberg
> Sent: Thursday, October 25, 2007 10:51 PM
> To: microblaze-uclinux@xxxxxxxxxxxxxx
> Subject: Re: [microblaze-uclinux] Please, I need your help about
> petalinux and the U-boot bootloader
>
> Hello,
>
> I have the exact same problem. I have verified that the address mappings
> are correct. The board boots with the pre-built reference design, but it
> hangs when I try to boot with a reference design I compiled myself after
> the message "FS-BOOT: Booting image...". Any further ideas why this
> happens?
>
> Regards,
> Kristoffer Hedberg
>
>> Hi John O,
>> In that case, have you check if your U-Boot image is linked to the
>> correct address by using the mb-objdump -t command?
>>
>> The u-boot elf image resides in the .../petalinux-dist/u-boot/u-boot.
>>
>> If the linked address is not in your hardware ddr memory address range
>
>> as specified in your system.mhs file then it means that your hardware
>> configurations has not yet been pass down to the petalinux kernel
> build.
>>
>> There could be a few reasons for this.
>>
>> * You are using the wrong version of or not using PetaLinux BSB in
>> your system.xmp file and it did not build the auto config files for
>> your platform when you run "make -f system.make libs".
>>
>> * The petalinux-copy-autoconfig has not been run or has copied the
>> auto config files to the wrong platform.
>>
>> You can look at your platform's auto-config.in or Kconfig.auto file to
>
>> check if it has the correct address map.
>>
>> Your platform's auto-config.in file should resides in (Substitute as
>> per appropriate for 2.6.).
>>
>> linux-2.4.x/arch/microblaze/platform/<your platform
>> name>/auto-config.in
>>
>> If this is not the same it means the problem may be with the auto
>> config files have not been generated or not being copied over.
>>
>> If this is the same then make sure that you have selected the correct
>> Vendor and platform for your target in your make menuconfig and clean
>> and rebuild your kernel and check again if you now have the correct
>> address map.
>>
>> Last but not least if the U-Boot linked address is in your hardware
>> address range then maybe it has got to do with the Revision D. I have
>
>> not tested this out so I am not sure if it will work.
>>
>> What you can do is to load the u-boot image manually into memory using
>
>> xmd and debug from there.
>>
>> Cheers,
>> Benny
>>
>>
>> run petalinux-copy-autoconfig from anywhere in your petalinfux tree to
>
>> copy the
>>
>> http://developer.petalogix.com/wiki/UserGuide/Basics/AutoConfig
>>
>> kala855 wrote:
>>>
>>>
>>> 2007/7/3, Benny Chen <bennyc@xxxxxxxxxxxxxx
>>> <mailto:bennyc@xxxxxxxxxxxxxx>>:
>>>
>>> Hi John O,
>>> Your problem may be with your U-Boot image. It must be linked to
> a
>>> different address to your hardware address maps.
>>>
>>> Do a mb-objdump -t on your u-boot.elf image and you should see
>>> where the
>>> code is linked.
>>>
>>> The root of your problem may be that you are trying to build an
>>> image
>>> for your platform using the Spartan3E reference design without
>>> doing a
>>> petalinux-copy-autoconfig to propagate your hardware
>>> configurations to
>>> the build framework .
>>>
>>> Your best bet is to to just add your platform to PetaLinux and
>>> all this
>>> problem will go away.
>>>
>>> B.
>>>
>>> kala855 wrote:
>>> > HI, I am John Osorio, and I have trouble for port uClinux on
>>> > microblaze, I work with a Spartan 3E revision D, but when I
>>> launch the
>>> > first bootloader FS-Boot I don't have any problem, however when
> I
>>> > download U-Boot, this don't boot,
>>> >
>>> >
>>> > When I type cat /tftpboot/u-boot.srec > /dev/ttyS0 the
> following
>>> > appear in the kermit terminal, I don't know what happen, How
>>> much time
>>> > I wait?
>>> >
>>> > ==============================
>>> > ===================
>>> > FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
>>> > =================================================
>>> > FS-BOOT: System initialisation completed.
>>> > FS-BOOT: No existing image in FLASH. Starting image download.
>>> > FS-BOOT: Waiting for SREC image....
>>> > FS-BOOT: Image download successful.
>>> > FS-BOOT: Warning image location differ from default boot
> location.
>>> > Image will not boot automatically after POR.
>>> > FS-BOOT: Press 'n' to boot old image.
>>> > FS-BOOT: Use new image.
>>> > FS-BOOT: Booting image...
>>> >
>>> > And I wait for ten minutes and nothing happen, please help
>>> > Please, help, I am following the tutorial in the petalinux page
>
>>> for
>>> > custom boards, because the RevC and RevD aren't equals, please
>>> excuse
>>> > me for send this e-mail directly at you, but I need uClinux in
> a
>>> > target, is for my graduation, I study Systems Engineering in
>>> Colombia,
>>> > please help.
>>> >
>>> >
>>> > The project is about the flight automation of an aero model
>>> > helicopter, all using Embedded System with FPGAs. This project
>
>>> will
>>> > have a lot of technology that includes CMOS sensors,
>>> > WiMax, Differential GPS and Laser Sensors. I need your help,
>>> please.
>>> >
>>> >
>>> >
>>> > PD. Excuse my English.
>>> >
>>> >
>>> > Regards,
>>> >
>>> > --
>>> > John Osorio
>>> ___________________________
>>> microblaze-uclinux mailing list
>>> microblaze-uclinux@xxxxxxxxxxxxxx
>>> <mailto:microblaze-uclinux@xxxxxxxxxxxxxx>
>>> Project Home Page :
>>> http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>>> <http://www.itee.uq.edu.au/%7Ejwilliams/mblaze-uclinux>
>>> Mailing List Archive :
>>> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>>> <http://www.itee.uq.edu.au/%7Elistarch/microblaze-uclinux/>
>>>
>>>
>>> Hi, but I have done this, and the error it's the same, thanks for
>>> your help.
>>>
>>> --
>>> John Osorio
>> ___________________________
>> microblaze-uclinux mailing list
>> microblaze-uclinux@xxxxxxxxxxxxxx
>> Project Home Page :
>> http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>> Mailing List Archive :
>> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>>
>>
>
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@xxxxxxxxxxxxxx
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>
>
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@xxxxxxxxxxxxxx
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/