• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2]
16  Linux Stuff / Kernel / Re: anyone compile a custom kernel yet? on: April 15, 2009, 01:58:01 AM
Fedora 10. Maybe I should try it on a debian system, I thought it wouldn't matter since It's a cross-compiler.
17  Linux Stuff / Kernel / Re: anyone compile a custom kernel yet? on: April 14, 2009, 01:06:39 AM
Im now trying to build a kernel following these instructions:  http://plugcomputer.org/plugwiki/index.php/Compiling_Linux_Kernel_for_the_Plug_Computer

The cross-compile is running, but my issue is that I cannot get mkimage to build:

Code:
[root@gnouf u-boot-2009.03]# make tools
for dir in tools examples api_examples ; do make -C $dir _depend ; done
make[1]: Entering directory `/root/tmp/u-boot-2009.03/tools'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory `/root/tmp/u-boot-2009.03/tools'
make[1]: Entering directory `/root/tmp/u-boot-2009.03/examples'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory `/root/tmp/u-boot-2009.03/examples'
make[1]: Entering directory `/root/tmp/u-boot-2009.03/api_examples'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory `/root/tmp/u-boot-2009.03/api_examples'
make -C tools all
make[1]: Entering directory `/root/tmp/u-boot-2009.03/tools'
gcc -g  -idirafter /root/tmp/u-boot-2009.03/include -idirafter /root/tmp/u-boot-2009.03/include2 -idirafter /root/tmp/u-boot-2009.03/include -DTEXT_BASE= -DUSE_HOSTCC -c -o env_embedded.o env_embedded.c
In file included from env_embedded.c:30:
/root/tmp/u-boot-2009.03/include/environment.h:107: error: 'CONFIG_ENV_SIZE' undeclared here (not in a function)
make[1]: *** [env_embedded.o] Error 1
make[1]: Leaving directory `/root/tmp/u-boot-2009.03/tools'
make: *** [tools] Error 2

Can anyone suggest what could be wrong, or post a mkimage binary? Smiley

*EDIT*

Well the cross-compile "finished" and looks like it is hosed too Sad
Code:
  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
  AS      arch/arm/boot/compressed/piggy.o
  CC      arch/arm/boot/compressed/misc.o
  LD      arch/arm/boot/compressed/vmlinux
/root/tmp/arm-2008q3/bin/arm-none-eabi-ld: ERROR: arch/arm/boot/compressed/misc.o uses VFP instructions, whereas arch/arm/boot/compressed/vmlinux does not
/root/tmp/arm-2008q3/bin/arm-none-eabi-ld: failed to merge target specific data of file arch/arm/boot/compressed/misc.o
make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [uImage] Error 2

I give up for now. Need sleep.
18  Linux Stuff / Kernel / Re: anyone compile a custom kernel yet? on: April 13, 2009, 11:56:26 PM
Maybe it's because I need sleep, but I appear to need some help here.  The docs that tell how to build a kernel mention some files that I cannot find:

linux-feroceon_4_2_7_KW_new.zip
0001_gw_BE_fix.patch

I have looked all over for these 2 files, but cannot find them. I'm sure it's right in front of my face so feel free to point it out and laugh at me :-)

Also is it possible to upgrade kernel via apt-get?  In this case it won't do me any good as I need a kernel that supports the uvcvideo module, but just wondering.
19  Linux Stuff / Kernel / Kernel building - monolithic or modular? on: April 13, 2009, 08:11:09 PM
Which do you suggest? I normally like modular kernel but is there any advantage to monolithic in this case? I need uvcvideo support so that I can plug in a newer USB webcam which needs the uvcvideo and videodev modules.

Before I got distracted dealing with my uImage partition getting hosed, I tried compiling kernel source without much luck, but will try again this weekend.  If someone is already setup to compile kernels and can build me one with uvcvideo support, I would be very appreciative Smiley
20  Linux Stuff / Kernel / Re: Problems reflashing UImage, bad blocks on: April 13, 2009, 08:06:32 PM
Thanks for your advice. I was able to boot NFS with the resized mtd partition (4MB) and reflash it. I am now booting from NAND again :-)

One question:
Code:
root@debian:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "uBoot"
mtd1: 00400000 00020000 "uImage"
mtd2: 1fb00000 00020000 "rootfs"

Is it normal for the "erasesize" to show as 2MB?

I also hate all these bad blocks I have on my flash...does anyone else have bad blocks?
Code:
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 749 at 0x05da0000
Bad eraseblock 767 at 0x05fe0000
Bad eraseblock 827 at 0x06760000
Bad eraseblock 828 at 0x06780000
Bad eraseblock 829 at 0x067a0000
Bad eraseblock 1003 at 0x07d60000
Bad eraseblock 1130 at 0x08d40000
Bad eraseblock 1231 at 0x099e0000
Bad eraseblock 1269 at 0x09ea0000
Bad eraseblock 1462 at 0x0b6c0000
Bad eraseblock 1889 at 0x0ec20000
Bad eraseblock 2773 at 0x15aa0000
Bad eraseblock 3874 at 0x1e440000
Bad eraseblock 3939 at 0x1ec60000
Bad eraseblock 4057 at 0x1fb20000
Bad eraseblock 4061 at 0x1fba0000
Bad eraseblock 4062 at 0x1fbc0000
Bad eraseblock 4063 at 0x1fbe0000
Bad eraseblock 4095 at 0x1ffe0000

 * Loading hardware drivers...                                                  end_request: I/O error, dev mtdblock2, sector 1038208
Buffer I/O error on device mtdblock2, logical block 129776
end_request: I/O error, dev mtdblock2, sector 1038208
Buffer I/O error on device mtdblock2, logical block 129776
end_request: I/O error, dev mtdblock2, sector 1038320
Buffer I/O error on device mtdblock2, logical block 129790
end_request: I/O error, dev mtdblock2, sector 1038320
Buffer I/O error on device mtdblock2, logical block 129790
end_request: I/O error, dev mtdblock2, sector 1038328
Buffer I/O error on device mtdblock2, logical block 129791
end_request: I/O error, dev mtdblock2, sector 1038328
Buffer I/O error on device mtdblock2, logical block 129791
end_request: I/O error, dev mtdblock2, sector 1038328
Buffer I/O error on device mtdblock2, logical block 129791
end_request: I/O error, dev mtdblock2, sector 1038328
Buffer I/O error on device mtdblock2, logical block 129791
end_request: I/O error, dev mtdblock2, sector 1038328
Buffer I/O error on device mtdblock2, logical block 129791
end_request: I/O error, dev mtdblock2, sector 1038328
Buffer I/O error on device mtdblock2, logical block 129791
end_request: I/O error, dev mtdblock2, sector 1038328
end_request: I/O error, dev mtdblock2, sector 1038272
end_request: I/O error, dev mtdblock2, sector 1038320
end_request: I/O error, dev mtdblock2, sector 1038328
end_request: I/O error, dev mtdblock2, sector 1038328
end_request: I/O error, dev mtdblock0, sector 0
end_request: I/O error, dev mtdblock0, sector 8
end_request: I/O error, dev mtdblock0, sector 16
end_request: I/O error, dev mtdblock0, sector 24
end_request: I/O error, dev mtdblock0, sector 0
21  Linux Stuff / Kernel / Problems reflashing UImage, bad blocks on: April 13, 2009, 03:32:12 PM
If anyone is interested, I posted pictures on my blog when I first received my unit: http://www.the-ownage.com/?p=830

I am currently having issues with mine, and GlobalScale has thusfar ignored my support request emails.

My issues started when I noticed that upon bootup, the boot partition was reporting lots of bad blocks, both seen on the console at boot-time and can also see in "dmesg". Now I know that bad blocks on NAND flash are not unheard of, and that in fact over time more and more blocks go bad and they are automatically marked bad, but I think its not right to have 20 bad blocks right out of the box. Seeing all the errors is annoying.

So, I had the dumb idea of using the "nandtest" binary on the partition in hopes that it would somehow clear the bad blocks or remap them elsewhere. Well it turns out it is a destructive test, so my root partition was erased.

No problem, I think, just use nandwrite and write the image back onto it....nope! Somehow my root partition is slightly too small for the image to fit!

So now I am stuck on booting it via NFS until I can figure out how to resize mtd paritions. Personally, due to the fact that I have been able to get zero dev work done due to dealing with this, and all the bad blocks, I would prefer an exchange for a new unit, but so far GlobalScale has not acknowledged any of the support questions I submitted, and it has been well over a week.

Code:
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00200000 00020000 "uImage"
mtd2: 1fd00000 00020000 "root"

# nandwrite -p /dev/mtd1 uImage.sheeva.20090319
Image 2106760 bytes, NAND page 2048 bytes, OOB area 2048 bytes, device size 2097152 bytes
Input file does not fit into device
Data was only partially written due to error

Does anyone know how to resize the mtd partitions, or build a smaller uImage image?
Pages: 1 [2]