Hi Robert:
Thanks for the replies.
So what does this build_deb.sh
Compared to Ubuntu 11.10 here:
http://elinux.org/BeagleBoardUbuntu#Oneiric_11.10.
Do I need to build_deb.sh as well? I don’t see mention of it in the README.
In general, should I be running all of the following scripts before I run “./tools/install_image.sh”:
Build: Debian deb package:
“./build_deb.sh”
Create SGX install Package: (OMAP3/DM37xx only, no PandaBoard Support)
“./create_sgx_package.sh”
Create DSP install Package: (OMAP3/DM37xx only, no PandaBoard Support)
“./create_dsp_package.sh”
Thanks!
Hi Robert:
Thanks for the replies.
So what does this build_deb.sh
Compared to Ubuntu 11.10 here:
BeagleBoardUbuntu - eLinux.org.
Do I need to build_deb.sh as well? I don't see mention of it in the README.
Instead of building just the zImage/modules... it builds a debian
*.deb package, mostly useful for installing on a device not near
you...
Think of it as:
./build_kernel.sh (zimage/modules) installing to an sd card you have
at your desk..
./build_deb.sh (deb) installing to a system running in the basement
and you don't want to walk down and remove the sd card..
Create SGX install Package: (OMAP3/DM37xx only, no PandaBoard Support)
"./create_sgx_package.sh"
Create DSP install Package: (OMAP3/DM37xx only, no PandaBoard Support)
"./create_dsp_package.sh"
Both of these last tools just add more closed source features... Not
necessary for every 'build'...
Regards,
Hi Robert:
It sounds like for BeagleBoardxM Rev. C this is turning into:
- Partition blank mini-SD like this:
http://eewiki.net/display/linuxonarm/BeagleBoard#BeagleBoard-SetupmicroSDcard
-
git clone git://github.com/RobertCNelson/stable-kernel.git
-
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
-
cp system.sh.sample system.sh
-
Make the following edits to system.sh:
5.1 Add cross compiler path:
CC=/usr/bin/arm-linux-gnueabi-
5.2. Add physical address in memory for the kernel entry point:
##For TI: OMAP3/4/AM35xx
ZRELADDR=0x80008000
5.3. Question - Do I need to add this line to system.sh? The comments in the script confuse me because you just had me partition the mini-SD:
MMC=/dev/sdb
As in:
###OPTIONAL: (REQUIRED FOR RUNNING: ./tools/load_uImage.sh & ./tools/load_uImage-net.sh)
##Note: This operates on raw disks, NOT PARTITIONS
##WRONG: MMC=/dev/mmcblk0p1
##CORRECT: MMC=/dev/mmcblk0
##WRONG: MMC=/dev/sde1
##CORRECT: MMC=/dev/sde
MMC=/dev/sdb
-
./build_kernel.sh
-
./tools/install_image.sh
-
Unmount the mini-SD
-
Pop the mini-SD into the BeagleBoard and power it on
Does this sound correct? I see the content about uEnv.txt at:
http://eewiki.net/display/linuxonarm/BeagleBoard#BeagleBoard-SetupmicroSDcard
I don’t to do any of that?
Thanks,
Bill
Hi Robert:
It sounds like for BeagleBoardxM Rev. C this is turning into:
1. Partition blank mini-SD like this:
http://eewiki.net/display/linuxonarm/BeagleBoard#BeagleBoard-SetupmicroSDcard
2. git clone git://github.com/RobertCNelson/stable-kernel.git
3. git clone
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
4. cp system.sh.sample system.sh
5. Make the following edits to system.sh:
5\.1 Add cross compiler path:
CC=/usr/bin/arm\-linux\-gnueabi\-
5\.2\. Add physical address in memory for the kernel entry point:
\#\#For TI: OMAP3/4/AM35xx
ZRELADDR=0x80008000
5\.3\. Question \- Do I need to add this line to system\.sh? The comments
in the script confuse me because you just had me partition the mini-SD:
MMC=/dev/sdb
This is just referenced by "./tools/install_image.sh" the next step
would be fore "./tools/install_image.sh" to scan and ask you
specifically which device you want.. (then the variable could be
deleted)... but all this does it copy the zImage/uImage and modules to
the sd card.. you can do this by hand too if you want..
6. ./build_kernel.sh
7. ./tools/install_image.sh
8. Unmount the mini-SD
9. Pop the mini-SD into the BeagleBoard and power it on
Does this sound correct? I see the content about uEnv.txt at:
http://eewiki.net/display/linuxonarm/BeagleBoard#BeagleBoard-SetupmicroSDcard
I don't to do any of that?
Without creating a uEnv.txt, it'll just go:
MLO -> u-boot.img -> fail to read uEnv.txt -> never-never-land based
on built-in u-boot variables..
Regards,