Hi,
On my Beaglebone A6 I am using the UBoot, which came with the
Angstrom-distribution. I have switched to Gentoo though.
Of Robert Nelsons kernels I was using version 3.2.*, which
I copied by hand via ssh on the beaglebone and uses a link
<current> kernel ==> uImage on /boot, which works fine.
On the one hand, I dont want to leave the "stable home" of the
3.2.*-series of kernels on the other hand I will try something
new.
Since the 3.7.* kernels on my PC offer a driver for my dvbt usbstick I
tried to compile the current 3.7.* kernel for the Beaglebone.
The compilation runs fine and produces a couple of files in the deploy
directory.
Unfortunately the scheme of ssh-copying and linking some files onto my
beaglebone no longer works...and in the deploy directory there are
some files/directories, which are unknown to me (not available with
the 3.2.* series).
Mainly this is the
dtbs
and the
fir
directory and the files contained in them.
Where can I find a howto/tutorial which points out the differences in
installing a 3.7.* kernel in comparison to the 3.2.* kernel and how to
use both on the same SD card with the same UBoot?
Thank you very much in advance for any help!
Best regards,
mcc
Hi,
On my Beaglebone A6 I am using the UBoot, which came with the
Angstrom-distribution. I have switched to Gentoo though.
Of Robert Nelsons kernels I was using version 3.2.*, which
I copied by hand via ssh on the beaglebone and uses a link
<current> kernel ==> uImage on /boot, which works fine.
On the one hand, I dont want to leave the "stable home" of the
3.2.*-series of kernels on the other hand I will try something
new.
Since the 3.7.* kernels on my PC offer a driver for my dvbt usbstick I
tried to compile the current 3.7.* kernel for the Beaglebone.
The compilation runs fine and produces a couple of files in the deploy
directory.
Unfortunately the scheme of ssh-copying and linking some files onto my
beaglebone no longer works...and in the deploy directory there are
some files/directories, which are unknown to me (not available with
the 3.2.* series).
Mainly this is the
dtbs
and the
fir
directory and the files contained in them.
Those are temporary.. Just ignore... They get tar'ed up into the
modules/firmware files..
Where can I find a howto/tutorial which points out the differences in
installing a 3.7.* kernel in comparison to the 3.2.* kernel and how to
use both on the same SD card with the same UBoot?
Well, then that's a great opportunity for someone to create a
blog/wiki post on doing it. 
Go for it!..
hint, use:
http://cateee.net/lkddb/web-lkddb/ARM_APPENDED_DTB.html
directions are ^ for creating the new "zImage" with dtb file for the
bone.. (am335x-bone.dts)
Regards,
Robert Nelson <robertcnelson@gmail.com> [13-02-13 20:12]:
> Hi,
>
> On my Beaglebone A6 I am using the UBoot, which came with the
> Angstrom-distribution. I have switched to Gentoo though.
>
> Of Robert Nelsons kernels I was using version 3.2.*, which
> I copied by hand via ssh on the beaglebone and uses a link
> <current> kernel ==> uImage on /boot, which works fine.
>
> On the one hand, I dont want to leave the "stable home" of the
> 3.2.*-series of kernels on the other hand I will try something
> new.
>
> Since the 3.7.* kernels on my PC offer a driver for my dvbt usbstick I
> tried to compile the current 3.7.* kernel for the Beaglebone.
>
> The compilation runs fine and produces a couple of files in the deploy
> directory.
>
> Unfortunately the scheme of ssh-copying and linking some files onto my
> beaglebone no longer works...and in the deploy directory there are
> some files/directories, which are unknown to me (not available with
> the 3.2.* series).
> Mainly this is the
> dtbs
> and the
> fir
> directory and the files contained in them.
Those are temporary.. Just ignore... They get tar'ed up into the
modules/firmware files..
> Where can I find a howto/tutorial which points out the differences in
> installing a 3.7.* kernel in comparison to the 3.2.* kernel and how to
> use both on the same SD card with the same UBoot?
Well, then that's a great opportunity for someone to create a
blog/wiki post on doing it. Go for it!..
hint, use:
Linux Kernel Driver DataBase: CONFIG_ARM_APPENDED_DTB: Use appended device tree blob to zImage (EXPERIMENTAL)
directions are ^ for creating the new "zImage" with dtb file for the
bone.. (am335x-bone.dts)
Regards,
--
Robert Nelson
http://www.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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Robert,
thank you for your reply ! :))
Question:
Does the including of DTB-files into the zImage that it will no longer
be possible to use uImage-files for booting? The system.sh still
offers the automagical generation of uImage-files, thoug -- but that
was commented out...?!?
Best regards,
mcc
Due to the nature of what mkimage does, you need to append the dtb to
the zImage first, then run the mkimage/uImage generator..
Regards,
Robert Nelson <robertcnelson@gmail.com> [13-02-13 20:12]:
> Hi,
>
> On my Beaglebone A6 I am using the UBoot, which came with the
> Angstrom-distribution. I have switched to Gentoo though.
>
> Of Robert Nelsons kernels I was using version 3.2.*, which
> I copied by hand via ssh on the beaglebone and uses a link
> <current> kernel ==> uImage on /boot, which works fine.
>
> On the one hand, I dont want to leave the "stable home" of the
> 3.2.*-series of kernels on the other hand I will try something
> new.
>
> Since the 3.7.* kernels on my PC offer a driver for my dvbt usbstick I
> tried to compile the current 3.7.* kernel for the Beaglebone.
>
> The compilation runs fine and produces a couple of files in the deploy
> directory.
>
> Unfortunately the scheme of ssh-copying and linking some files onto my
> beaglebone no longer works...and in the deploy directory there are
> some files/directories, which are unknown to me (not available with
> the 3.2.* series).
> Mainly this is the
> dtbs
> and the
> fir
> directory and the files contained in them.
Those are temporary.. Just ignore... They get tar'ed up into the
modules/firmware files..
> Where can I find a howto/tutorial which points out the differences in
> installing a 3.7.* kernel in comparison to the 3.2.* kernel and how to
> use both on the same SD card with the same UBoot?
Well, then that's a great opportunity for someone to create a
blog/wiki post on doing it. Go for it!..
hint, use:
Linux Kernel Driver DataBase: CONFIG_ARM_APPENDED_DTB: Use appended device tree blob to zImage (EXPERIMENTAL)
directions are ^ for creating the new "zImage" with dtb file for the
bone.. (am335x-bone.dts)
Regards,
--
Robert Nelson
http://www.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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Robert,
I tried my best but until with no success...
As far as I understand the whole thing:
The dtbs contains for each platform a kind of "hardware definition
database" (or something like that). With the option described via the
link you posted, the DTB is appended to zImage. But I didnt find a way
to either tell the kernel, on what platform it will start or tell to
tell the kernel build process, what dtb it has to include/append.
Is there any document with further information of this dtb/s stuff
available?
Best regards,
mcc
Hi Robert,
I tried my best but until with no success…
As far as I understand the whole thing:
The dtbs contains for each platform a kind of “hardware definition
database” (or something like that). With the option described via the
link you posted, the DTB is appended to zImage. But I didnt find a way
to either tell the kernel, on what platform it will start or tell to
tell the kernel build process, what dtb it has to include/append.
Is there any document with further information of this dtb/s stuff
available?
Well it’s a workaround for old bootloaders there is no select this dtb file logic. You need to cat it manually yourself.
Regards