Imx35 getting stuck with "Uncompressing Linux ................."

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Imx35 getting stuck with "Uncompressing Linux ................."

2,102 Views
santhoshsl
Contributor III

Following steps I followed to load the Demo Linux image provided in to IMX35

Booting from MMC:

1.Erase complete MMC

2.$ sudo dd if=./Desktop/mx35_3stack_redboot_mmc.bin of=/dev/sdd bs=512 skip=2 seek=2  -- To copy Redboot image on to MMC

3.Reset

Loading Image:

with Redboot booted up

1. load -r -b 0x100000 -m xmodem

Redboot now is ready to receive data and printing out character “C” continuously. To send a file, click on “Transfer -

> Send File -> Xmodem (under Protocol) -> Browse”, choose the file to download and then click on “Send”

2. fis init -- To initialize flash

3. fis create -f 0x200000 kernel -- Section on flash to copy our Image

4. fis load -d kernel

5. fis list --

   here we can see following sections being created

... Read from 0x07ee0000-0x07eff000 at 0x00060000: .                           

Name              FLASH addr  Mem addr    Length      Entry point              

RedBoot           0x00000000  0x00000000  0x00040000  0x00000000               

FIS directory     0x00060000  0x00060000  0x0001F000  0x00000000               

RedBoot config    0x0007F000  0x0007F000  0x00001000  0x00000000               

kernel            0x00200000  0x00100000  0x00200000  0x00100000 

6. Then when i give Run, it is getting stuck at following error

load entry_address=0x100000                                                    

virt_addr=0x100000                                                             

phys_addr=0x80100000                                                           

Uncompressing Linux.............................................................

Can some one help me on this.


Labels (1)
Tags (1)
0 Kudos
Reply
8 Replies

1,499 Views
fabio_estevam
NXP Employee
NXP Employee

Maybe it would be easier if you use U-boot instead of Redboot.

mx35pdk support is available in the Freescale BSP as well as in the mainline U-boot.

Regards,

Fabio Estevam

1,499 Views
pj0585
Contributor III

If the boot stops at "uncompressing linux..." that may indicate: there was an error in the kernel code. This error occurred before kernel initialized Serial controller.

To check the error:

1) Get the System.map file of the specific kernel image that you have. If you built it yourself, you will find System.map in the top level kernel directory. (For pre-built BSPs they usually include somewhere in the root filesystem, check /boot dir)

2) In System.map search for "__log_buf" (I think thats the one)

3) Note down the memory address (8 digit hex number)

4) Power on the board and boot stops at "uncompressing linux..."

5) Reset the board (reset without power down)

6) Stop at Uboot prompt and use uboot 'md' command to dump the contents of the memory location for '__log_buf'

7) from that you may get some clue of the error.

This is a general debugging technique, not sure if any specific of the board is involved.

Hope this helps.

-Pj

0 Kudos
Reply

1,499 Views
VladanJovanovic
NXP Employee
NXP Employee

Is this on a custom board? Did you modify memory controller setup for the memory you're using (probably different from what is used on i.MX35PDK)? This setup for i.MX35PDK in Redboot is in:

packages/hal/arm/mx35/3stack/current/include/hal_platform_setup.h

1,499 Views
santhoshsl
Contributor III

Hello Vladan,

Thanks for your inputs.

This is not a custom board. And we didnt changed any Memory controller setup. We are just trying to flash demo Linux image provided from Freescale.

Note: But earlier the same board was used with WinCE os and some application was made based on it. Would this have any problem? Please provide your inputs.

Also I will cross check the settings in hal_platform_setup.h

0 Kudos
Reply

1,499 Views
VladanJovanovic
NXP Employee
NXP Employee

There's no problem with using WinCE previously.

Can you try loading image via TFTP instead of via serial port? Errors in transfer are possible when using serial port so that may explain the problems. Also there seems to be only 2MB allocated for kernel partition. Is that enough (zImage < 2MB)?

Also it would help to see full redboot environment variable setup and entire log after you try the Run.

0 Kudos
Reply

1,499 Views
santhoshsl
Contributor III

Also Vladan, I couldnot find the path/file you mentioned

packages/hal/arm/mx35/3stack/current/include/hal_platform_setup.h

I have downloaded L2_6_26_3_4_2_SDK_source and L2.6.31_09.12.01_SDK_images_MX35 from freescale website. And I was unsuccessful in finding hal_platform_setup.h file in these.

0 Kudos
Reply

1,499 Views
VladanJovanovic
NXP Employee
NXP Employee

I think pinging to i.MX35 running Redboot will not work (if I remember correctly). Try pinging from i.MX35/Redboot to server PC instead...

hal_platform_setup.h you will find in the Redboot....zip package in the source archive. You'll need to unzip it, untar sources and apply the patches as described in documentation in the .zip package.

0 Kudos
Reply

1,499 Views
santhoshsl
Contributor III

Hello Valdan,

Thanks for further inputs.

I tried to load image via TFTP but ping to the device itself is not happening. I tried both Static IP and an DHCP configuration. Following were my setup details

IMX35 -- static configuration

Use BOOTP for network configuration: false

Gateway IP address: 192.168.1.121

Local IP address: 192.168.1.80

Local IP address mask: 255.255.255.0

Default server IP address: 192.168.1.121(my PC)

and my PC eth0 is being assigned with 192.168.1.121

For DHCP

Use BOOTP for network configuration: True

Gateway IP address: 192.168.1.1

Local IP address mask: 255.255.255.0

And i connected this to Cisco's linksys router.

Both ways i was not able to ping.

So I again tried with Serial communication to load and got similar issue as earlier,

Please find the log attached.


0 Kudos
Reply