Hi,
I have done it from Windows with Open tftp, but the process failed.
tftpboot 0x80F80000 am335x-boneblack.dtb
tftpboot 0x80007FC0 uImage
setenv bootargs console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4
rootwait
bootm 0x80007FC0 - 0x80F80000
All works until last step which returns:
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
I have no reboot the BBB yet, but it is probably even if I repeat the
process for zImage it will failed too.
Is there any way to check the kernel?
KR!
El miércoles, 27 de enero de 2016, 17:31:54 (UTC+1), RobertCNelson escribió:
>
> On Wed, Jan 27, 2016 at 9:43 AM, <yol...@gmail.com <javascript:>> wrote:
> > Hi all,
> >
> > finally I have launched myself to build a new kernel for my BeaglBone
> Black,
> > as this is my first time, I have read lot of links and follow the steps
> > proposed at some of them.
> > I have been able to cconfigure and compile the kernel, but there is no
> way
> > to upload the kernel to target, BeagleBone Black. So, I can't verify if
> it
> > is working or not.
> >
> > I'm going to explain all the steps I have done, and what I have tested
> in
> > order to get your help.
> >
> > BeagleBone Black Configuration:
> >
> > Hardware: BeagleBone Black 4GB rev.C
> > OS: Debian 4.6.3-14
> > Kernel (current): 3.8.13-bone79
> > Internet connection: USB ('USB0')
> >
> >
> > Configure and Compile the Kernel: [Link]
> >
> > 1. ARM Cross Compiler: arm-linux-gnueabihf-
> >
> > 2. GIT -> downloaded kernel 4.1
> >
> > 3. Installed 'lzop' tool and 'libssl-dev'.
> >
> > 4. Downloaded U-Boot tools, made and installed (included 'mkimage'
> tool).
> >
> >
> >
> > wget ftp://ftp.denx.de/pub/u-boot/u-boot-latest.tar.bz2
> > tar -xjf u-boot-latest.tar.bz2
> > cd into u-boot directory
> > make sandbox_defconfig tools-only
> > sudo install tools/mkimage /usr/local/bin
> >
> >
> >
> > 5. Compiled the BeagleBone Black kernel.
> >
> > git clone git://github.com/beagleboard/linux.git
> >
> > cd linux
> >
> > git checkout 4.1
> >
> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bb.org_defconfig
> >
> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig (To modify
> > some features)
> >
> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
> >
> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- uImage dtbs
> > LOADADDR=0x80008000 -j4
> >
> >
> >
> > 6. Build kernel modules.
> >
> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- modules -j4
> >
> >
> >
> > 7. Rootfs folder:
> >
> > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
> > INSTALL_MOD_PATH=/home/user/export/rootfs modules_install
> >
> >
> > Once, kernel is built, it is upload time. For such action, I have test
> both
> > suggestions from link above, also another one.
> > Now, I will explain how I have tried to do it and the results, moreover
> my
> > doubts.
> >
> > Upload Kernel:
> >
> > Way1 (brute force):
> >
> > To be fast, '4.1.15' modules were copied to '/lib/modules/4.1.15' path.
> > uImage was copied from 'arch/arm/boot' on Host-PC to '/boot/uboot' on
> BBB.
> > am335x-boneblack.dtb was copied from 'arch/arm/boot/dts' on Host-PC to
> > '/boot/uboot/dtbs' on BBB.
> > Then, BBB is rebooted, but BBB is halted at boot. The four leds are
> switched
> > on permanently.
> > I have to restore the BBB with the SD Card.
> >
> > Which is the right kernel image, uImage or zImage? I have compiled
> uImage
> > but I saw at so many websites that the image to upload is zImage.
>
> Don't bother with "uImage".. Use the zImage...
>
> Grab a 3.3v ftdi usb serial cable and actually watch the boot process,
> unless you enjoy guessing what's going on..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
