2009-09-01 05:49:52     Boot problem

Document created by Aaronwu Employee on Aug 19, 2013
Version 1Show Document
  • View in full screen mode

2009-09-01 05:49:52     Boot problem

Emanuele Italia (ITALY)

Message: 79424   

 

Hello,

 

i have just compiled withotu problem the 2009 uClinux version for blackfin with the right toolchain.

 

When i try to boot up the uImage it doesn't work and i don't have any interesting errors. I just see some strange characters.

 

It looks like i choose bad baud rate but it not like this because i tried to switch the baud rate when the image was loading by tftp from u-boot but without result.

 

 

 

this is what happen when i try to boot the new uimage:

 

CPU:   ADSP BF532 Rev.: 0.5

 

Board: IP04 IP-PBX

 

         www.rowetel.com/ucasterisk/ip04.html

 

Clock: VCO: 400 MHz, Core: 400 MHz, System: 133 MHz

 

SDRAM: 64 MB

 

In:    serial

 

Out:   serial

 

Err:   serial

 

256 MiB

 

DM9000#0

 

starting from spi flash

 

Hit any key to stop autoboot:  0

 

ip04>

 

ip04>

 

ip04>

 

ip04>

 

ip04>tftp 0x1000000 uImage_2009

 

dm9000 i/o: 0x20100000, id: 0x90000a46

 

MAC: 00:09:45:56:50:b0

 

operating at 100M full duplex mode

 

Using DM9000#0 device

 

TFTP from server 10.0.0.200; our IP address is 10.0.0.100

 

Filename 'uImage_2009'.

 

Load address: 0x1000000

 

Loading: checksum bad

 

checksum bad

 

T #################################################################

 

         #################################################################

 

         #################################################################

 

         #################################################################

 

         #################################################################

 

         ###############checksum bad

 

##################################################

 

         #################################################################

 

         #################################################################

 

         #################################################################

 

         #################################################################

 

         #################################################################

 

         #################################################################

 

         ###########################################################

 

done

 

Bytes transferred = 4293200 (418250 hex)

 

Automatic boot of image at addr 0x01000000 ...

 

## Booting image at 01000000 ...

 

   Image Name:   Linux-2.6.28.10-ADI-2009R1

 

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

 

   Data Size:    4293136 Bytes =  4.1 MB

 

   Load Address: 00001000

 

   Entry Point:  0017f6d4

 

   Verifying Checksum ... OK

 

   Uncompressing Kernel Image ... OK

 

Starting Kernel at = 17f6d4

 

Y^ex@fEbcY_^@b^f^bx^a`]]b``y"a@Xb__dDEBYA^Y@XGCC@fEbcY_^@d^a^b@X@cf^YY@Cax@_^@eG@ca@aezaazcy@##$@b``yB__dC_^c_\E@;EAb\y?cXAD_g`=@E^AB\ED'Ab^Y^Gz@\Y]YdY^G@]E]_by

 

@d_@ef@DeE@d_@XAbDgAbE@A^_]A\y@`e```bfc_AbD@E]_byz@fd

 

b^E\@A^AGED@E]_byz@fdE]_by@]A`z@@FYxEDC_DE@}@`x`````d``]`x`````dy`@@dExd@@@@@@}@`x````a```]`x``a`dEx`@@b_DAdA@@@@}@`x``a`dEx`]`x``aecAF`@@Bcc@@@@@@@}@`x``aed```

 

]`x``afddex@@DAdA@@@@@@}@`x``afddex]`x``agd```@@@@cdAC[@@@}@`x``agb```]`x``agd```@@Y^Yd@@@@@@}@`x``agd```]`x``gFe```@@AfAY\AB\E@}@`x``gFe```]`x`cgFF```@@@:_^E@@

 

}@`x`cF`````]`x`d``````AbDgAbE@$bACE@CdYfE@A^D@^AB\ED__d@_DEz@f\AC[FY^@ce``_bd@XY@b``d]b``y@^A\_G@EfYCEc\@^C^_]`Y\ED@F_b@# ]ecc@"Ef@`^c'Ab^Y^Gz@_]`Y\ED@F_b@"Ef@

 

c\@Bed@be^^Y^G@_^@"Ef@e\AC[FY^@Y^ex@ce``_bd@By@Xdd`z__B\AC[FY^^eC\Y^ex^_bG_ b_CEcc_b@#`EEDz@ddb@z@C_bE@C\_C[@A^D@adg@z@#ycdE]@\_C[ %z@cEddY^G@e`@C`\B@dAB\Ec^cdb

 

eCdY_^@ACXE@^AB\ED@F_b@ %`AdA@ACXE@^AB\ED@F_b@ %`@XgbYdE]BAC[YeY\d

 

 

 

Thank you in advance,

 

 

 

Emanuele

 

Immagine 1.png

TranslateQuoteReplyEditDelete

 

 

2009-09-01 07:01:45     Boot problem

Michael Hennerich (GERMANY)

Message: 79431    From your u-boot prompt can you type print

 

ip04>print

 

and then post the output?

 

I suspect there is something wrong with your bootargs...

Typical bootargs include something like this:

 

root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600

console=ttyBF0,57600

 

-Michael

QuoteReplyEditDelete

 

 

2009-09-01 07:59:58     Re: Boot problem

Emanuele Italia (ITALY)

Message: 79432   

 

My bootargs are:

 

bootargs=ethaddr=00:09:45:56:50:B0 console=ttyBF0,115200 root=/dev/mtdblock2 rw

 

it's strange becuase i don't see some "normal errors" like kernel panic, etc.

 

 

 

Emanuele

TranslateQuoteReplyEditDelete

 

 

2009-09-01 08:08:38     Re: Boot problem

Michael Hennerich (GERMANY)

Message: 79433    I assume you set CONFIG_CLKIN_HZ to the right frequency/value for your

board?

QuoteReplyEditDelete

 

 

2009-09-01 08:19:58     Re: Boot problem

Emanuele Italia (ITALY)

Message: 79434   

 

I assume you set CONFIG_CLKIN_HZ to the right frequency/value for your

board? ---

 

is it kernel parameter? how can i know the right value?

 

thank you

 

Emanuele

TranslateQuoteReplyEditDelete

 

 

2009-09-01 08:31:27     Re: Boot problem

Michael Hennerich (GERMANY)

Message: 79435    It's the frequency of your Blackfin CLKIN (crystal)

Looks like it is 10MHz for the IP04

 

So you should set CONFIG_CLKIN_HZ to 10000000 during kernel/board

configuration.

Alternatively you can pass it via bootargs clkin_hz=10000000

 

-Michael

QuoteReplyEditDelete

 

 

2009-09-01 08:53:59     Re: Boot problem

Emanuele Italia (ITALY)

Message: 79437   

 

thank you! now it boots correctly! but it doesn't find mtdblock...even in /dev/ doesn't exist none mtd device files.

 

Emanuele

TranslateQuoteReplyEditDelete

 

 

2009-09-01 09:40:08     Re: Boot problem

Mike Frysinger (UNITED STATES)

Message: 79440   

 

so make sure you enable the right drivers in your kernel for your desired root source

QuoteReplyEditDelete

 

 

2009-09-02 08:09:13     Re: Boot problem

Emanuele Italia (ITALY)

Message: 79489   

 

so make sure you enable the right drivers in your kernel for your desired root source

 

---

 

I compiled the kernel several times..but it doesn't find my NAND memory...

 

i follow these instructions:

 

  docs.blackfin.uclinux.org/doku.php?id=linux-kernel:drivers:bfin_async_nand

 

but after boot.. i don't find any mtd blocks

 

root:/> ls /dev/

 

console             ptmx                ram2                sport0

 

cpu_dma_latency     pts                 ram3                sport1

 

fd                  ram0                ram4                stderr

 

full                ram1                ram5                stdin

 

kmsg                ram10               ram6                stdout

 

log                 ram11               ram7                tty

 

mem                 ram12               ram8                ttyBF0

 

network_latency     ram13               ram9                urandom

 

network_throughput  ram14               random              watchdog

 

null                ram15               rtc0                zero

 

 

 

Emanuele

TranslateQuoteReplyEditDelete

 

 

2009-09-02 08:32:38     Re: Boot problem

Mike Frysinger (UNITED STATES)

Message: 79494   

 

please review the documentation:

  docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:dev-management#troubleshooting

QuoteReplyEditDelete

 

 

2009-09-03 04:46:59     Re: Boot problem

Emanuele Italia (ITALY)

Message: 79516   

 

please review the documentation:

  docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:dev-management#troubleshooting

 

---

 

i read the documentation and then my major number are:

 

root:/> cat /proc/devices

 

Character devices:

 

  1 mem

 

  5 /dev/tty

 

  5 /dev/console

 

  5 /dev/ptmx

 

10 misc

 

90 mtd

 

128 ptm

 

136 pts

 

204 ttyBF

 

237 sport

 

254 rtc

 

 

 

Block devices:

 

  1 ramdisk

 

259 blkext

 

31 mtdblock

 

 

 

 

 

root:/> cat /proc/misc

 

61 network_throughput

 

62 network_latency

 

63 cpu_dma_latency

 

130 watchdog

 

 

 

Following the documentation:

 

    the device drivers are actually available -- either compiled in or loaded as a module

    i think so

    the device driver detects the device -- for platform device drivers, proper platform resources must be declared in the board resources file

    I don't know, how can i check it?

    the device driver correctly registers itself via the class/kobject/whatever subsystem -- this will automatically trigger and generate the required hotplug messages

    In my case it's not a module.. i think it's ok here

    there is a userspace application processing the hotplug messages from the kernel -- if you aren't using the default settings with the mdev program from busybox, you will need to make sure things are properly configured in your system

    I'm using default setting

 

Emanuele

TranslateQuoteReplyEditDelete

 

 

2009-09-03 08:48:36     Re: Boot problem

Emanuele Italia (ITALY)

Message: 79560   

 

i try to compile the nand driver like modules and load them by hand...

 

 

 

root:/> modprobe nand

 

root:/> lsmod

 

Module                  Size  Used by

 

nand                   23764  0

 

nand_ids                2644  1 nand

 

nand_ecc                2616  1 nand

 

root:/> ls /dev/

 

console             ptmx                ram2                stderr

 

cpu_dma_latency     pts                 ram3                stdin

 

fd                  ram0                ram4                stdout

 

full                ram1                ram5                tty

 

kmsg                ram10               ram6                ttyBF0

 

log                 ram11               ram7                urandom

 

mem                 ram12               ram8                watchdog

 

network_latency     ram13               ram9                zero

 

network_throughput  ram14               random

 

null                ram15               rtc0

 

 

 

it seems that driver don't find my nand chip, it's very strange on 2007 it works perfectly.

 

 

 

Thanks in advance,

 

 

 

Emanuele

TranslateQuoteReplyEditDelete

 

 

2009-09-03 11:05:28     Re: Boot problem

Mike Frysinger (UNITED STATES)

Message: 79568   

 

drivers change and are obsoleted by better ones all the time

 

"nand" is the main nand code, it does not deal with any low level chip in any way

QuoteReplyEditDelete

 

 

2009-09-04 04:01:29     Re: Boot problem

Emanuele Italia (ITALY)

Message: 79603   

 

drivers change and are obsoleted by better ones all the time

 

"nand" is the main nand code, it does not deal with any low level chip in any way

 

---

 

Strange, i think they are quite common chips.

 

They are:

 

Samsung K4S560832H-UC75

 

Anyway now i'm tring on SVN

 

 

 

Emanuele

Attachments

Outcomes