Hi all
A very basic question
I replaced uImage on Beagleboard …with new kernel’s uImage
as far as i I know it will replace kernel .
but does that replace kernel modules also ?
or
we have to do something else to replace kernel modules?
It depends, does this new uImage have everything builtin? (then don't
worry about the modules)... If it relies on modules, you better update
them too to matching ones...
Regards,
I understood your point .Thanks a lot
i have downloaded linux-2.6.32 source and Now to create uImage …
inside kernel source directory i did
make -j3 ARCH=arm CROSS_COMPILE=/usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi- uImage
that gave me a uImage…
Q1)is that the right method to create uImage ?
i replaced uImage on BB with this uImage…BB is not able to boot …it stucks at uncompressing linux step …
Thanks
Nidhi
Is it really "stuck" or do you have the wrong ttyS2/ttyO2 value for
your serial console? Or even the serial console enabled? Add a
"earlyprintk" if your sure you have the other two things mentioned set
right to see past that....
Regards,
just to share with list …link suggested by Robert is
http://elinux.org/BeagleBoardUbuntu#Beagle_Bx.2FCx
But Robert ,
I already have successfully working image on sdcard – obtained from koen’s link
http://www.angstrom-distribution.org/building-angstrom
and i just want to change kernel …
then do i need to set console serial thing again…?
mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Ubuntu" -d ./boot.cmd ./boot.scr
Copy "boot.scr" to the Boot Partition
For "igepv2" users, rename this to "boot.ini"
and
do i need to change some parameters in the command in my case.?
thanks
Nidhi.
P.S:
just for the information , i am doing this as i want the ability , to insmod a kernel module in Beagleboard,which i am not able to do in my present kernel on Beagleboard,
1)i have taken linux2.6.32(same as version of linux came with angstrom) – from standard repository of linux kernel- (as i did not get source with angstrom image.)
2)took config file and compiler from angstrom setup directory where in image is kept.
3)compiled the required module
using make M=drivers/usb/gadget/ -C /home/mohit/files/beagle/
linux-2.6.32/ ARCH=arm CROSS_COMPILE=/home/mohit/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- modules
4)now copied .ko on BB, and insmod g_file_storage.ko gives error
g_file_storage: disagrees about version of symbol module_layout
insmod: error inserting ‘g_file_storage.ko’: -1 Invalid module format
so i am thinking that by changing kernel uImage , i will be able to insert , a module into it.
am i right ?
Thanks
Nidhi
Mohit, i shared the links with you over google talks as only a
reference to look at for how the serial port bootarg should be used..
Now you need to take some time and think/look at how your bootarg
variables are set and determine if you have them correct.. (ttyS2
kernel < 2.6.36, ttyO2 > 2.6.36)
Regards,
http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux
this link may help you guys…
thanks
bumble
Hello all
i have made boot.scr as suggested but its giving this error.
this is my boot_cmd file from which i made boot.scr
setenv bootargs ‘console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait’
mmc init
fatload mmc 0 0x80300000 uImage
bootm 0x80300000
boot
Probing for expansion boards, if none are connected you’ll see a harmless I2C error.
No EEPROM on expansion board
Beagle xM Rev A
Die ID #52a800011ff00000015739eb08017025
Hit any key to stop autoboot: 0
mmc1 is available
The user button is currently NOT pressed.
reading boot.scr
Invalid FAT entry
** Unable to read “boot.scr” from mmc 1:1 **
reading uImage
3013584 bytes read
Booting from mmc …
Booting kernel from Legacy Image at 80200000 …
Image Name: Linux-2.6.38.5
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3013520 Bytes = 2.9 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK
Loading Kernel Image … OK
OK
Starting kernel …
Uncompressing Linux… done, booting the kernel.
Please help
fix your sd card, more then likely your fatfs got corrupt, so it isn't
reading your custom boot.scr...
Regards,
Did you edit a file named boot.scr or create it with make image?
I’m just following along and trying to understand 
It´s more likely to be a corrupted fat partition (in sdcard).
I´m a newbie in linux environment and i edited the boot.scr file and i got something like “BAD CRC HEADER”, which is not the case.
I managed to change the boot.scr with mkimage and boot from my 4gb usb stick (it´s faster) and used Froyo with 720p resolution.
Try to reformat that sdcard and do all over again.
2011/5/4 mark hubrich <meistro57@gmail.com>
What I see from your compile statement
make -j3 ARCH=arm CROSS_COMPILE=/usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi- uImage
is that uImage is an ELF file unless the make script is compressing it too. So this seems to be an attempt to uncompress a file that is not compressed in the first place, so it might generate illegal opcodes and attempt to execute it. If this is true, I do not know a solution.
Usually kernel files that end with a z is compressed. Such as “vmlinuz” while “vmlinux” is the uncompressed copy of the kernel image.
uImage is perfectly fine, it's the final output, from when vmlinuz is
wrapped in a u-boot compatible header via a the u-boot prog/script
(mkimage)...
Regards,