Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

On 12/05/2013 03:53 PM, Robert Nelson wrote:


Well, the best option is to write a patch against:
https://github.com/beagleboard/kernel/tree/3.8
and then i'll merge it into both tree's and push out a new
debian/ubuntu kernel build. .;)  So everyone get's the patch and
supports your new cape out of the box...

Regards,


Robert,
I just wanted to check if you got the patch I sent you directly. I 
know you are very busy, so I was not expecting any immediate feedback.


Best regards,

Dave.

--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

Thanks Micka. I was considering just removing the request to capemgr via 
uEnv.txt, and writing a service to populate the slot. Ultimately the 
loading should be taken care of via the EEPROM signature, but that has 
not yet been implemented. I was just curious as to what was the 
difference between Debian and Angstrom which makes capemgr.enable_partno 
not work reliably on Debian.


Best regards,

Dave.



On 12/10/2013 01:53 AM, Micka wrote:


Why not disabling the cap manager at the boot (is it possible?) and 
later push yourself the config that you want in the slot?


Micka,

On Dec 10, 2013 5:50 AM, "David Lambert" > wrote:


On 12/09/2013 05:12 PM, Robert Nelson wrote:

On Mon, Dec 9, 2013 at 2:15 PM, David Lambert
mailto:d...@lambsys.com>> wrote:

In desperation, I added a printk to capemgr to print out
the return value
from request_firmware. I get -2 ENOENT, but the file name
is in
/lib/firmware exactly as printed in the error line.
Another thought is that
Debian appears to use initrd, whereas I don't think
Angstrom does? Could
this be the issue? Any ideas would be very welcome.

You could try updating the initrd..

sudo /boot/uboot/tools/update_boot_files.sh

Regards,

Thanks for the suggestion Robert. That is good to know,
unfortunately it did not fix the problem :-( I now suspect that
the firmware load request from capemgr is happening before
/lib/firmware is accessible, but this is just a WAG. I need to
understand the way capemgr works before I can offer any logical
explanation :-[

Regards,

Dave.

-- 
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/groups/opt_out.

--
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/groups/opt_out.


--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[Micka]

Why not disabling the cap manager at the boot (is it possible?) and later
push yourself the config that you want in the slot?

Micka,
On Dec 10, 2013 5:50 AM, "David Lambert"  wrote:

> On 12/09/2013 05:12 PM, Robert Nelson wrote:
>
>> On Mon, Dec 9, 2013 at 2:15 PM, David Lambert  wrote:
>>
>>> In desperation, I added a printk to capemgr to print out the return value
>>> from request_firmware. I get -2 ENOENT, but the file name is in
>>> /lib/firmware exactly as printed in the error line. Another thought is
>>> that
>>> Debian appears to use initrd, whereas I don't think Angstrom does? Could
>>> this be the issue? Any ideas would be very welcome.
>>>
>> You could try updating the initrd..
>>
>> sudo /boot/uboot/tools/update_boot_files.sh
>>
>> Regards,
>>
>>  Thanks for the suggestion Robert. That is good to know, unfortunately it
> did not fix the problem :-( I now suspect that the firmware load request
> from capemgr is happening before /lib/firmware is accessible, but this is
> just a WAG. I need to understand the way capemgr works before I can offer
> any logical explanation :-[
>
> Regards,
>
> Dave.
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

On 12/09/2013 05:12 PM, Robert Nelson wrote:

On Mon, Dec 9, 2013 at 2:15 PM, David Lambert  wrote:

In desperation, I added a printk to capemgr to print out the return value
from request_firmware. I get -2 ENOENT, but the file name is in
/lib/firmware exactly as printed in the error line. Another thought is that
Debian appears to use initrd, whereas I don't think Angstrom does? Could
this be the issue? Any ideas would be very welcome.

You could try updating the initrd..

sudo /boot/uboot/tools/update_boot_files.sh

Regards,

Thanks for the suggestion Robert. That is good to know, unfortunately it 
did not fix the problem :-( I now suspect that the firmware load request 
from capemgr is happening before /lib/firmware is accessible, but this 
is just a WAG. I need to understand the way capemgr works before I can 
offer any logical explanation :-[


Regards,

Dave.

--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[Robert Nelson]

On Mon, Dec 9, 2013 at 2:15 PM, David Lambert  wrote:
> In desperation, I added a printk to capemgr to print out the return value
> from request_firmware. I get -2 ENOENT, but the file name is in
> /lib/firmware exactly as printed in the error line. Another thought is that
> Debian appears to use initrd, whereas I don't think Angstrom does? Could
> this be the issue? Any ideas would be very welcome.

You could try updating the initrd..

sudo /boot/uboot/tools/update_boot_files.sh

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

In desperation, I added a printk to capemgr to print out the return 
value from request_firmware. I get -2 ENOENT, but the file name is in 
/lib/firmware exactly as printed in the error line. Another thought is 
that Debian appears to use initrd, whereas I don't think Angstrom does? 
Could this be the issue? Any ideas would be very welcome.


Thanks,

Dave.




On 12/09/2013 11:50 AM, David Lambert wrote:

Robert,

I switched to systemd, but the problem still exists. Is there a guide 
on debugging the cape manager? The only messages I see are:


[2.559511] bone-capemgr bone_capemgr.9: failed to load firmware 
'argus-ups-00A0.dtbo'
[2.567868] bone-capemgr bone_capemgr.9: loader: failed to load 
slot-7 argus-ups:00A0 (prio 0)


I would like to find out some more information as to why this failure.


Regards,

Dave.


On 12/06/2013 03:20 PM, William Hermans wrote:
Something like that, Robert would know better than I. I do have years 
of Debian experience, but much of the low level details I am 
unfamiliar with. This would be one of those cases.



On Fri, Dec 6, 2013 at 2:13 PM, David Lambert > wrote:


On 12/06/2013 03:02 PM, William Hermans wrote:

Perhaps the HDMI video and audio are not being disabled
quickly enough for your module to load. Another way to load
your module would be to write a startup service. Which you
can then load at any point in the Debian startup cycle. I
have a write up of an example here

:http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-init-scripts-default-gatewayand-ntpdate/


I think you may be right William. There may be a race condition
here. Sometimes when I boot, I get:


root@debian:~# cat /sys/devices/bone_capemgr.9/slots
 0: 54:PF---
 1: 55:PF---
 2: 56:PF---
 3: 57:PF---
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
 7: ff:P-O-L Override Board Name,00A0,Override Manuf,argus-ups

But the module is not loaded.

Other times I get nothing in slot 7.

I think one difference between my Angstrom system may be that
Angstrom uses systemd, and Debian uses System V init???

Anyway, I will try your suggestion.

Thanks,

Dave.



Turns out the reason why I wrote this short article was a
goof on my part. Also, the reasons why I did this may not
seen sane to some. Meaning, there could be a much easier way
to do the same things . . . but . . . whatever the case the
example is perfectly usable for different  situations.


-- 
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/groups/opt_out.


--
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/groups/opt_out.


--
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/groups/opt_out.


--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

Robert,

I switched to systemd, but the problem still exists. Is there a guide on 
debugging the cape manager? The only messages I see are:


[2.559511] bone-capemgr bone_capemgr.9: failed to load firmware 
'argus-ups-00A0.dtbo'
[2.567868] bone-capemgr bone_capemgr.9: loader: failed to load 
slot-7 argus-ups:00A0 (prio 0)


I would like to find out some more information as to why this failure.


Regards,

Dave.


On 12/06/2013 03:20 PM, William Hermans wrote:
Something like that, Robert would know better than I. I do have years 
of Debian experience, but much of the low level details I am 
unfamiliar with. This would be one of those cases.



On Fri, Dec 6, 2013 at 2:13 PM, David Lambert > wrote:


On 12/06/2013 03:02 PM, William Hermans wrote:

Perhaps the HDMI video and audio are not being disabled
quickly enough for your module to load. Another way to load
your module would be to write a startup service. Which you can
then load at any point in the Debian startup cycle. I have a
write up of an example here

:http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-init-scripts-default-gatewayand-ntpdate/


I think you may be right William. There may be a race condition
here. Sometimes when I boot, I get:


root@debian:~# cat /sys/devices/bone_capemgr.9/slots
 0: 54:PF---
 1: 55:PF---
 2: 56:PF---
 3: 57:PF---
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
 7: ff:P-O-L Override Board Name,00A0,Override Manuf,argus-ups

But the module is not loaded.

Other times I get nothing in slot 7.

I think one difference between my Angstrom system may be that
Angstrom uses systemd, and Debian uses System V init???

Anyway, I will try your suggestion.

Thanks,

Dave.



Turns out the reason why I wrote this short article was a goof
on my part. Also, the reasons why I did this may not seen sane
to some. Meaning, there could be a much easier way to do the
same things . . . but . . . whatever the case the example is
perfectly usable for different  situations.


-- 
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/groups/opt_out.


--
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/groups/opt_out.


--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[William Hermans]

Something like that, Robert would know better than I. I do have years of
Debian experience, but much of the low level details I am unfamiliar with.
This would be one of those cases.


On Fri, Dec 6, 2013 at 2:13 PM, David Lambert  wrote:

> On 12/06/2013 03:02 PM, William Hermans wrote:
>
>> Perhaps the HDMI video and audio are not being disabled quickly enough
>> for your module to load. Another way to load your module would be to write
>> a startup service. Which you can then load at any point in the Debian
>> startup cycle. I have a write up of an example here :
>> http://www.embeddedhobbyist.com/debian-tips/beaglebone-
>> black/beaglebone-black-init-scripts-default-gatewayand-ntpdate/
>>
>>  I think you may be right William. There may be a race condition here.
> Sometimes when I boot, I get:
>
>
> root@debian:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,argus-ups
>
> But the module is not loaded.
>
> Other times I get nothing in slot 7.
>
> I think one difference between my Angstrom system may be that Angstrom
> uses systemd, and Debian uses System V init???
>
> Anyway, I will try your suggestion.
>
> Thanks,
>
> Dave.
>
>
>
>  Turns out the reason why I wrote this short article was a goof on my
>> part. Also, the reasons why I did this may not seen sane to some. Meaning,
>> there could be a much easier way to do the same things . . . but . . .
>> whatever the case the example is perfectly usable for different  situations.
>>
>>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

On 12/06/2013 03:02 PM, William Hermans wrote:
Perhaps the HDMI video and audio are not being disabled quickly enough 
for your module to load. Another way to load your module would be to 
write a startup service. Which you can then load at any point in the 
Debian startup cycle. I have a write up of an example here 
:http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-init-scripts-default-gatewayand-ntpdate/ 



I think you may be right William. There may be a race condition here. 
Sometimes when I boot, I get:


root@debian:~# cat /sys/devices/bone_capemgr.9/slots
 0: 54:PF---
 1: 55:PF---
 2: 56:PF---
 3: 57:PF---
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
 7: ff:P-O-L Override Board Name,00A0,Override Manuf,argus-ups

But the module is not loaded.

Other times I get nothing in slot 7.

I think one difference between my Angstrom system may be that Angstrom 
uses systemd, and Debian uses System V init???


Anyway, I will try your suggestion.

Thanks,

Dave.


Turns out the reason why I wrote this short article was a goof on my 
part. Also, the reasons why I did this may not seen sane to some. 
Meaning, there could be a much easier way to do the same things . . . 
but . . . whatever the case the example is perfectly usable for 
different  situations.




--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[William Hermans]

Perhaps the HDMI video and audio are not being disabled quickly enough for
your module to load. Another way to load your module would be to write a
startup service. Which you can then load at any point in the Debian startup
cycle. I have a write up of an example here :
http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-init-scripts-default-gatewayand-ntpdate/

Turns out the reason why I wrote this short article was a goof on my part.
Also, the reasons why I did this may not seen sane to some. Meaning, there
could be a much easier way to do the same things . . . but . . . whatever
the case the example is perfectly usable for different  situations.


On Fri, Dec 6, 2013 at 1:48 PM, David Lambert  wrote:

> On 12/06/2013 02:31 PM, Robert Nelson wrote:
>
>> Very strange... Does it help in any way to dump the argus-ups dtbo to
>> /lib/firmware/ ?
>>
>>  I am not sure what you mean by "dump"? The dtbo was put in /lib/firmware
> by your scripts:
>
> root@debian:~# ls -l /lib/firmware/arg*
> -rw-r--r-- 1 dlambert dlambert 1677 Dec  6 13:45
> /lib/firmware/argus-ups-00A0.dtbo
>
> Regards,
>
> Dave.
>
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

On 12/06/2013 02:31 PM, Robert Nelson wrote:

Very strange... Does it help in any way to dump the argus-ups dtbo to
/lib/firmware/ ?

I am not sure what you mean by "dump"? The dtbo was put in /lib/firmware 
by your scripts:


root@debian:~# ls -l /lib/firmware/arg*
-rw-r--r-- 1 dlambert dlambert 1677 Dec  6 13:45 
/lib/firmware/argus-ups-00A0.dtbo


Regards,

Dave.

--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

On 12/06/2013 02:37 PM, William Hermans wrote:
I think that just a space between the disable / enables lines is all 
you need. There are a couple ways I could read your last message as in 
text formating etc, but be sure there are no Windows type white spaces 
or more specifically what Microsoft OSes call a line feed.

Thanks for the suggestion William.
I removed the backslash to no avail. The module refuses to autoload. 
Here is the dmesg dump of the kernel command line:
[0.00] Kernel command line: console=ttyO0,115200n8 
capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
capemgr.enable_partno=argus-ups VIDEO_DISPLAY root=/dev/mmcblk0p5 ro 
rootfstype=ext4 rootwait fixrtc


To be succinct: If you're using backslash to esc the line to make your 
file more readable. Dont. put it all on one line.



Regards,

Dave.

--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[William Hermans]

I think that just a space between the disable / enables lines is all you
need. There are a couple ways I could read your last message as in text
formating etc, but be sure there are no Windows type white spaces or more
specifically what Microsoft OSes call a line feed.

To be succinct: If you're using backslash to esc the line to make your file
more readable. Dont. put it all on one line.


On Fri, Dec 6, 2013 at 1:14 PM, David Lambert  wrote:

> On 12/06/2013 01:20 PM, Robert Nelson wrote:
>
>> BTW, if you used my kernel build script, the config is already setup
>> to place the *.dtbo's (firmware) into into the kernel (zImage). So if
>> your utilizing a new one, you don't actually have to copy the *.dtbo
>> to the /lib/firmware/ directory..
>>
> Thanks so much for your help, your scripts really help simplify things a
> lot!
> BTW I am going to change the name of my module to something more
> appropriate before sending you a patch. I just need to test it first with
> the "argus-ups" name.
> I am getting really close now, but do not seem to be able to automatically
> load my driver/dt. Manually all works fine, as follows:
>
> root@debian:~# echo argus-ups:00A0 > /sys/devices/bone_capemgr.9/slots
> [  543.266228] bone-capemgr bone_capemgr.9: part_number 'argus-ups',
> version '00A0'
> [  543.274815] bone-capemgr bone_capemgr.9: slot #8: generic override
> [  543.281388] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data at slot 8
> [  543.289441] bone-capemgr bone_capemgr.9: slot #8: 'Override Board
> Name,00A0,Override Manuf,argus-ups'
> [  543.299325] bone-capemgr bone_capemgr.9: slot #8: Requesting part
> number/version based 'argus-ups-00A0.dtbo
> [  543.309581] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware
> 'argus-ups-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
> [  543.328913] bone-capemgr bone_capemgr.9: slot #8: dtbo
> 'argus-ups-00A0.dtbo' loaded; converting to live tree
> [  543.340358] bone-capemgr bone_capemgr.9: slot #8: #2 overlays
> [  543.352047] bone-capemgr bone_capemgr.9: slot #8: Applied #2 overlays.
> root@debian:~# [  543.368913] Init UPS module - debug=0, shutdown=1
> [  543.375128] Debug parameter read from DT:0
> [  543.379479] Shutdown parameter read from DT:1
>
> root@debian:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,argus-ups
>
> But if I add:
>
> optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN \
> capemgr.enable_partno=argus-ups
>
> to the start of uEnv.txt, then I get the following in dmesg:
>
>
> --snip--
> [0.00] Kernel command line: console=ttyO0,115200n8
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
> capemgr.enable_partno=argus-ups VIDEO_DISPLAY root=/dev/mmcblk0p5 ro
> rootfstype=ext4 rootwait fixrtc
> --snip--
> [1.382046] bone-capemgr bone_capemgr.9: Skipping disabled cape with
> part# BB-BONELT-HDMIN
> [1.420581] bone-capemgr bone_capemgr.9: slot #0: No cape found
> [1.457686] bone-capemgr bone_capemgr.9: slot #1: No cape found
> [1.494794] bone-capemgr bone_capemgr.9: slot #2: No cape found
> [1.531905] bone-capemgr bone_capemgr.9: slot #3: No cape found
> [1.538151] bone-capemgr bone_capemgr.9: slot #4: specific override
> [1.544751] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data at slot 4
> [1.552798] bone-capemgr bone_capemgr.9: slot #4:
> 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
> [1.562915] bone-capemgr bone_capemgr.9: slot #5: specific override
> [1.569510] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data at slot 5
> [1.577555] bone-capemgr bone_capemgr.9: slot #5:
> 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
> [1.587569] bone-capemgr bone_capemgr.9: slot #6: specific override
> [1.594164] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data at slot 6
> [1.602209] bone-capemgr bone_capemgr.9: slot #6:
> 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
> [1.612420] bone-capemgr bone_capemgr.9: enabled_partno part_number
> 'argus-ups', version 'N/A', prio '0'
> [1.622379] bone-capemgr bone_capemgr.9: slot #7: generic override
> [1.628873] bone-capemgr bone_capemgr.9: bone: Using override eeprom
> data at slot 7
> [1.636917] bone-capemgr bone_capemgr.9: slot #7: 'Override Board
> Name,00A0,Override Manuf,argus-ups'
> [1.646758] bone-capemgr bone_capemgr.9: Skipping loading of disabled
> cape with part# BB-BONELT-HDMI
> [1.656356] bone-capemgr bone_capemgr.9: Skipping loading of disabled
> cape with part# BB-BONELT-HDMIN
> [1.666237] bone-capemgr bone_capemgr.9: loader: before slot-4
> BB-BONE-EMMC-2G:00A0 (prio 1)
> 

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[Robert Nelson]

On Fri, Dec 6, 2013 at 2:14 PM, David Lambert  wrote:
> On 12/06/2013 01:20 PM, Robert Nelson wrote:
>>
>> BTW, if you used my kernel build script, the config is already setup
>> to place the *.dtbo's (firmware) into into the kernel (zImage). So if
>> your utilizing a new one, you don't actually have to copy the *.dtbo
>> to the /lib/firmware/ directory..
>
> Thanks so much for your help, your scripts really help simplify things a
> lot!
> BTW I am going to change the name of my module to something more appropriate
> before sending you a patch. I just need to test it first with the
> "argus-ups" name.
> I am getting really close now, but do not seem to be able to automatically
> load my driver/dt. Manually all works fine, as follows:

Very strange... Does it help in any way to dump the argus-ups dtbo to
/lib/firmware/ ?

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

On 12/06/2013 01:20 PM, Robert Nelson wrote:

BTW, if you used my kernel build script, the config is already setup
to place the *.dtbo's (firmware) into into the kernel (zImage). So if
your utilizing a new one, you don't actually have to copy the *.dtbo
to the /lib/firmware/ directory..
Thanks so much for your help, your scripts really help simplify things a 
lot!
BTW I am going to change the name of my module to something more 
appropriate before sending you a patch. I just need to test it first 
with the "argus-ups" name.
I am getting really close now, but do not seem to be able to 
automatically load my driver/dt. Manually all works fine, as follows:


root@debian:~# echo argus-ups:00A0 > /sys/devices/bone_capemgr.9/slots
[  543.266228] bone-capemgr bone_capemgr.9: part_number 'argus-ups', 
version '00A0'

[  543.274815] bone-capemgr bone_capemgr.9: slot #8: generic override
[  543.281388] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 8
[  543.289441] bone-capemgr bone_capemgr.9: slot #8: 'Override Board 
Name,00A0,Override Manuf,argus-ups'
[  543.299325] bone-capemgr bone_capemgr.9: slot #8: Requesting part 
number/version based 'argus-ups-00A0.dtbo
[  543.309581] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware 
'argus-ups-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[  543.328913] bone-capemgr bone_capemgr.9: slot #8: dtbo 
'argus-ups-00A0.dtbo' loaded; converting to live tree

[  543.340358] bone-capemgr bone_capemgr.9: slot #8: #2 overlays
[  543.352047] bone-capemgr bone_capemgr.9: slot #8: Applied #2 overlays.
root@debian:~# [  543.368913] Init UPS module - debug=0, shutdown=1
[  543.375128] Debug parameter read from DT:0
[  543.379479] Shutdown parameter read from DT:1

root@debian:~# cat /sys/devices/bone_capemgr.9/slots
 0: 54:PF---
 1: 55:PF---
 2: 56:PF---
 3: 57:PF---
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
 8: ff:P-O-L Override Board Name,00A0,Override Manuf,argus-ups

But if I add:

optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN \
capemgr.enable_partno=argus-ups

to the start of uEnv.txt, then I get the following in dmesg:


--snip--
[0.00] Kernel command line: console=ttyO0,115200n8 
capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
capemgr.enable_partno=argus-ups VIDEO_DISPLAY root=/dev/mmcblk0p5 ro 
rootfstype=ext4 rootwait fixrtc

--snip--
[1.382046] bone-capemgr bone_capemgr.9: Skipping disabled cape with 
part# BB-BONELT-HDMIN

[1.420581] bone-capemgr bone_capemgr.9: slot #0: No cape found
[1.457686] bone-capemgr bone_capemgr.9: slot #1: No cape found
[1.494794] bone-capemgr bone_capemgr.9: slot #2: No cape found
[1.531905] bone-capemgr bone_capemgr.9: slot #3: No cape found
[1.538151] bone-capemgr bone_capemgr.9: slot #4: specific override
[1.544751] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 4
[1.552798] bone-capemgr bone_capemgr.9: slot #4: 
'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'

[1.562915] bone-capemgr bone_capemgr.9: slot #5: specific override
[1.569510] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 5
[1.577555] bone-capemgr bone_capemgr.9: slot #5: 
'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'

[1.587569] bone-capemgr bone_capemgr.9: slot #6: specific override
[1.594164] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 6
[1.602209] bone-capemgr bone_capemgr.9: slot #6: 
'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
[1.612420] bone-capemgr bone_capemgr.9: enabled_partno part_number 
'argus-ups', version 'N/A', prio '0'

[1.622379] bone-capemgr bone_capemgr.9: slot #7: generic override
[1.628873] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
data at slot 7
[1.636917] bone-capemgr bone_capemgr.9: slot #7: 'Override Board 
Name,00A0,Override Manuf,argus-ups'
[1.646758] bone-capemgr bone_capemgr.9: Skipping loading of disabled 
cape with part# BB-BONELT-HDMI
[1.656356] bone-capemgr bone_capemgr.9: Skipping loading of disabled 
cape with part# BB-BONELT-HDMIN
[1.666237] bone-capemgr bone_capemgr.9: loader: before slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1)
[1.675115] bone-capemgr bone_capemgr.9: loader: check slot-4 
BB-BONE-EMMC-2G:00A0 (prio 1)

[1.683911] bone-capemgr bone_capemgr.9: initialized OK.
[1.689508] bone-capemgr bone_capemgr.9: loader: before slot-7 
argus-ups:00A0 (prio 0)
[1.697824] bone-capemgr bone_capemgr.9: loader: check slot-7 
argus-ups:00A0 (prio 0)

[1.707286] OneNAND driver initializing
[1.712253] usbcore: registered new interface driver cdc_ether
[1.718459] usbcore: registered new interface driver rndis_host
[1.724749] bone-capemgr bone_capemgr.9: loader: check slot-4 
BB-BONE-EMMC-2G:00

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[Robert Nelson]

On Fri, Dec 6, 2013 at 1:15 PM, David Lambert  wrote:
> Thanks Robert. This make perfect sense now. Sorry for the dumb question :-[

Not a problem Dave..

BTW, if you used my kernel build script, the config is already setup
to place the *.dtbo's (firmware) into into the kernel (zImage). So if
your utilizing a new one, you don't actually have to copy the *.dtbo
to the /lib/firmware/ directory..

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

Thanks Robert. This make perfect sense now. Sorry for the dumb question :-[

Regards,

Dave.

On 12/06/2013 12:19 PM, Robert Nelson wrote:


I'm not sure on your confusion.  With Angstrom the bootloader/uEnv.txt
matched each other and since they programmed them at the factory they
had a 100% guarantee of what was installed.  In my case, I have to
deal with the original factory u-boot/MLO, and i also support a good
dozen more boards.  So for my sanity the uEnv.txt has a lot of generic
options that override some of the factory defaults for this board.

So if you compare with a board that has no factory (NAND/eMMC) like
the orignal bone, the uEnv.txt is a lot simpler:
http://eewiki.net/display/linuxonarm/BeagleBone#BeagleBone-uEnv.txtbasedbootscript

So back to the line:
loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f /dtbs/${fdtfile}

For the bone (this image will boot on board boards):
ftdfile: (set by u-boot.img)
am335x-boneblack.dtb
am335x-bone.dtb

you can also override this with "fdtfile=am335x-mycape.dtb"  (all
dtb's are in a single directory in the fat partition)

mmcdev:
0: microSD
1: eMMC

mmcpart:
1: (fat partition..) (i don't use 2, ext4)

In your case, follow William's example and add:

optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

To the top of the uEnv.txt..

Regards,



--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

I may be barking up the wrong tree here, but I also notice that the 
uboot partition contains dtbs (see below). Do I need to put my cape's 
dtb here? Also I am attaching the uEnv.txt from the Debian system. I am 
particularly confused by the line:


loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f /dtbs/${fdtfile}

I have been looking for some documentation on this without success.

Best regards,

Dave.



root@debian:~# ls -R /boot/uboot/dtbs/
/boot/uboot/dtbs/:
am335x-boneblack.dtb   omap3430-sdp.dtb  omap4-panda.dtb
am335x-bone.dtbomap3-beagle.dtb  omap4-panda-es.dtb
am335x-evm.dtb omap3-beagle-xm.dtb   omap4-sdp.dtb
am335x-evmsk.dtb   omap3-devkit8000.dtb omap4-sdp-es23plus.dtb
am335x-tester.dtb  omap3-evm.dtb omap4-var-som.dtb
am3517-evm.dtb omap3-igep0020.dtbomap5-evm.dtb
am3517_mt_ventoux.dtb  omap3-igep0030.dtbomap5-uevm.dtb
am43x-epos-evm.dtb omap3-tobi.dtb
omap2420-h4.dtbomap4-panda-a4.dtb


On 12/06/2013 11:58 AM, William Hermans wrote:

Errr, that is as long as the file names have not changed . . .

I also wanted to point out that that technically uEnv.txt and uboot 
have *nothing* to do with the OS in particular. However in this case 
optargs are passed to the kernel when it starts up so . ..



On Fri, Dec 6, 2013 at 10:55 AM, William Hermans > wrote:


optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN




On Fri, Dec 6, 2013 at 10:48 AM, David Lambert mailto:d...@lambsys.com>> wrote:

On 12/05/2013 03:53 PM, Robert Nelson wrote:

Well, the best option is to write a patch against:
https://github.com/beagleboard/kernel/tree/3.8
and then i'll merge it into both tree's and push out a new
debian/ubuntu kernel build. .;)  So everyone get's the
patch and
supports your new cape out of the box...

Regards,

Well I got my module and dtb to compile and install cleanly,
but I am now confused by the uEnv.txt. It appears to be much
more complex than the one I used for Angstrom (attached). I
would like to disable the HDMI virtual cape and enable mine.
Is there a wiki that explains how to do this with Debian?

Regards,

Dave.

-- 
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/groups/opt_out.



--
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/groups/opt_out.


--
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/groups/opt_out.
#Normal Boot
initrd_high=0x
fdt_high=0x

kernel_file=zImage
initrd_file=initrd.img

console=ttyO0,115200n8

mmcroot=/dev/mmcblk0p5 ro
mmcrootfstype=ext4 rootwait fixrtc

loadkernel=load mmc ${mmcdev}:${mmcpart} 0x8030 ${kernel_file}
loadinitrd=load mmc ${mmcdev}:${mmcpart} 0x8160 ${initrd_file}; setenv 
initrd_size ${filesize}
loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f /dtbs/${fdtfile}

boot_classic=run loadkernel; run loadinitrd
boot_fdt=run loadkernel; run loadinitrd; run loadfdt

video_args=setenv video VIDEO_DISPLAY
device_args=run video_args; run expansion_args; run mmcargs
mmcargs=setenv bootargs console=${console} ${optargs} ${video} root=${mmcroot} 
rootfstype=${mmcrootfstype} ${expansion}

expansion_args=setenv expansion
#Classic Board File Boot:
#uenvcmd=run boot_classic; run device_args; bootz 0x8030 
0x8160:${initrd_size}
#New Device Tree Boot:
uenvcmd=run boot_fdt; run device_args; bootz 0x8030 
0x8160:${initrd_size} 0x815f

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[Robert Nelson]

On Fri, Dec 6, 2013 at 12:12 PM, David Lambert  wrote:
> I may be barking up the wrong tree here, but I also notice that the uboot
> partition contains dtbs (see below). Do I need to put my cape's dtb here?
> Also I am attaching the uEnv.txt from the Debian system. I am particularly
> confused by the line:
>
> loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f /dtbs/${fdtfile}
>
> I have been looking for some documentation on this without success.

I'm not sure on your confusion.  With Angstrom the bootloader/uEnv.txt
matched each other and since they programmed them at the factory they
had a 100% guarantee of what was installed.  In my case, I have to
deal with the original factory u-boot/MLO, and i also support a good
dozen more boards.  So for my sanity the uEnv.txt has a lot of generic
options that override some of the factory defaults for this board.

So if you compare with a board that has no factory (NAND/eMMC) like
the orignal bone, the uEnv.txt is a lot simpler:
http://eewiki.net/display/linuxonarm/BeagleBone#BeagleBone-uEnv.txtbasedbootscript

So back to the line:
loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f /dtbs/${fdtfile}

For the bone (this image will boot on board boards):
ftdfile: (set by u-boot.img)
am335x-boneblack.dtb
am335x-bone.dtb

you can also override this with "fdtfile=am335x-mycape.dtb"  (all
dtb's are in a single directory in the fat partition)

mmcdev:
0: microSD
1: eMMC

mmcpart:
1: (fat partition..) (i don't use 2, ext4)

In your case, follow William's example and add:

optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

To the top of the uEnv.txt..

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[William Hermans]

Errr, that is as long as the file names have not changed . . .

I also wanted to point out that that technically uEnv.txt and uboot have
*nothing* to do with the OS in particular. However in this case optargs are
passed to the kernel when it starts up so . ..


On Fri, Dec 6, 2013 at 10:55 AM, William Hermans  wrote:

> optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>
>
>
>
> On Fri, Dec 6, 2013 at 10:48 AM, David Lambert  wrote:
>
>> On 12/05/2013 03:53 PM, Robert Nelson wrote:
>>
>>> Well, the best option is to write a patch against:
>>> https://github.com/beagleboard/kernel/tree/3.8
>>> and then i'll merge it into both tree's and push out a new
>>> debian/ubuntu kernel build. .;)  So everyone get's the patch and
>>> supports your new cape out of the box...
>>>
>>> Regards,
>>>
>>>  Well I got my module and dtb to compile and install cleanly, but I am
>> now confused by the uEnv.txt. It appears to be much more complex than the
>> one I used for Angstrom (attached). I would like to disable the HDMI
>> virtual cape and enable mine. Is there a wiki that explains how to do this
>> with Debian?
>>
>> Regards,
>>
>> Dave.
>>
>> --
>> 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/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[William Hermans]

optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN




On Fri, Dec 6, 2013 at 10:48 AM, David Lambert  wrote:

> On 12/05/2013 03:53 PM, Robert Nelson wrote:
>
>> Well, the best option is to write a patch against:
>> https://github.com/beagleboard/kernel/tree/3.8
>> and then i'll merge it into both tree's and push out a new
>> debian/ubuntu kernel build. .;)  So everyone get's the patch and
>> supports your new cape out of the box...
>>
>> Regards,
>>
>>  Well I got my module and dtb to compile and install cleanly, but I am
> now confused by the uEnv.txt. It appears to be much more complex than the
> one I used for Angstrom (attached). I would like to disable the HDMI
> virtual cape and enable mine. Is there a wiki that explains how to do this
> with Debian?
>
> Regards,
>
> Dave.
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

On 12/05/2013 03:53 PM, Robert Nelson wrote:

Well, the best option is to write a patch against:
https://github.com/beagleboard/kernel/tree/3.8
and then i'll merge it into both tree's and push out a new
debian/ubuntu kernel build. .;)  So everyone get's the patch and
supports your new cape out of the box...

Regards,

Well I got my module and dtb to compile and install cleanly, but I am 
now confused by the uEnv.txt. It appears to be much more complex than 
the one I used for Angstrom (attached). I would like to disable the HDMI 
virtual cape and enable mine. Is there a wiki that explains how to do 
this with Debian?


Regards,

Dave.

--
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/groups/opt_out.
optargs=run_hardware_tests \
capemgr.disable_partno=BB-BONELT-HDMIN,BB-BONELT-HDMI \
capemgr.enable_partno=argus-ups

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

Thanks Robert. I must admit I am much more comfortable with that 
approach, than with bitbake/Angstrom recipes.


Dave.


On 12/05/2013 03:53 PM, Robert Nelson wrote:

On Thu, Dec 5, 2013 at 3:48 PM, David Lambert  wrote:

On 12/05/2013 03:37 PM, Robert Nelson wrote:

On Thu, Dec 5, 2013 at 3:33 PM, David Lambert  wrote:

Mainly due to some frustrations around opencv Python support in Angstrom,
I
am investigating switching to the Debian distribution. I have followed
Robert Nelson's excellent tutorials and scripts, but need some guidance
in
adding my own kernel modules and device trees. I have already
successfully
built them under Angstrom/bitbake, but cannot determine the preferred or
"correct" workflow for Debian. Any help would be greatly appreciated.

Hi Dave,

What kernel modules/device tree's do you need enabled?

Thanks for your quick reply.
These are modules/dts that I have written to support a UPS/watchdog cape I
am developing. They are building and working fine with the 3.8 Angstrom
kernel using the attached bitbake recipe. My question is what are the
magical incantations I need to build these outside the kernel tree? I
suspect there is a "correct" way to do this under Debian, rather than me
re-inventing a wheel.

Well, the best option is to write a patch against:
https://github.com/beagleboard/kernel/tree/3.8
and then i'll merge it into both tree's and push out a new
debian/ubuntu kernel build. .;)  So everyone get's the patch and
supports your new cape out of the box...

Regards,



--
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/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[Robert Nelson]

On Thu, Dec 5, 2013 at 3:48 PM, David Lambert  wrote:
> On 12/05/2013 03:37 PM, Robert Nelson wrote:
>>
>> On Thu, Dec 5, 2013 at 3:33 PM, David Lambert  wrote:
>>>
>>> Mainly due to some frustrations around opencv Python support in Angstrom,
>>> I
>>> am investigating switching to the Debian distribution. I have followed
>>> Robert Nelson's excellent tutorials and scripts, but need some guidance
>>> in
>>> adding my own kernel modules and device trees. I have already
>>> successfully
>>> built them under Angstrom/bitbake, but cannot determine the preferred or
>>> "correct" workflow for Debian. Any help would be greatly appreciated.
>>
>> Hi Dave,
>>
>> What kernel modules/device tree's do you need enabled?
>
> Thanks for your quick reply.
> These are modules/dts that I have written to support a UPS/watchdog cape I
> am developing. They are building and working fine with the 3.8 Angstrom
> kernel using the attached bitbake recipe. My question is what are the
> magical incantations I need to build these outside the kernel tree? I
> suspect there is a "correct" way to do this under Debian, rather than me
> re-inventing a wheel.

Well, the best option is to write a patch against:
https://github.com/beagleboard/kernel/tree/3.8
and then i'll merge it into both tree's and push out a new
debian/ubuntu kernel build. .;)  So everyone get's the patch and
supports your new cape out of the box...

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[David Lambert]

On 12/05/2013 03:37 PM, Robert Nelson wrote:

On Thu, Dec 5, 2013 at 3:33 PM, David Lambert  wrote:

Mainly due to some frustrations around opencv Python support in Angstrom, I
am investigating switching to the Debian distribution. I have followed
Robert Nelson's excellent tutorials and scripts, but need some guidance in
adding my own kernel modules and device trees. I have already successfully
built them under Angstrom/bitbake, but cannot determine the preferred or
"correct" workflow for Debian. Any help would be greatly appreciated.

Hi Dave,

What kernel modules/device tree's do you need enabled?

Thanks for your quick reply.
These are modules/dts that I have written to support a UPS/watchdog cape 
I am developing. They are building and working fine with the 3.8 
Angstrom kernel using the attached bitbake recipe. My question is what 
are the magical incantations I need to build these outside the kernel 
tree? I suspect there is a "correct" way to do this under Debian, rather 
than me re-inventing a wheel.


Regards,

Dave.



For the bone, the kernel script can be found here: (it's 99% source
identical to angstrom's 3.8 tree)
https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8

Regards,



--
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/groups/opt_out.
DESCRIPTION = "UPS control kernel module"
HOMEPAGE = "http://breakawaysystems.com";
SECTION = "kernel/modules"
PRIORITY = "optional"
LICENSE = "none"
#RDEPENDS = "kernel (${KERNEL_VERSION})"
DEPENDS = "virtual/kernel"
PR = "r40"

DTC = "${STAGING_KERNEL_DIR}/scripts/dtc/dtc"

LICENSE = "MIT"

LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"


SRC_URI = " \
file://argus-ups.c \
file://Makefile \
file://argus-ups-00A0.dts \
"

S = "${WORKDIR}"

inherit module


do_compile () {
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS CC LD CPP
oe_runmake 
'MODPATH="${D}${base_libdir}/modules/${KERNEL_VERSION}/kernel/drivers/misc/"' \
'KERNEL_SOURCE="${STAGING_KERNEL_DIR}"' \
'KDIR="${STAGING_KERNEL_DIR}"' \
'KERNEL_VERSION="${KERNEL_VERSION}"' \
'CC="${KERNEL_CC}"' \
'LD="${KERNEL_LD}"'
${DTC} -O dtb -o argus-ups-00A0.dtbo -b 0 -@ argus-ups-00A0.dts
}

do_install () {
install -d 
${D}${base_libdir}/modules/${KERNEL_VERSION}/kernel/drivers/misc
install -m 0644 ${S}/argus-ups*${KERNEL_OBJECT_SUFFIX} \
${D}${base_libdir}/modules/${KERNEL_VERSION}/kernel/drivers/misc
install -d ${D}${base_libdir}/firmware/
install -m 0755 ${S}/argus-ups-00A0.dtbo ${D}${base_libdir}/firmware/
}

FILES_${PN} += "/lib/firmware/"

Re: [beagleboard] Switching from Angstrom to Debian for the BBB

[Robert Nelson]

On Thu, Dec 5, 2013 at 3:33 PM, David Lambert  wrote:
> Mainly due to some frustrations around opencv Python support in Angstrom, I
> am investigating switching to the Debian distribution. I have followed
> Robert Nelson's excellent tutorials and scripts, but need some guidance in
> adding my own kernel modules and device trees. I have already successfully
> built them under Angstrom/bitbake, but cannot determine the preferred or
> "correct" workflow for Debian. Any help would be greatly appreciated.

Hi Dave,

What kernel modules/device tree's do you need enabled?

For the bone, the kernel script can be found here: (it's 99% source
identical to angstrom's 3.8 tree)
https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.