[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] system booting problem

To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] system booting problem
From: Faiza Ait-Kaci <faiza.ak@xxxxxxxxxx>
Date: Wed, 22 Jul 2009 11:46:42 +0200 (CEST)
In-reply-to: <16326102.101248248216606.JavaMail.AWS04$@AWS04>
Reply-to: microblaze-uclinux@xxxxxxxxxxxxxx
Sender: owner-microblaze-uclinux@xxxxxxxxxxxxxxxxxxxx
Hi,

Trying with tftp, I first launched the srec image download then launched the platform initialisation with tftp. it faild. here is the error log:

----------------------------------------------------------------------------------------
=================================================
FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
Project name: DCE_Test
Build date: Jul 20 2009 09:58:46  FS
Serial console: Uartlite
=================================================
FS-BOOT: System initialisation completed.
FS-BOOT: Booting from FLASH. Press 's' for 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...
SDRAM :
	Enabling caches :
		Icache:OK
		Dcache:OK
	U-Boot Start:0x87fc0000
	Malloc Start:0x87f80000
	Board Info Start:0x87f7ffd0
	Boot Parameters Start:0x87f6ffd0
FLASH: 16 MB
ETHERNET: MAC:00:0a:35:00:22:01

*** Warning - bad CRC, using default environment

Hit any key to stop autoboot:  0 
U-Boot> run update_uboot
TFTP from server 192.168.0.1; our IP address is 192.168.0.10
Filename 'u-boot-s.bin'.
Load address: 0x86000000
Loading: bad length 4 < 28
bad length 4 < 28
bad length 4 < 28
T T T T T T T T T T 
Retry count exceeded; starting again
TFTP from server 192.168.0.1; our IP address is 192.168.0.10
Filename 'u-boot-s.bin'.
Load address: 0x86000000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
TFTP from server 192.168.0.1; our IP address is 192.168.0.10
Filename 'u-boot-s.bin'.
Load address: 0x86000000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
TFTP from server 192.168.0.1; our IP address is 192.168.0.10
Filename 'u-boot-s.bin'.
Load address: 0x86000000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
TFTP from server 192.168.0.1; our IP address is 192.168.0.10
Filename 'u-boot-s.bin'.
Load address: 0x86000000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
TFTP from server 192.168.0.1; our IP address is 192.168.0.10
Filename 'u-boot-s.bin'.
Load address: 0x86000000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
TFTP from server 192.168.0.1; our IP address is 192.168.0.10
Filename 'u-boot-s.bin'.
Load address: 0x86000000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
-----------------------------------------------------------------------------

Regards,

Faiza


----- Mail Original -----
De: "Faiza Ait-Kaci" <faiza.ak@xxxxxxxxxx>
À: microblaze-uclinux@xxxxxxxxxxxxxx
Envoyé: Mercredi 22 Juillet 2009 09h37:15 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: [microblaze-uclinux] system booting problem

Hi,

thanks for answering.

well, I did not make any changes in the distribution. the only difference is the edk project. I took the same bsb file as the reference design one except that I do not take the DTE_RS232 port but select the DCE_RS232 uartlite instead. all remaining is identical to reference design.

I will try to use tftp or telnet to see if it is well working via network and tell you back what was the result.
Thanks again for helping me.

Regards,

Faiza.

----- Mail Original -----
De: "Michal Simek" <michal.simek@xxxxxxxxxxxxx>
À: microblaze-uclinux@xxxxxxxxxxxxxx
Envoyé: Mercredi 22 Juillet 2009 08h03:14 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: [microblaze-uclinux] system booting problem

Hi,

Faiza Ait-Kaci wrote:
> Hi,
> 
> isn'it possible to solve the problem just by using serial downloads?

I just want to know if your system work or not - just check/debug your setting through network

> 
> (I don't want to use network solutions because I want to port the petalinux dist. on a board not having Ethernet port. so I running all steps on the Spatan3E500 kit to validate the booting without using Ethernet (or telnet) so that afterward when coming to the other board, I know all steps.)

Of course you can use Linux without any Ethernet port.

I am still not sure why you have this problem. The easier way is used reference design which is in
PetaLinux and compile Linux for it. It is prepared and tested. You shouldn't have any problem
to run it on s3e500 board.
I saw it this behavior but not for clean PetaLinux build.
Have you done any code changes?

Regards,
Michal


> 
> Regards,
> 
> Faiza
> 
> 
> ----- Mail Original -----
> De: "Michal Simek" <michal.simek@xxxxxxxxxxxxx>
> À: microblaze-uclinux@xxxxxxxxxxxxxx
> Envoyé: Mardi 21 Juillet 2009 16h05:49 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
> Objet: Re: [microblaze-uclinux] system booting problem
> 
> 
> 
> Faiza Ait-Kaci wrote:
>> Hi,
>>
>> chekking in /petalinux-dist/romfs/etc/inittab I get:
>>
>> ttyUL0:vt100:/bin/agetty 115200 ttyUL0
>> flt:unknown:/bin/flatfsd
>> inet:unknown:/bin/inetd /etc/inetd.conf
>>
>> Should I modify this file?
> 
> it is ok. You have there eth - can you try to telnet to board?
> 
> Regards,
> Michal
> 
>> ----- Mail Original -----
>> De: "Michal Simek" <michal.simek@xxxxxxxxxxxxx>
>> À: microblaze-uclinux@xxxxxxxxxxxxxx
>> Envoyé: Mardi 21 Juillet 2009 14h00:42 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
>> Objet: Re: [microblaze-uclinux] system booting problem
>>
>> Hi,
>>
>> check your /etc/inittab
>> There should be something like
>>
>> ttyUL0:vt100:respawn:/sbin/getty 115200 ttyUL0
>>
>> Regards,
>> Michal
>>
>>
>> Faiza Ait-Kaci wrote:
>>> Hi,
>>>
>>> I am trying to boot the petalinux-dist on a Spartan3E-RevC starter kit. not being able to use the DTE port ,I created my own EDK project with same features except that I use the DCE port.
>>>
>>> For u-boot, since I am not using tftp but serial connection for downloads, I downloaded to the Flash with the u-boot "loadb" command the following files:
>>>
>>> u-boot-s.bin at address 0x85000000 (sector 0 of Flash)
>>>
>>> ub.config.img           0x85020000 (sector 1)
>>>
>>> image.ub                0x85080000 (sector 5)
>>>
>>> (I choosed these adresses by lookin to the result of the "printenv")
>>>
>>> after the downloads, I reset the board.
>>> the booting of the system started but stopped before the uclinux login prompt. Can anyone help me find what step went wrong?
>>>
>>> Here is the log:
>>> ----------------------------------------------------------------------------- 
>>>
>>> =================================================
>>> FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
>>> Project name: DCE_Test
>>> Build date: Jul 20 2009 09:58:46  FS
>>> Serial console: Uartlite
>>> =================================================
>>> FS-BOOT: System initialisation completed.
>>> FS-BOOT: Booting from FLASH. Press 's' for image download.
>>> FS-BOOT: Booting image...
>>> SDRAM :
>>> 	Enabling caches :
>>> 		Icache:OK
>>> 		Dcache:OK
>>> 	U-Boot Start:0x87fc0000
>>> 	Malloc Start:0x87f80000
>>> 	Board Info Start:0x87f7ffd0
>>> 	Boot Parameters Start:0x87f6ffd0
>>> FLASH: 16 MB
>>> ETHERNET: MAC:00:0a:35:00:22:01
>>>
>>> *** Warning - bad CRC, using default environment
>>>
>>> Hit any key to stop autoboot:  0 
>>> ## Booting image at 85080000 ...
>>>    Image Name:   PetaLinux Kernel 2.6
>>>    Image Type:   Microblaze Linux Kernel Image (uncompressed)
>>>    Data Size:    2760848 Bytes =  2.6 MB
>>>    Load Address: 86000000
>>>    Entry Point:  86000000
>>>    Verifying Checksum ... OK
>>> OK
>>> Found romfs @ 0x861b308c (0x000ef000)
>>> #### klimit 861cb000 ####
>>> Moving 0x000ef000 bytes from 0x861b308c to 0x861ca880
>>> New klimit: 0x862ba000
>>> Linux version 2.6.20-uc0 (faiza@desktop) (gcc version 3.4.1 ( PetaLinux 0.20 Build -rc1 050607 )) #4 Mon Jul 20 10:13:57 CEST 2009
>>> setup_cpuinfo: initialising
>>> setup_cpuinfo: No PVR support in CPU.  Using static compile-time info
>>> set_cpuinfo_static: Using static CPU info.
>>> setup_memory: max_mapnr: 0x87fff
>>> setup_memory: min_low_pfn: 0x86000
>>> setup_memory: max_low_pfn: 0x2000
>>> On node 0 totalpages: 8192
>>>   DMA zone: 64 pages used for memmap
>>>   DMA zone: 0 pages reserved
>>>   DMA zone: 8128 pages, LIFO batch:0
>>>   Normal zone: 0 pages used for memmap
>>> Built 1 zonelists.  Total pages: 8128
>>> Kernel command line: mtdparts=physmap-flash.0:256K(boot),128K(bootenv),128K(config),4M(image),11M(spare) macaddr=00:0a:35:00:22:01 console=ttyUL0,115200
>>> OPB INTC #0 at 0x81800000
>>> PID hash table entries: 128 (order: 7, 512 bytes)
>>> TIMER at 0x83C00000
>>> disabling early console
>>> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
>>> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
>>> Memory: 29688k/32768k available
>>> Calibrating delay loop... 49.45 BogoMIPS (lpj=247296)
>>> Mount-cache hash table entries: 512
>>> NET: Registered protocol family 16
>>> NET: Registered protocol family 2
>>> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
>>> TCP established hash table entries: 1024 (order: 0, 4096 bytes)
>>> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
>>> TCP: Hash tables configured (established 1024 bind 1024)
>>> TCP reno registered
>>> io scheduler noop registered
>>> io scheduler anticipatory registered
>>> io scheduler deadline registered
>>> io scheduler cfq registered (default)
>>> xgpio0 #0 at 0x81420000 mapped to 0x81420000 device: 10,185 using IRQ#3
>>> xgpio1 #1 at 0x81400000 mapped to 0x81400000 device: 10,186 using IRQ#2
>>> uartlite.0: ttyUL0 at MMIO 0x84000000 (irq = 4) is a uartlite
>>> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
>>> eth0: using fifo mode.
>>> eth0: No PHY detected.  Assuming a PHY at address 0.
>>> eth0: Xilinx EMACLite #0 at 0x81000000 mapped to 0x81000000, irq=1
>>> physmap platform flash device: 01000000 at 85000000
>>> physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
>>>  Intel/Sharp Extended Query Table at 0x0031
>>> Using buffer write method
>>> cfi_cmdset_0001: Erase suspend on write enabled
>>> erase region 0: offset=0x0,size=0x20000,blocks=128
>>> 5 cmdlinepart partitions found on MTD device physmap-flash.0
>>> Creating 5 MTD partitions on "physmap-flash.0":
>>> 0x00000000-0x00040000 : "boot"
>>> 0x00040000-0x00060000 : "bootenv"
>>> 0x00060000-0x00080000 : "config"
>>> 0x00080000-0x00480000 : "image"
>>> 0x00480000-0x00f80000 : "spare"
>>> uclinux[mtd]: RAM probe address=0x861ca880 size=0xef000
>>> Creating 1 MTD partitions on "RAM":
>>> 0x00000000-0x000ef000 : "ROMfs"
>>> uclinux[mtd]: set ROMfs to be root filesystem index=5
>>> TCP cubic registered
>>> NET: Registered protocol family 1
>>> NET: Registered protocol family 17
>>> VFS: Mounted root (cramfs filesystem) readonly.
>>> Freeing unused kernel memory: 84k freed
>>> -------------------------------------------------------------------
>>>
>>> ___________________________
>>> 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/
>>>
>>>
> 

-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
___________________________
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/
Follow-Ups:
- Re: [microblaze-uclinux] system booting problem
  - From: Faiza Ait-Kaci
References:
- Re: [microblaze-uclinux] system booting problem
  - From: Faiza Ait-Kaci
Prev by Date: Re: [microblaze-uclinux] petalinux-jtag-boot
Next by Date: Re: [microblaze-uclinux] problem with "petalinux-copy-autoconfig" command...
Previous by thread: Re: [microblaze-uclinux] system booting problem
Next by thread: Re: [microblaze-uclinux] system booting problem
Index(es):
- Date
- Thread