Do you have a uEnv.txt file on the fat partition?
What are the contents?

On Thu, May 15, 2014 at 2:15 PM, Daniel Hastings <
[email protected]> wrote:

> Thanks for your reply.
>
> I had not previously but I think that I have now.
>
> I copied <kernel tree>/arch/arm/boot/dts/am335x-boneblack.dtb to /boot/
> but the boot process still hangs at the same spot.
>
>
> On Thursday, May 15, 2014 10:06:56 AM UTC-7, cody wrote:
>
>> Did you move the correct .dtb into the /boot directory
>>
>>
>> On Thu, May 15, 2014 at 11:07 AM, Daniel Hastings <daniel.robe...@gmail.
>> com> wrote:
>>
>>> Hello,
>>>
>>> I've been trying to get a kernel build environment set up for my BBB.
>>> I've set up a cross compiler and I've followed the following steps.
>>>
>>> git clone git://github.com/beagleboard/kernel.git
>>> cd kernel
>>> git checkout 3.8
>>> ./patch.sh
>>> cp configs/beaglebone kernel/arch/arm/configs/beaglebone_defconfig
>>> wget 
>>> http://arago-project.org/git/projects/?p=am33x-cm3.git\;a=blob_plain\;f=bin/am335x-pm-firmware.bin\;hb=HEAD
>>>  -O kernel/firmware/am335x-pm-firmware.bin
>>> cd kernel
>>> make ARCH=arm CROSS_COMPILE=${CC} beaglebone_defconfig -j4
>>> make ARCH=arm CROSS_COMPILE=${CC} uImage dtbs LOADADDR=0x80008000 -j4
>>> make ARCH=arm CROSS_COMPILE=${CC} uImage-dtb.am335x-boneblack 
>>> LOADADDR=0x80008000 -j4
>>>
>>>
>>> make ARCH=arm CROSS_COMPILE=${CC} modules -j4
>>>
>>>
>>> I've moved the modules created into /lib/modules/<version> and copied the 
>>> uImage into /boot in the second partition of the mmc.
>>>
>>>
>>> When trying to boot the new kernel, this is the last output I receive over 
>>> the serial port:
>>>
>>>
>>> Booting from mmc ...
>>>
>>> ## Booting kernel from Legacy Image at 80007fc0 ...
>>>
>>>    Image Name:   Linux-3.8.13+
>>>
>>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>>
>>>    Data Size:    4311374 Bytes = 4.1 MiB
>>>
>>>    Load Address: 80008000
>>>
>>>    Entry Point:  80008000
>>>
>>>    Verifying Checksum ... OK
>>>
>>> ## Flattened Device Tree blob at 80f80000
>>>
>>>    Booting using the fdt blob at 0x80f80000
>>>
>>>    XIP Kernel Image ... OK
>>>
>>> OK
>>>
>>>    Using Device Tree in place at 80f80000, end 80f89133
>>>
>>>
>>> Starting kernel ...
>>>
>>>
>>> Uncompressing Linux... done, booting the kernel.
>>>
>>>
>>> Then it just hangs with no led activity until I power cycle it.
>>>
>>>
>>> I think that this indicates that uboot has finished and that the problem 
>>> must lie with the kernel I've built. Perhaps I'm missing an option 
>>> somewhere?
>>>
>>>
>>> I've tried both using the beaglebone_defconfig and using the info from 
>>> /proc/config.gz to build a kernel. I've tried two cross compiler tool 
>>> chains and I've let the thing build natively overnight and still it hangs 
>>> on "done, booting the kernel".
>>>
>>>
>>> Does anyone have any idea what I may be doing wrong?
>>>
>>>
>>> Thanks,
>>>
>>> Dan
>>>
>>>
>>>  --
>>> 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 [email protected].
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to