• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2
1  Hardware and U-Boot firmware / U-Boot stuff / Re: after new kernel system hungs after "done, booting the kernel." on: September 21, 2009, 05:14:09 PM
Hy folks...

This is still my problem with new compiled kernel 2.6.31
Code:

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Jul 19 2009 - 16:03:28) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
SDHC found. Card desciption is:
Manufacturer:       0x02, OEM "TM"
Product name:       "SD04G", revision 3.8
Serial number:      3056159759
Manufacturing date: 12/2008
CRC:                0x00, b0 = 0

3488752 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.31-rc9
   Created:      2009-09-21  23:54:27 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3488688 Bytes =  3.3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Any ideas Huh

My "printenv":
Code:
Marvell>> printenv
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootargs_root=root=/dev/mmcblk0p2 rootdelay=10
ethaddr=00:50:43:01:d6:e6
real_bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000
bootargs_console=console=ttyS0,115200
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=mmc; bootm 0x00800000 0x01100000
recover3=usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd
arcNumber=2097
filesize=32D62A
bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=a0000
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no

Environment size: 1800/131068 bytes

Best regards

Nephilim
2  Linux Stuff / Kernel / Re: Help using DVB - Hauppauge WinTV NOVA-TD USB2 on: September 21, 2009, 05:09:37 PM
I'm trying to get my Pinnacle Dazzle DVC 100 to work, too.
It's an USB-device.

My topic "vl4-support needed" in the kernel section was deleted...   :-(

Though I try to compile my own version of kernel.

With 2.6.31, I have the same issues like you.

With my first self-compiled kernel, the video-adapter is working !
But I have missed some network options. I couldn't stream the signal to internet via VLC.

My second kernel isn't booting... :-(

Now I am searching for the bug...

If the issue is resolved, I could send you my "uImage" with drivers for our video-adapters...

No problem.

Please look at

http://plugcomputer.org/plugforum/index.php?topic=693.0

for progress.

Best regards
Nephilim
3  Linux Stuff / Kernel / Re: Installing headers / Kernel clarifications on: September 21, 2009, 06:03:20 AM
@ Manic:

Same problem for me... Now, we are 2...  ;-)
4  Linux Stuff / Kernel / Re: Cross compiling 2.6.31 - ERROR on: September 18, 2009, 04:08:20 AM
The solution:

The newest version of cross compiler is buggy. Use the next oldest version instead (2008-q3)
5  Linux Stuff / Kernel / Cross compiling 2.6.31 - ERROR [SOLVED] on: September 17, 2009, 06:29:55 PM
Want to cross compile my kernel with v4l and em28xx support.

http://plugcomputer.org/plugwiki/index.php/Compiling_Linux_Kernel_for_the_Plug_Computer#Crosscompiling_the_kernel

After
Code:
make -j2 ARCH=arm CROSS_COMPILE=~/Projekte/SheevaPlug/kernel-build/arm-2009q1/bin/arm-none-eabi- uImage

the code runs a few minutes till the following message occurs:

Code:
  LD      net/built-in.o
  LD      vmlinux.o
  MODPOST vmlinux.o
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
  KSYM    .tmp_kallsyms1.S
  AS      .tmp_kallsyms1.o
  LD      .tmp_vmlinux2
  KSYM    .tmp_kallsyms2.S
  AS      .tmp_kallsyms2.o
  LD      vmlinux
  SYSMAP  System.map
  SYSMAP  .tmp_System.map
  OBJCOPY arch/arm/boot/Image
  Kernel: arch/arm/boot/Image is ready
  AS      arch/arm/boot/compressed/head.o
  GZIP    arch/arm/boot/compressed/piggy.gz
  CC      arch/arm/boot/compressed/misc.o
  AS      arch/arm/boot/compressed/piggy.o
  LD      arch/arm/boot/compressed/vmlinux
Segmentation fault
make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 139
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [uImage] ERROR 2

Any ideas, what went wrong ?

Best regards.

EDIT:

http://www.unixguide.net/linux/faq/09.06.shtml        Huh?

6  Linux Stuff / Kernel / Re: 2.6.31 new release on: September 17, 2009, 11:09:06 AM
2.6.31 works...  but...
Code:
root@ubuntu:~# lsmod
Module                  Size  Used by
ipv6                  271508  10
dm_crypt               14460  0
dm_mod                 70700  1 dm_crypt

... the number of loaded modules is very low.

You'll get the same result?
7  General Category / Application ideas and development Q/A / Re: VLC Media Player Server on: September 17, 2009, 04:47:17 AM
Hi !

I would like to use my "plug" as streaming media server.
First tests with vlc (X11 forwarding over ssh) and local video files where successful.

Now I want to use my "Pinnacle Dazzle DVC 100" USB device, which needs em28xx support in kernel, for streaming analog video
into network (for example: analog signal from Camcorder or DVB-T device)

Please look at
http://plugcomputer.org/plugforum/index.php?topic=730.0

Any idea, how to solve this issue ?

Best regards
Nephilim
8  Linux Stuff / Kernel / Re: 2.6.31 new release on: September 17, 2009, 04:42:34 AM
Great work !

Short question:  Is it possible to add support for em28xx (video4linux) in kernel ?

Please look at
http://plugcomputer.org/plugforum/index.php?topic=730.0

Best regards
Nephilim
9  Hardware and U-Boot firmware / U-Boot stuff / Re: How to figure out correct mmc device ?? on: September 14, 2009, 11:11:58 AM
My MMC shows

"** Bad partition - mmc 0:1 **"

after an

"ext2ls mmc 0:1 /"
10  Linux Stuff / Kernel / Re: Need kernel headers for 2.6.30.2 on: September 14, 2009, 11:09:32 AM
Thats, what I have done at least... ;-)

Thanx and close.
11  Hardware and U-Boot firmware / U-Boot stuff / Re: How to figure out correct mmc device ?? on: September 13, 2009, 01:32:42 PM
Hi DamonHD...

To be precisely:

copy /sheeva-2.6.30.6-uImage from partition "sheevaplug-rootf" on MMC
to
/uImage on partition "sheevaplug-uImag" on MMC

This solved all my problems so far.
No modifying for "bootcmd" was necessary...

Best regards and good luck!
Bjoern
12  Hardware and U-Boot firmware / U-Boot stuff / Re: How to figure out correct mmc device ?? on: September 12, 2009, 11:30:09 PM
SOLVED:

- Put mmc into desktop computer
- Copy new 2.6.30.6 uImage to mmc-partition with ROOTFS

Ready...

13  Hardware and U-Boot firmware / U-Boot stuff / How to figure out correct mmc device ?? on: September 12, 2009, 10:42:41 PM
Hi folks...

As described in
http://plugcomputer.org/plugforum/index.php?topic=711.msg4437#msg4437
my SheevaPlug doesn't recognize my mmc after updating to 2.6.30.6 kernel.

The standard bootcmd shows "mmc 0:1"
Quote
Marvell>> printenv bootcmd
bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000
I think, 0:1 could be "disk 1, partition 2" Huh
(like GRUB ??)

After changin the kernel-path only and hitting ENTER...
Quote
Marvell>> setenv bootcmd setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /sheeva-2.6.30.6-uImage; bootm 0x00800000
leaving mmc device with the same options, I get following error...

Quote
SDHC found. Card desciption is:
Manufacturer:       0x02, OEM "TM"
Product name:       "SD04G", revision 3.8
Serial number:      3056159759
Manufacturing date: 12/2008
CRC:                0x00, b0 = 0

** Unable to read "/sheeva-2.6.30.6-uImage" from mmc 0:1 **
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>


How I could search for mmc device, like "fdisk" Huh

mmcinit shows
Quote
SDHC found. Card desciption is:
Manufacturer:       0x02, OEM "TM"
Product name:       "SD04G", revision 3.8
Serial number:      3056159759
Manufacturing date: 12/2008
CRC:                0x00, b0 = 0

Best regards
Bjoern
14  Linux Stuff / Kernel / Re: 2.6.30.6 new release on: September 12, 2009, 10:21:54 PM
Ehhhm...  could we talk about functionallity a little bit later, when booting 2.6.30.6 was successfull ?
;-)

@ DamonHD:
Do you want to boot from NAND or from MMC ?
I am wondering about your error message while running README...

@ cbxbiker61:
Is there a HowTo, which explains, WHERE "uImage" is located ?
My /boot is empty... The updated README only generates the file /sheeva-2.6.30.6-uImage

Please look at http://plugcomputer.org/plugforum/index.php?topic=711.msg4437#msg4437

Best regards.
Bjoern

EDIT:

SOLVED BY MYSELF:
http://plugcomputer.org/plugforum/index.php?topic=724.0
15  Linux Stuff / Kernel / Re: 2.6.30.6 new release on: September 12, 2009, 05:13:41 AM
Many thanks for the new "--rootkernel"-feature !

But there is still a little problem existing:

Code:
USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

First, I want to know the settings from "bootcmd"....
Code:
Marvell>> printenv bootcmd
bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000


Then, I try to change settings to the new uImage...
(sheeva-2.6.30.6-uImage exists in /  )
Code:
Marvell>> setenv bootcmd setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /sheeva-2.6.30.6-uImage; bootm 0x00800000

After hitting ENTER, error message appears...
Code:
SDHC found. Card desciption is:
Manufacturer:       0x02, OEM "TM"
Product name:       "SD04G", revision 3.8
Serial number:      3056159759
Manufacturing date: 12/2008
CRC:                0x00, b0 = 0

** Unable to read "/sheeva-2.6.30.6-uImage" from mmc 0:1 **
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>

Probably I am just a step away from solution...   ;-)

Best regards
Bjoern

PS:

Quote from: cbxbiker61
You'll still need to update your bootcmd or create a symlink to /uImage.

There's no /uImage by default...
Doing a "find / -name *uImage*" shows nothing but sheeva-2.6.30.6-uImage   :-(

"ln -s /sheeva-2.6.30.6-uImage /uImage" does nothing better... still booting 2.6.30.2

"mmcinit" shows:
Code:
SDHC found. Card desciption is:
Manufacturer:       0x02, OEM "TM"
Product name:       "SD04G", revision 3.8
Serial number:      3056159759
Manufacturing date: 12/2008
CRC:                0x00, b0 = 0

Probably it should be mmc 0:0, and not mmc 0:1  Huh
Pages: [1] 2