Re: [beagleboard] kernel updates: 4.1.12-ti-r27 (BBB all spi/spidev users rejoice)

['Andreas Müller' via BeagleBoard]

On Thu, Nov 5, 2015 at 3:47 PM, Robert Nelson  wrote:
> The journey into spi & dma..
>
> So for awhile now, we've had a bug for spi users, where the system
> would hardlock at the "160" byte threashold:
>
> debian@beaglebone:~$ sudo dd if=/dev/zero of=/dev/spidev1.0 bs=159 count=1
> 1+0 records in
> 1+0 records out
> 159 bytes (159 B) copied, 0.000508833 s, 312 kB/s
> debian@beaglebone:/sys$ dd if=/dev/zero of=/dev/spidev1.0 bs=160 count=1
> ^C
>
> (hangs..)
>
> "160" happens to be a the magic number where DMA takes over from PIO mode...
>
> Well as of yesterday:
>
> debian@beaglebone:~$ sudo dd if=/dev/zero of=/dev/spidev1.0 bs=320 count=1
> 1+0 records in
> 1+0 records out
> 320 bytes (320 B) copied, 0.00266366 s, 120 kB/s
>
> So here's the deal, it looks to be a spi/overlay bug, as we don't seem
> to get the correct dma tx/rx channels..
>
> What interesting, when the "spi" node is enabled in the main dtb:
>
> https://github.com/RobertCNelson/dtb-rebuilder/blob/4.1-ti/src/arm/am335x-boneblack-spi0.dts#L120-L137
>
> it works fine in dma mode...
>
> So with "4.1.12-ti-r27" spi-dma is now disabled..
>
> *btw:
>
> Late last night i wrote a better fix (will be r28)
>
> where you can disable "spi-dma" via the dt option:
>
> ti,pio-mode;
>
> https://github.com/beagleboard/bb.org-overlays/commit/48d33d4d22f284103db83626b343724cf18c578d
>
> Regards,
>
It is very long time ago, but now I am running into performance issues
with SPI. I see the DMA is still disabled in current bb.org-overlays.
So is the bug for blocks > 160 still there (what about kernel 4.4.x?)

Thanks in advance

Andreas

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALbNGRSqXpYEd1p2bMKngZKZz-mGZOshv%3D3Os1WcdscvAh5dtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Set GPIO in a precisely time using usleep()

[andreas . bunte]

Thanks all for the response.
It is right, I try to generate a PWM, because all hardware PWMs are 
occupied.

I will check the PREEMPT RT kernel.

-- 
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.

[beagleboard] Set GPIO in a precisely time using usleep()

[andreas . bunte]

Hi,

I am trying to control a servo with my BeagleBoneBlack using Angstrom. I 
must have a high-level on a GPIO for 1 millisecond. I use the following 
simple code:

while(1){
servo.setValue(BlackLib::low);
usleep(19000);
servo.setValue(BlackLib::high);
usleep(1000);
}

The GPIO is high for about 1.5 Milliseconds. The usleep()-function is not 
linear, so it did not work with any other value e.g. usleep(500). Sometimes 
I decrease the value by one (1 microsecond) but the time decrease by 100 
microseconds.
Has anybody an idea what could be wrong? 

-- 
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.

[beagleboard] Questions regarding bbone environment

['Andreas Müller' via BeagleBoard]

Hi,

as mentioned previously I am preparing a simple yocto layer for
beaglebone. I did not find any hints in the github repos
(image-builder?)  so far so maybe someone can help me here:

* Where does the default uEnv.txt come from - of where can I 'steal' it
* Currently I can set dt-overlays only with mounted rootfs. I think to
make kernel params working I need some initrd containing the dtbo
files - a pointer would be appreciated.

Andreas

-- 
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.

Re: [beagleboard] Understanding the whole Yocto/Linux stack for the BB

['Andreas Müller' via BeagleBoard]

On Tue, Nov 3, 2015 at 7:04 PM, Robert Nelson  wrote:
>> Is there a more stable source available (probably in near future)?
>
> The "4.1" branch get's rebased every thursday...  The git tag's
> "4.1.12-ti-r26" will never be modified after they are pushed..
>
Hmm I am not sure if bitbake's git fetcher can get a commit not
belonging to a branch. If not I'll create a mirror so I'll update
sources and recipe at the same time. Whatever I have more information
than before :)

Andreas

-- 
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.

Re: [beagleboard] Understanding the whole Yocto/Linux stack for the BB

['Andreas Müller' via BeagleBoard]

On Tue, Nov 3, 2015 at 6:05 PM, Robert Nelson  wrote:
> On Tue, Nov 3, 2015 at 10:57 AM, 'Andreas Müller' via BeagleBoard
>  wrote:
>> On Tue, Nov 3, 2015 at 4:56 PM, Baptiste  wrote:
>>> Hello,
>>>
>>>
>>>
>>> I’m using a BeagleBone as a base to develop a custom board. I’ve read pages
>>> and pages of doc and I feel I need some highlights to make sense of it all.
>>> Note that I’m mainly trying to understand the custom Linux distribution
>>> workflow at the lowest level here, for instance to be able to recreate from
>>> scratch the OE BeagleBoard stack… and I’m confused by all the available
>>> resources.
>>>
>>>
>>> So, here is my question spree to shed some light on these matters, not
>>> necessarily specific to the BeagleBone but it's a great platform to
>>> understand it all. Feel free to contribute even if you don’t have all the
>>> answers.
>>>
>>>
>>> I don’t understand why is the meta-beagleboard layer that huge. First, why
>>> is it using the kernel 3.8 where the meta-ti layer supports 4.1? (is
>>> meta-beagleboard depending on meta-ti in the first place, and if not, why?
>>> There are references to the BB in the meta-ti tree, why is an other layer
>>> even needed?) What's the difference with the layer meta-bbb?
>>>
>>> Then, why is recipes-kernel so full of all kind of patches? Where do those
>>> come from, why does the kernel need so much patching? Then, if those patches
>>> are here to “fix” the mainline kernel for the BB, what is exactly the
>>> RobertCNelson/bb-kernel repo? And the beagleboard/linux repo? What’s the
>>> relationship between all those projects?
>>>
>>>
>>> Also, I’ve read the DeviceTree story, but it seems that the actual
>>> BeagleBone DTS is in the kernel
>>> (arch/arm/boot/dts/am335x-bone-common.dtsi)... yet I thought the whole point
>>> of the DTS transition was not to add all ARM board files to the kernel.
>>> Moreover, many mach-omap2/ and DTS files are patched in bb-kernel and in
>>> meta-beagleboard... is it just because they’ve not been merged back to
>>> mainline yet?
>>>
>>> When it comes to customizing the DTS, I’ve seen for instance a reference to
>>> https://github.com/bradfa/beaglebone_pinmux_tables/blob/master/beaglebone_pins_p8
>>> or https://github.com/jadonk/bonescript/blob/master/src/bone.js to find out
>>> the actual pin numbers. How are these files have even been generated?
>>>
>>>
>>> I know I am mixing up different concepts here but they all coexist in the
>>> different docs… so I thought I’d give it a try here. Some resources clearing
>>> that up would be great too.
>>>
>>>
>>> Thank you for any clue that’ll help me to see through this forest!
>>> Baptiste
>>>
>> FWIW: For the reason other meta's seem to me either unmaintained for
>> long time or bloated or both, I created another very simple layer [1]
>> with current beagleboard.org kernel and dt.overlays. No meta-ti
>> dependency / only sw-rendered mesa - works just fine for me.
>>
>> [1] https://github.com/schnitzeltony/meta-bbone
>
> And i probally break it weekly:
Yes I noticed that already when building on different machines trying
to checkout non existent commits. Up to now I thought that happened by
accident.

>
> https://github.com/schnitzeltony/meta-bbone/blob/master/recipes-kernel/linux/linux-bbone_4.1.bb#L12
>
> I never got it working 100%, but you should be able to use the git tag's

As far as I can remember: tags in yocto SRC_URI are causing trouble -
something like a broken or weak network connection causes recipe
parsing to fail - even when building for another machine.

>
> https://github.com/RobertCNelson/meta-beagleboard-kernel/blob/master/recipes-kernel/linux/linux-beagleboard.org_4.1.bb#L46-L58

Wow - so many people doing the same thing - what a waste of resources.
My excuse: We have many different machines to build images for and use
yocto for very long time. Now I was forced to get something to work on
bbb...
>
> So it'll break less often..
>
Is there a more stable source available (probably in near future)?

Andreas

-- 
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.

Re: [beagleboard] Understanding the whole Yocto/Linux stack for the BB

['Andreas Müller' via BeagleBoard]

On Tue, Nov 3, 2015 at 4:56 PM, Baptiste  wrote:
> Hello,
>
>
>
> I’m using a BeagleBone as a base to develop a custom board. I’ve read pages
> and pages of doc and I feel I need some highlights to make sense of it all.
> Note that I’m mainly trying to understand the custom Linux distribution
> workflow at the lowest level here, for instance to be able to recreate from
> scratch the OE BeagleBoard stack… and I’m confused by all the available
> resources.
>
>
> So, here is my question spree to shed some light on these matters, not
> necessarily specific to the BeagleBone but it's a great platform to
> understand it all. Feel free to contribute even if you don’t have all the
> answers.
>
>
> I don’t understand why is the meta-beagleboard layer that huge. First, why
> is it using the kernel 3.8 where the meta-ti layer supports 4.1? (is
> meta-beagleboard depending on meta-ti in the first place, and if not, why?
> There are references to the BB in the meta-ti tree, why is an other layer
> even needed?) What's the difference with the layer meta-bbb?
>
> Then, why is recipes-kernel so full of all kind of patches? Where do those
> come from, why does the kernel need so much patching? Then, if those patches
> are here to “fix” the mainline kernel for the BB, what is exactly the
> RobertCNelson/bb-kernel repo? And the beagleboard/linux repo? What’s the
> relationship between all those projects?
>
>
> Also, I’ve read the DeviceTree story, but it seems that the actual
> BeagleBone DTS is in the kernel
> (arch/arm/boot/dts/am335x-bone-common.dtsi)... yet I thought the whole point
> of the DTS transition was not to add all ARM board files to the kernel.
> Moreover, many mach-omap2/ and DTS files are patched in bb-kernel and in
> meta-beagleboard... is it just because they’ve not been merged back to
> mainline yet?
>
> When it comes to customizing the DTS, I’ve seen for instance a reference to
> https://github.com/bradfa/beaglebone_pinmux_tables/blob/master/beaglebone_pins_p8
> or https://github.com/jadonk/bonescript/blob/master/src/bone.js to find out
> the actual pin numbers. How are these files have even been generated?
>
>
> I know I am mixing up different concepts here but they all coexist in the
> different docs… so I thought I’d give it a try here. Some resources clearing
> that up would be great too.
>
>
> Thank you for any clue that’ll help me to see through this forest!
> Baptiste
>
FWIW: For the reason other meta's seem to me either unmaintained for
long time or bloated or both, I created another very simple layer [1]
with current beagleboard.org kernel and dt.overlays. No meta-ti
dependency / only sw-rendered mesa - works just fine for me.

[1] https://github.com/schnitzeltony/meta-bbone

Andreas

-- 
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.

Re: [beagleboard] Kernel 4.1.9 overlays not working

['Andreas Müller' via BeagleBoard]

On Mon, Oct 12, 2015 at 11:51 AM, Bremenpl  wrote:
> I used dtc in version 1.4.0 i believe.
>
>
> --
> 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.
To make overlays build properly, you need a special version of dtc
found at [1] further details see [2]

[1] https://github.com/pantoniou/dtc
[2] https://github.com/beagleboard/bb.org-overlays

Andreas

-- 
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.

Re: [beagleboard] Kernel 4.1.9 overlays not working

['Andreas Müller' via BeagleBoard]

On Mon, Oct 12, 2015 at 11:01 AM, bremenpl  wrote:
> Hello there,
> I have installed latest console version of Debian from eLinux.org. Its uses
> kernel version 4.1.9:
> Linux beaglebone 4.1.9-ti-r20 #1 SMP PREEMPT Fri Oct 2 05:35:56 UTC 2015
> armv7l GNU/Linux
>
> I was trying to load BB-UART5 overlay but I failed. I also dont see any
> overlays loaded I thought I would, like eMMC:
> root@beaglebone:/sys/devices/platform/bone_capemgr# cat slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>
> When I tried to load the tree i got:
> [ 3013.532495] bone_capemgr bone_capemgr: part_number 'BB-UART5', version
> 'N/A'
> [ 3013.532543] bone_capemgr bone_capemgr: slot #4: override
> [ 3013.532561] bone_capemgr bone_capemgr: Using override eeprom data at slot
> 4
> [ 3013.532579] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,BB-UART5'
> [ 3013.533110] __of_adjust_tree_phandle_references: Could not find target
> property 'fixup' @/__local_fixups__
> [ 3013.548518] bone_capemgr bone_capemgr: slot #4: Failed to resolve tree
>
> And I have compiled the tds before and put the dtbo in /lib/firmware/
>
> Has anything changed in the new kernel regarding dts loading and general
> usage?
> I would apreciate all help regarding this topic!
>
> --
Am not sure: Did you compile dts with the patched version of dtc?

Andreas

-- 
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.

[beagleboard] Location of devicetree overlays

['Andreas Müller' via BeagleBoard]

Hi,

I started create a small board support layer [1] for yocto (aka
angstrom) because we use yocto/angstrom for all our boards and the
available beagle bsp is loveless or unmaintained. So far images are
working very nice with kernel 4.1 (beagleboard/rnelson source).

Now my question: At what folder does kernel expect the devicetree
overlays (*.dtb)?

[1] https://github.com/schnitzeltony/meta-bbone

Andreas

-- 
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.

Re: [beagleboard] Re: libpruio (fast and easy D/A - I/O)

[andreas . vogelfrei]

[SOLVED]

Hello TJF,

I will answer in English to give other users the possibility to use this 
information as well.

Thank you for your answer. With this information I was able to compile the 
supplied libpruio FreeBASIC examples.

Steps to take (on the BeagleBone, as root, otherwise use 'sudo'):

1.) wget 
http://www.freebasic-portal.de/dlfiles/625/freebasic_1.01.0debian7_armhf.deb 
2.) dpkg --install freebasic_1.01.0debian7_armhf.deb 
(Note: On 
http://www.freebasic-portal.de/downloads/fb-on-arm/debian-package-fbc-1-01-357.html
 
  you type: freebasic_1.01.0~debian7_armhf.deb which make copy 
and paste from the website resulting in an error)
3.) apt-get -f install
4.) rm /usr/local/bin/fbc
5.) reboot
6.) cp -R /usr/local/include/freebasic/BBB /usr/include/freebasic/

After this, compiling fbc -w all analyse.bas works.

Thank you.


>

-- 
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.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[andreas . vogelfrei]

Am Freitag, 14. November 2014 15:19:01 UTC+1 schrieb TJF:
>
> But I recommend to install the new BBB_fbc-1.00, which I also use on my 
> board now. Just follow the instructions in (only point 1)
>
>
> http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/_cha_preparation.html#SecInstallation
>

Hello TJF,

thanks for librpuio and the effort you spent for this.

I followed the instructions on the side above, but still can not compile 
the FB examples:

- I run a BBB with a very new Debian Linux image.
- I installed everything according the documentation on the above link.
- fbc is working:
 fbc -version
 FreeBASIC Compiler - Version 1.01.0 (10-14-2014), built for linux-arm 
(32bit) Copyright (C) 2004-2014 The FreeBASIC development team.

However, compiling an FB example yields:
libpruio-0.2/src/examples# fbc -w all analyse.bas
/usr/local/include/freebasic/BBB/prussdrv.bi(56) error 23: File not found, 
"crt/sys/types.bi" in '#INCLUDE ONCE "crt/sys/types.bi" '__HEADERS__: 
sys/types.h'

- I have searched my system manually for "types.bi", but there is none.

Do you have any suggestions what might be missing to compile the libpruio 
FB examples?
Btw. The C-examples can be compiled without errors.

Thanks.

 

-- 
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.

[beagleboard] Right way to use MT9P031 camera on BeagleBoard xM Rev C on Debian

[Andreas Weber]

Dear users,

I have a BeagleBoard-xM Rev C with LI-5M03CS camera module from Leopard 
Imaging with Aptina mt9p031 sensor.

What is the correct way to get this constellation running?
I know http://elinux.org/BeagleBoardDebian but it looks like the mt9p031 
doesn't work with 3.17.x kernel yet.

TIA, Andy

-- 
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.

[beagleboard] gpio works in system but not in hardware

[andreas . christ]

Hi,

i test with selfcompiled kernels (3.16.5 and 3.18.0).
I can export gpio-pins and can set/unset the values for direction and value 
in the /sys/class/gpio.
But on the beagleboard no pin change his state.
I.e. i will change the pin 9 on the P8-plug then i use the follow commands 
in the gpio-directory
echo 136 > export
echo out > ./gpio136/direction
echo 1 > ./gpio136/value

With 
cat ./gpio136/value
it returns the value 1. Thats ok. But the pin on the board to stay at 
low-level.

The board works fine with a prebuild linux-installation i.e. ubuntu.

Bye Andreas

-- 
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.

Re: [beagleboard] Replace u-boot only possible?

[andreas . christ]

Hi Robert,

Thank you!
This works perfect for me.

Regards
Andreas

-- 
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.

[beagleboard] Re: [PATCH POST V2] ARM: dts: Add am57xx-beagle-x15

[Andreas Färber]

Hi,

Am 07.11.2014 um 18:47 schrieb Nishanth Menon:
> BeagleBoard-X15 is the next generation Open Source Hardware
> BeagleBoard based on TI's AM5728 SoC featuring dual core 1.5GHz A15
> processor. The platform features 2GB DDR3L (w/dual 32bit busses),
> eSATA, 3 USB3.0 ports, integrated HDMI (1920x1080@60), separate LCD
> port, video In port, 4GB eMMC, uSD, Analog audio in/out, dual 1G
> Ethernet.
> 
> For more information, refer to:
> BeagleBoard-X15 Wiki:
> http://www.elinux.org/Beagleboard:BeagleBoard-X15

That page is very empty... is it the correct URL?

Regards,
Andreas

-- 
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg

-- 
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.

[beagleboard] Replace u-boot only possible?

[andreas . christ]

Hi,

i install arm-debian on a sd-card and this works initialy fine.
But i must change the mapping of the GPIOs and i rebuild the u-boot.
I replace the files MLO and u-boot.img with the new ones on the sd-card.
On reboot i see this:
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Checking for: /uEnv.txt ...
reading /uEnv.txt
987 bytes read in 4 ms (240.2 KiB/s)
Loaded environment from /uEnv.txt
Checking if uenvcmd is set ...
Checking for: /boot/uEnv.txt ...
** Invalid partition 2 **
** Invalid partition 3 **
** Invalid partition 4 **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
** Invalid partition 7 **
U-Boot#

The partitions:
sda1:fat16
sda5:ext4
sda6:swap

My intension was to change the u-boot without a new kernel. Is this 
possible?

Here my uEnv.txt
kernel_file=zImage
initrd_file=initrd.img
console=ttyO2,115200n8
mmcroot=/dev/mmcblk0p5 ro
mmcrootfstype=ext4 rootwait fixrtc
xyz_load_image=fatload mmc 0:1 0x8030 ${kernel_file}
xyz_load_initrd=fatload mmc 0:1 0x8160 ${initrd_file}; setenv 
initrd_size ${filesize}
xyz_load_dtb=fatload mmc 0:1 0x815f /dtbs/${dtb_file}
xyz_mmcboot=run xyz_load_image; run xyz_load_initrd; echo Booting from mmc 
...
video_args=setenv video vram=${vram} 
omapfb.mode=${defaultdisplay}:${dvimode} omapdss.def_disp=${defaultdisplay}
device_args=run video_args; run expansion_args; run mmcargs
mmcargs=setenv bootargs console=${console} ${optargs} ${video} 
root=${mmcroot} rootfstype=${mmcrootfstype} ${expansion}
optargs=console=tty0
expansion_args=setenv expansion buddy=${buddy} buddy2=${buddy2}
loaduimage=run xyz_mmcboot; run device_args; bootz 0x8030 
0x8160:${initrd_size}

Bye
Andreas

-- 
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.

Re: [beagleboard] Re: BBB Weston + sgx + ti-omap3-sgx-wayland-wsegl + HDMI: display wrapping issue

[Andreas Müller]

On Wed, Jul 30, 2014 at 12:13 AM, Cody P Schafer  wrote:
> After I posted this I realized that while I was building the drm-gbm
> branch, weston was using the fbdev backend, and thus not passing
> anything through the accelerated part :(
Aargh - and I hoped you could inspire me :)

FWIW: fbdev backend should work (more or less) with --use-gl (this
option is not mentioned in weston --help) and master branch

Andreas

-- 
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.

[beagleboard] Re: BBB Weston + sgx + ti-omap3-sgx-wayland-wsegl + HDMI: display wrapping issue

[Andreas Müller]

On Tuesday, July 1, 2014 10:30:58 PM UTC+2, Cody P Schafer wrote:
>
> Hi all,
>
> I've put together a yocto build for the BBB which uses weston+wayland 
> driven by the sgx kernel modules.
>
> I'm using this as a wrapper around libEGL: 
> https://github.com/schnitzeltony/ti-omap3-sgx-wayland-wsegl/tree/drm-gbm
> And I'm using some bit bake hackery based on: 
> http://gitorious.org/schnitzeltony-oe-meta/meta-gumstix-community
> I'm running ti's 3.12 staging kernel with the 5.01.01.01 GFX release.
>

Sorry to hijack this: You got drm-gbm branch to work? Which backend are you 
using?

Andreas (schnitzeltony)

-- 
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.

[beagleboard] Device Tree Overlays

[andreas . b24]

Hello,

I like to develop a new cape for Beaglebone Black and tried to create a 
Device Tree Overlay for it.

I found a table for the pin definitions. A part of the table is this:



Head_pin  $PINS  ADDR/OFFSET  Name GPIO NO.  Mode7

P9_11   28   0x870/070  UART4_RXD   30 gpio0[30]
P9_12   30   0x878/078  GPIO1_28  60 
gpio1[28]
P9_13   29   0x874/074  UART4_TXD31gpio0[31]
P9_14   18   0x848/048 EHRPWM1A50gpio1[18]
P9_15   16   0x840/040  GPIO1_16   48   
 gpio1[16]



With this information I created the following device tree overlay:


/*
 * This is a template-generated file from BoneScript
 */

/dts-v1/;
/plugin/;

/{
compatible = "ti,beaglebone", "ti,beaglebone-black";
part_number = "test";

exclusive-use =
"P9.11", /* gpio0.30, Pin  30 */
"P9.13", /* gpio0.31, Pin  31 */
"gpio0_30",
"gpio0_31",
"pru0";

fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
foo_pins: foo_pins {
pinctrl-single,pins = <
0x078 0x3F
0x07c 0x3F
>;
};
};
};

fragment@1 {
target = <&pruss>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&foo_pins>;
};
};
};


To my surprise I had to use the GPIO Numbers 30 and 31 together with the 
offsets 0x078 and 0x07c to make the GPIO pins P9_11 and P9_13 work as 
inputs with pullups.
I would have expected, that I have to use the software pins 28 and 29 for 
the inputs P9_11 and P9_13.

But it would be ok, if it would work for all unused pins of the Beaglebone 
Black. The problem is, that it doesn´t work for many pins. For example when 
I try to use the input P9_15 with the GPIO number 48 and the corresponding 
offset: 48 * 4 = 192 = 0x0c0 the whole overlay does not load correctly. I 
think this is because $PIN 48 corresponds to P8_37 in the list which is 
used as a HDMI pin.

Why do I have to use GPIO NO instead of $PIN as I expected?
If I have to use GPIO NO instead of $PIN, then why does this work only for 
some pins and not for all?

Any help is appreciated. I am running out of ideas!

Andy

-- 
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.

Re: [beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

[Andreas Tauböck]

Well, neither of them works:

ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo su -c "echo TT3201:001 > slots"
[sudo] password for ubuntu:
bash: line 0: echo: write error: No such file or directory
ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo -S "echo TT3201:001 > slots"
sudo: echo TT3201:001 > slots: command not found
ubuntu@arm:/sys/devices/bone_capemgr.9$

Does someone know how to "disable the kernel config switch for building 
firmware inside the kernel" as Robert mentioned in a prior post to force 
the BBB to load the .dtbo from /lib/firmware?


Am Freitag, 25. April 2014 19:15:12 UTC+2 schrieb William Hermans:
>
> I think sudo -S  might work too, but have not tested this myself 
> yet.
>
>
> On Fri, Apr 25, 2014 at 4:51 AM, Charles Steinkuehler <
> cha...@steinkuehler.net > wrote:
>
>> On 4/25/2014 5:37 AM, Andreas Tauböck wrote:
>> >
>> > and I get a permission denied when i want to add it manually with:
>> >
>> > ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo echo TT3201:001 >slots
>> > -bash: slots: Permission denied
>>
>> The redirect happens before the sudo, try:
>>
>> sudo su -c "echo TT3201:001 > slots"
>>
>> --
>> Charles Steinkuehler
>> cha...@steinkuehler.net 
>>
>> --
>> 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...@googlegroups.com .
>> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Cape Device Tree Overlay fails to load during boot?

[Andreas Tauböck]

Hy,

I´m having a very similar problem. I am using the current version of ubuntu 
for BBB (Ubuntu 14.04 LTS (GNU/Linux 3.8.13-bone47 armv7l)) and tried to a 
device tree overlay with this guide for the exact same cape: 
http://the8thlayerof.net/2013/10/28/canbus-beagle-bone-black-as-a-canbus-data-logger-part-2/

However the dmesg output says the loading fails:

[2.011897] bone-capemgr bone_capemgr.9: loader: before slot-3 
TT3201-001:05 (prio 0)
[2.020116] bone-capemgr bone_capemgr.9: loader: check slot-3 
TT3201-001:05 (prio 0)
[2.042227] bone-capemgr bone_capemgr.9: loader: after slot-3 
TT3201-001:05 (prio 0)
[2.062825] bone-capemgr bone_capemgr.9: slot #3: Requesting part 
number/version based 'TT3201-001-05.dtbo
[2.093253] bone-capemgr bone_capemgr.9: slot #3: Requesting firmware 
'TT3201-001-05.dtbo' for board-name 'TT3201 CAN Bus Cape', version '05'
[2.901230] bone-capemgr bone_capemgr.9: failed to load firmware 
'TT3201-001-05.dtbo'
[2.909494] bone-capemgr bone_capemgr.9: loader: failed to load slot-3 
TT3201-001:05 (prio 0)

and I get a permission denied when i want to add it manually with:

ubuntu@arm:/sys/devices/bone_capemgr.9$ sudo echo TT3201:001 >slots
-bash: slots: Permission denied

There are plenty of people having this problem but i could not find a good 
solution yet as it should not happen in newer releases anymore.

I appreciate any help???

Am Freitag, 15. November 2013 11:50:05 UTC+1 schrieb Jesper We:
>
> OK, I have read this 
> threadtwice
>  now, and I still fail to see any real solution in between the 
> discussion of various patches. 
>
> There is a lot of discussion in that thread about custom kernels, but my 
> BB Black has the latest Angstrom eMMC flasher version with everything as 
> default.
>
> I have made a Cape PCB with an RTC and 4 serial ports for UART1,2,4,5. The 
> Cape has an EEPROM at i2c address 0x54 (Slot #0) with the proper part 
> number and revision.
> I have disabled the loading of all HDMI overlay features in uEnv.txt.
>
> On exactly the same board I can swap out my Cape for the Circuitco RS232 
> cape which I have a couple of. It has the .dto files already in 
> /lib/firmware in the distro.
> That DTO loads fine during boot, with the same priority (0) as my cape.
> So it's not an issue of the eMMC not being ready.
>
> However, the Circuitco Rs232 Capes are loaded earlier in the boot process 
> than the point at which my cape fails. Since my DTO is just a merge of the 
> original RS232 UARTs DTOs from the distro, I cannot understand why...
>
> So my questions are:
> - Why is the failure to load my cape coming much later in the boot process 
> than the Circuitco cape's success?
> - Is there any way to know why the boot time loading fails, when the cape 
> loads fine manually?
>
> See below fore some transcripts. The source for my DTO is enclosed.
>
> /jesper
>
>
> root@beaglebone:~# ls -l /lib/firmware/CP*
> -rw-r--r-- 1 root root 1969 Nov 14 19:15 /lib/firmware/CP-CLOUDSAFE-
> 00A0.dtbo
> -rwxr-xr-x 1 root root 2117 Nov 14 19:13 /lib/firmware/CP-CLOUDSAFE-
> 00A0.dts
>
> Loading the DTO manually works fine:
>
> root@beaglebone:/lib/firmware# echo CP-CLOUDSAFE 
> >/sys/devices/bone_capemgr.8/slots
> root@beaglebone:/lib/firmware# dmesg
> 
> [  200.937688] bone-capemgr bone_capemgr.8: part_number 
> 'CP-CLOUDSAFE',version 
> 'N/A'
> [  200.937766] bone-capemgr bone_capemgr.8: slot #7: generic override
> [  200.937786] bone-capemgr bone_capemgr.8: bone: Using override eeprom 
> data at slot 7
> [  200.937803] bone-capemgr bone_capemgr.8: slot #7: 'Override Board 
> Name,00A0,Override Manuf,CP-CLOUDSAFE'
> [  200.937896] bone-capemgr bone_capemgr.8: slot #7: Requesting part 
> number/version based 'CP-CLOUDSAFE-00A0.dtbo
> [  200.937915] bone-capemgr bone_capemgr.8: slot #7: Requesting firmware 
> 'CP-CLOUDSAFE-00A0.dtbo' for board-name 'Override Board Name', version 
> '00A0'
> [  200.947556] bone-capemgr bone_capemgr.8: slot #7: dtbo 
> 'CP-CLOUDSAFE-00A0.dtbo' loaded; converting to live tree
> [  200.947984] bone-capemgr bone_capemgr.8: slot #7: #5 overlays
> [  200.954890] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a 
> OMAP UART1
> [  200.958878] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a 
> OMAP UART2
> [  200.964739] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a 
> OMAP UART4
> [  200.970604] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a 
> OMAP UART5
> [  200.974945] bone-capemgr bone_capemgr.8: slot #7: Applied #5 overlays.
> 
> root@beaglebone:~# cat /sys/devices/bone_capemgr.8/slots
>  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,CP

[beagleboard] Re: CPU speed and kernel builds

[andreas . robert . berger]

Hi Will,

Am Samstag, 22. März 2014 09:33:53 UTC+1 schrieb cwrse...@gmail.com:
>
>
>
> On Saturday, March 22, 2014 7:51:28 AM UTC, robert.berger wrote:
>>
>> Hi,
>>
>> Did you try compile the cpupower tool [1] which comes with the kernel?
>>
>>
>>
> Yes, but the cpufreq directories under /sys just aren't there.  It has to 
> be a kernel config problem; could you please pastebin your 3.13 kernel 
> config somewhere, and I'll try building 3.14 against that.
>
> Will
>  
>

Have fun: http://pastebin.com/VZS4epai 

-- 
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.

[beagleboard] LI-5M03CS (Aptina MT9P031) on BB-xM Rev C

[Andreas Weber]

Dear users,

I'm trying to get the LI-5M03CS (Aptina MT9P031) on BB-xM Rev C
configuration running with Debian.

First I tried some newer kernels but the FDT based boot isn't fully
supported yet (or at least this is what I think after some reading)

Then I cloned the git://github.com/RobertCNelson/stable-kernel.git
build scripts, v3.9.x branch, selected MT9P031 in menuconfig and build
the kernel. Then I cherry-picked some patches from Laurent:

git remote add pinchartl git://linuxtv.org/pinchartl/media.git
git fetch pinchartl
git cherry-pick b54ece2d97c244416e3239f0a0d2a665fe1c152a
git cherry-pick bca60770d38a41bab4b69c93cbbe3d79c1443f80
git cherry-pick 58ee8629ebc528b629dac36e5e5c67dffeecd2fa

Then recompiled and installed the kernel on a SD Card which was
previously installed with RCNs debian netinstall.

After cloning, compiling and installing media-ctl and yavta im able to
get images with

sudo media-ctl -r -l '"mt9p031 2-0048":0->"OMAP3 ISP CCDC":0[1],
"OMAP3 ISP CCDC":2->"OMAP3 ISP preview":0[1], "OMAP3 ISP
preview":1->"OMAP3 ISP resizer":0[1], "OMAP3 ISP resizer":1->"OMAP3
ISP resizer output":0[1]'
sudo media-ctl -V '"mt9p031 2-0048":0 [SGRBG10 1280x1024], "OMAP3 ISP
CCDC":2 [SGRBG10 1280x1024], "OMAP3 ISP preview":1 [UYVY 1280x1024],
"OMAP3 ISP resizer":1 [UYVY 1024x768]'

/usr/sbin/yavta -f UYVY -s 1024x768 --capture=3
--file="$(pwd)/img#.uyvy" /dev/video6
gm mogrify -size 1024x768 -format jpg *.uyvy

but the first image is a "magnified" version of the following 2 images
(all 3 have 1024x768 Pixels)

After all this trial&error process I really wonder what would be the
best way to get this camera running on Debian. Is there a better
branch to clone from?

In the end I want to be able to get RAW bayer images from the sensor.

Thank in advance, Andy

-- 
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.

[beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support

[Andreas]

Password for login?

Den torsdagen den 30:e januari 2014 kl. 09:43:47 UTC skrev 
xris@googlemail.com:
>
> The previous file share expired. File can now be found at:
>
> http://www.fileswap.com/dl/pxPvW1nVwM/
>
>
> On Monday, January 27, 2014 10:28:06 PM UTC+1, crystal@gmail.comwrote:
>>
>> Excellent.  thanks.
>>
>> I'll give it a whirl tonight.
>>
>> On Thursday, January 23, 2014 12:12:25 PM UTC-6, 
>> xris@googlemail.comwrote:
>>>
>>> Hey guys,
>>>
>>> As promised. Ubuntu 12.04 BBB image for the Chipsee 7” 1024x600 LCD 
>>> touchscreen.
>>>
>>> Grab it here:
>>> http://www.fileswap.com/dl/sdFGPZoIw6/
>>>
>>> You should find yourself downloading 
>>> bbb-ubuntu-12.04-for-community.xz
>>>
>>> Just extract and write that to your SD card (4gb expected) with 
>>> something like:
>>>
>>> *cat bbb-ubuntu-12.04-for-community.xz | xz -d > /dev/sdX*
>>>
>>> Note it’s a raw sector dump NOT a tarball, so extract straight to your 
>>> SD card device. (eg.  /dev/sdx, NOT /dev/sdx1) 
>>>
>>> Also note this image doesn’t install or boot from MMC so make sure 
>>> you’ve got the SD card selected on the boot switch thing.
>>>
>>> Once the extract is complete, simply slap it into the BBB and boot.  It 
>>> should come up with the Chipsee splash screen but then
>>> boot into Ubuntu 12.04 after a while. 
>>>
>>> Hope this helps.
>>>
>>> l8r,
>>> Xris.
>>>
>>

-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Andreas Tauböck]

 I hava a similar problem, just it almost everytime does not boot. I have 
1.2A and nothing connected, just uSD card inserted. Also tried to flash the 
eMMC or boot from uSD, no success. And when it boots one of a hundret tries 
and i do not diconnect the power source an just reboot in shell, it is the 
same again.

Can anybody please help me?

Am Mittwoch, 31. Juli 2013 23:48:54 UTC+2 schrieb duckhunt...@gmail.com:
>
> Hi guys,
>
> we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
> Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
> The Beagle Bone is placed in a case and we have connected it to a DC power 
> supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
> in our power supply, the BeagleBone powers on (Power LED is on), but 
> nothing more happens (none of the other four LEDs is on). If we are now 
> removing the power supply and putting it in again, the BBB starts normally. 
> I guess the power supply is strong enough: 5A@5V.
>
> Thanks for your help in advance.
>
> Regards,
> duckhunter
>

-- 
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.

[beagleboard] dtc / meta-beagleboard

[Andreas Müller]

Hi,

ping on [1]

[1] https://github.com/beagleboard/meta-beagleboard/pull/17

Andreas

-- 
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.