[beagleboard] PTP Porting Bounty
I hope it is permissible to offer a bounty of $1,000-$2,000 for a GPL project (if completed by 2015-01-31). I would like the BBB to become a USB reference device for PTP. This means that I would like the normal low-level block-sector based file-system over USB that we are currently using to be replaced by a more mid-level file-id based system over USB that is used by android. fortunately, there is at least one ptp-gadget already in public existence, maintained by Michael Grzeschik, so my request is probably only a port with debugging, documentation, and posting requirements. the idea is for the BBB to become *the* reference implementation for a linux PTP stack, both on a host and on a device. when I looked, I learned that, although in wide use, most PTP/MTP implementations seem to be hacks that try to reverse-engineer the sins of others. that is, for example, even the linux host implementations are greatly concerned with making buggy legacy PTP/MTP devices work. in turn, some more modern devices do not seem to work with the standard low-level fuse-ptp linux hosts, even when they work well with gnome's gvfs. with a command-line interface, it should finally be possible to have solid tests of PTP/MTP communication protocol. something like # mount /dev/usb/... /mnt/ptp # mkdir /mnt/ptp/testme # perl checkptp.pl write /mnt/ptp/testfile 123 SUCCESS # perl checkptp.pl read /mnt/ptp/testfile 123 SUCCESS # perl checkptp.pl ls /mnt/ptp/testfile EXISTS # perl checkptp.pl read /mnt/ptp/nonexist FAIL # perl checkptp.pl rm /mnt/ptp/testfile SUCCESS # rmdir /mnt/ptp/testme # umount /mnt/ptp for my bounty, I only want the principal functions to be working (writefile, readfile, ls, rm, cd, mkdir, rmdir), but these I want to work rock-solid and fast (i.e., not just an over-serial-port emulation that maxes out at 115KBaud). it needs to work solidly with both gphotofs and gvfs. it needs to work if PTP is the only protocol communicating over the USB port between USB host desktop and USB gadget client BBB. it needs to be GPL'ed and public for everyone to use, hosted on git so that others (Robert Nelson?) can use it. This is not just a project for me. This project should also be of interest for others. Please drop me a private note (ivo.we...@gmail.com) if you are interested, and explain to me your expertise. I don't want multiple people to work on this. I would be particularly interested if this were done by someone who wanted to do it anyway, and maintain it for others after the project bounty is paid. /iaw -- 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: How can I use PRU by CCS Compiler?
เมื่อ วันจันทร์ที่ 8 ธันวาคม ค.ศ. 2014, 1 นาฬิกา 9 นาที 51 วินาที UTC+7, Peter Gregory เขียนว่า: Check out my post: PRU C Project - from device tree to program execution It gives notes for all the above questions Thank you Your suggestion was helpful for me. And now I have some problem with insert a device tree to slot file in /sys/devices/bone_capemgr.9 by cat slots command 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-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI it was not show after I insert echo myoverlay slots and I recheck by cat slots command again it's not show in list And it's show error like this -bash: echo: write error: File exists I think it tell me that has file in it already but it's not show -- 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] DVI cape .dts file for BeagleBone Black
Hello there, I am looking for a device tree overlay file for this cape: http://elinux.org/CircuitCo:BeagleBone_DVI-D_with_Audio I have found 3 dvi cape files here: https://github.com/beagleboard/linux/tree/3.8/firmware/capes But they are for standard BeagleBone and I was not abble to modify them to work with BeagleBone Black, I was receiving message: no such file or directory everytime i tried to echo the .dtbo file to slots... I would aprichiate all help. -- 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: DVI cape .dts file for BeagleBone Black
I have done another approach. I booted the BeagleBone Black from a standard debian image on a sd card. I turned off hdmi and emmc and turned on the BB-BONE-DVID-01 dts. Then when I booted, I could for a second see something on the screen, but it seemd like there is a sycing problem, as it was only some blurry like. When In the debug window i have seen: [ 26.468200] tilcdc 4830e000.fb: timeout waiting for framedone and the screen went black. Does anyone know what could be the case? W dniu poniedziałek, 8 grudnia 2014 12:31:13 UTC+1 użytkownik bremenpl napisał: Hello there, I am looking for a device tree overlay file for this cape: http://elinux.org/CircuitCo:BeagleBone_DVI-D_with_Audio I have found 3 dvi cape files here: https://github.com/beagleboard/linux/tree/3.8/firmware/capes But they are for standard BeagleBone and I was not abble to modify them to work with BeagleBone Black, I was receiving message: no such file or directory everytime i tried to echo the .dtbo file to slots... I would aprichiate all help. -- 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: How can I use PRU by CCS Compiler?
Try putting the device tree overlay file in /sys/firmware I made a mistake when I specified it go in /sys/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] How Device Tree Overlay Works
Hello All,
I am a newbie to Linux and trying to figure out how device tree overlay
works...
So after googling for many days, I came up with below device tree:
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = MY-LED;
version = 00A0;
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
P9.12,/* GPIO*/
/* the hardware ip uses */
gpio0;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
bb_mygpio_pins: pinmux_bb_mygpio_pins {
pinctrl-single,pins =
0x870 0x07/* output
mode | MODE7, see Pin_Configuration.pdf in BBB */
;
};
};
};
fragment@1 {
target = ocp;/* not sure why it is not gpio0 */
__overlay__ {
status = okay;
pinctrl-names = default;
pinctrl-0 = bb_mygpio_pins;
};
};
};
I was able to build the dtc and generated MY-LED-00A0.dtbo
I then copied the MY-LED-00A0.dtbo to /lib/firmware
Then i echoed it to slots:
echo MY-LED $SLOTS
and cat $SLOTS gives me below result:
root@beaglebone:/lib/firmware# cat $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
9: ff:P-O-L Override Board Name,00A0,Override Manuf,MY-LED
By looks of this, MY_LED seems to be loaded...
The main confusion is how can I use MY-LED?
Where are the files for MY-LED present?
Any help or guidance is much appreciated.
--
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: How can I use PRU by CCS Compiler?
I mean /lib/firmware -- 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] 2014-08-19 LXDE flasher image: broken web site
On Mon, Dec 8, 2014 at 12:23 AM, Gunjan Gupta viran...@gmail.com wrote: Hi Robert, I have built a customized debian image based on your latest imagebuilder script, and I am also facing this issue. Is it still broken? If yes, could you please tell the steps to get it working? bone101 master is still broken.. (master is built with jekyll) i just pushed a commit to use a pre master checkout (non-jekyll dependent) version that'll work: (it's a version of bone101 from mid summerish) https://github.com/RobertCNelson/omap-image-builder/commit/a61106b255bc7ae379981d13988c977671fa14b2 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/d/optout.
[beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support
Hello all, I am new to Beaglebone Black (making the jump from the arduino/chipkit world) and am having some difficulty with this Chipsee 7 capacitive cape. I feel I am banging my head against the wall over something simple, but could some one provide a walk through for just getting started with the display. I have the BBB working to an external display via HDMI, but am not able to get the lcd to work unless I use an existing .img. I am trying to use one of Chipsee's provided prebuilt images, but am having trouble. Chipsee's directions state to use: sudo su ./mksdcard.sh /dev/sdX (X in this instance is a after checking with fdisk -l) But I keep getting either no passwd for ./mksdcard.sh. If I drop the sudo su I get permission denied. Any help would be very much appreciated. 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.
Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.
Hi Alex, In past couple days, I went through the same path as you did. However, with my limited tests, I see improvement on 3.8.13-bone68. I have BBB Rev C from Element14 with a generic 5V 2.8A switch power supplier. - with 3.8.13-bone47 (the original image) power cycle 50 times, there were 2 phy not found - with 3.8.13-bone68 (prebuild image from http://rcn-ee.net/, power cycle 50 times, there were no phy not found I also tested 3.14.22-ti-r31, power cycle 50 time, and no phy not found. I'll do more test to see if the issue show up. In you tests, did you see any improvement in 3.8.13-bone67 vs earlier version ? Thanks KeOu -- 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: TI PRU Cape demos: tiobj2bin fails
Thanks for your rapid response Peter.
I understand now that trying to make a simple example from the PRU cape
demo using only PRU_LED0 is flawed because I then only have a _pru_ program
without the infrastructure on the arm8 to run it.
My reason for trying to use just the LED0 example was that when following
the PRU cape demo instructions I got the linking error:
*Linkingfatal error #10183: --abi=eabi is incompatible with file
C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_Audio/Debug/PRU_Audio_image.obj
(TIABI v0)*
(Full listing below.)
My aim, of course, was to get a working rebuild so that I could begin
developing my own tests.
You may be wondering whether I have actually run the provided PRU cape demo
MLO and app.
I haven't because when I bought the beaglebone black I didn't realise I
needed an FTDI serial cable AND a right angle header to be able to use the
TI PRU cape and run the pru cape demo.
If I could rebuild the demo then I could modify the demo to automatically
run one of the apps on bootup e.g. blinking LED0 so that I didn't need the
cable for testing :)
Any further help appreciated.
Bryan
---
*'Building target: PRU_Demo.out''Invoking: ARM
Linker'c:/ti/ccsv6/tools/compiler/arm_5.1.9/bin/armcl -mv7A8
--code_state=32 --abi=eabi -me -O2 --define=am3359 --display_error_number
--diag_warning=225 --diag_wrap=off -z -mPRU_Demo.map --heap_size=0x800
--stack_size=0x800 -ic:/ti/ccsv6/tools/compiler/arm_5.1.9/lib
-ic:/ti/ccsv6/tools/compiler/arm_5.1.9/include
-iC:/TI/AM335X_StarterWare_02_00_01_01/binary/armv7a/cgt_ccs/am335x/drivers/Release/
-iC:/TI/AM335X_StarterWare_02_00_01_01/binary/armv7a/cgt_ccs/utils/Release/
-iC:/TI/AM335X_StarterWare_02_00_01_01/binary/armv7a/cgt_ccs/am335x/beaglebone/platform/Release/
-iC:/TI/AM335X_StarterWare_02_00_01_01/binary/armv7a/cgt_ccs/am335x/system_config/Release/
--reread_libs --define=A8_CORE=1 --warn_sections --display_error_number
--diag_wrap=off --xml_link_info=PRU_Demo_linkInfo.xml --rom_model -o
PRU_Demo.out
C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_Audio/Debug/PRU_Audio_image.obj
C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_HDQ_TempSensor0/Debug/PRU_HDQ_TempSensor0_image.obj
C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_HDQ_TempSensor1/Debug/PRU_HDQ_TempSensor1_image.obj
C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_Hardware_UART/Debug/PRU_Hardware_UART_image.obj
C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_LED0/Debug/PRU_LED0_image.obj
C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_LED1/Debug/PRU_LED1_image.obj
C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_Switch/Debug/PRU_Switch_image.obj
./pru.obj ./pru_cape_demo.obj ../pru_cape_demo.cmd
-lrtsv7A8_A_le_eabi.lib -ldrivers.lib -lutils.lib -lsystem.lib
-lplatform.lib Linkingfatal error #10183: --abi=eabi is incompatible
with file
C:/ti/pru-software-support-package/pru_cape/pru_fw/PRU_Audio/Debug/PRU_Audio_image.obj
(TIABI v0) Compilation failuregmake: *** [PRU_Demo.out] Error 1gmake:
Target `all' not remade because of errors. Build Finished *
--
On Saturday, 6 December 2014 06:41:02 UTC+11, Peter Gregory wrote:
Try running hexpru with the following command options
-b
-image
ROMS {
PAGE 0:
text: o = 0x0, l = 0x1000, files={text.bin}
PAGE 1:
data: o = 0x0, l = 0x1000, files={data.bin}
}
--
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] Where is the MLO and u-boot.img
Yes, a lot of things on Linux looks like voodoo magic, and so many mysterious codes lying everywhere :) That said, can you point me to the place where I can learn how that was done, and the complete boot mechanism of the BBB? I am trying to learn the boot process(among other things) of the BBB but there are just so much info lying around, some are outdated and some are conflicting. Also does that mean I can no longer access or see these two files? Is there a place where I could download the source for the image? I read your instructions at: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSD/SDcard and saw that you have only made one partition on the SDcard with both the kernel and file system, and before you format the card you've dd'ed both the MLO and u-boot.img to it. Is this how that was done? And I thought that was a mistake, silly me :) I have learned a lot from what you have posted on the web, thank you for your work and I look forward to seeing more Products from you. Too bad there is not a centralized location where we can learn all these for the BBB. Best Regards, Ricky Chang -- 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] How to do a 4 Deep Callback in Bonescript/JS
I can only get two deep callback to work here is my function
function send(Callback) {
var Angle = document.getElementById(DampAngle).value;
var AtCmd6 = 0x4 ;
var AtCmd4 = 0x4 ;
var AtCmd3 = 0x4 ;
var AtCmd2 = 0x4 ;
if ((Angle 0x8) == 0x8) { // ANGL[3:0] = [D6, D4, D2, D1]
atCmd6 = 0x05;}//
else {
atCmd6 = 0x04;}//
if ((Angle 0x4) == 0x4) { // ANGL[3:0] = [D6, D4, D2, D1]
atCmd4 = 0x05;}//
else {
atCmd4 = 0x04;}//
if ((Angle 0x2) == 0x2) { // ANGL[3:0] = [D6, D4, D2, D1]
atCmd3 = 0x05;}//
else {
atCmd3 = 0x04;}//
if ((Angle 0x1) == 0x1) { // ANGL[3:0] = [D6, D4, D2, D1]
atCmd2 = 0x05;}//
else {
atCmd2 = 0x04;}//
sendCmd(damp1Addr, D6, atCmd6,
sendCmd(damp1Addr, D4, atCmd4,
sendCmd(damp1Addr, D3, atCmd3,
sendCmd(damp1Addr, D2, atCmd2
function Callback() {sendCmd(damp1Addr, AC, 0 );} //apply changes
}
It will only perform two of the sendCmd commands no matter how I structure
it. I want to do these function in this order but the next function can
not start until the last one is completed.
sendCmd(damp1Addr, D6, atCmd6);
sendCmd(damp1Addr, D4, atCmd4);
sendCmd(damp1Addr, D3, atCmd3);
sendCmd(damp1Addr, D2, atCmd2)
sendCmd(damp1Addr, AC, 0 );
every time I call the send function.
I went through a few tutorials and looked at many examples and although I
think I understand what callback is doing I do not understand how to
construct the code to do more than just two callbacks.
Can anyone help?
--
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: chipsee beaglebone lcd/dvi expansion kernel support
Hi; If I understand you correctly, you need to use either “su” or “sudo” but not both. If you enter: sudo . /mksdcard.sh /dev/sdX It will prompt you for a password. Just use the password that you used to login. Bill No one could make a greater mistake than he who did nothing because he could do only a little. All that is necessary for the triumph of evil is that good men do nothing Edmond Burke (1729 - 1797) http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] Sent: Sunday, December 07, 2014 4:00 PM To: beagleboard@googlegroups.com Cc: xris.ruo...@googlemail.com Subject: [beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support Hello all, I am new to Beaglebone Black (making the jump from the arduino/chipkit world) and am having some difficulty with this Chipsee 7 capacitive cape. I feel I am banging my head against the wall over something simple, but could some one provide a walk through for just getting started with the display. I have the BBB working to an external display via HDMI, but am not able to get the lcd to work unless I use an existing .img. I am trying to use one of Chipsee's provided prebuilt images, but am having trouble. Chipsee's directions state to use: sudo su ./mksdcard.sh /dev/sdX (X in this instance is a after checking with fdisk -l) But I keep getting either no passwd for ./mksdcard.sh. If I drop the sudo su I get permission denied. Any help would be very much appreciated. 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. _ No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5577 / Virus Database: 4235/8695 - Release Date: 12/07/14 -- 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: BB Black and SSD1289 with 3.8
Le lundi 8 décembre 2014 03:31:46 UTC+1, Peter Gregory a écrit : I was interested in getting this display working too. I found this message thread: http://www.cemetech.net/forum/viewtopic.php?t=7814postdays=0postorder=ascstart=0 Apparently is it possible to get it working. I didn't pursue it and went with a 4dcape-43t instead. Yes I saw this thread, but all links are dead and they aren't very explicit. The main problem, that I don't know where is my problem, if it's a DTO/kernel/Xorg/FB issue :( -- 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] Where is the MLO and u-boot.img
On Sat, Dec 6, 2014 at 1:24 AM, rickyc8...@gmail.com wrote: Yes, a lot of things on Linux looks like voodoo magic, and so many mysterious codes lying everywhere :) That said, can you point me to the place where I can learn how that was done, and the complete boot mechanism of the BBB? I am trying to learn the boot process(among other things) of the BBB but there are just so much info lying around, some are outdated and some are conflicting. Also does that mean I can no longer access or see these two files? Is there a place where I could download the source for the image? Page 4934 (mmc raw mode) http://www.ti.com/lit/ug/spruh73k/spruh73k.pdf I read your instructions at: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSD/SDcard and saw that you have only made one partition on the SDcard with both the kernel and file system, and before you format the card you've dd'ed both the MLO and u-boot.img to it. Is this how that was done? And I thought that was a mistake, silly me :) Do you you notice how we create a 1Mb hole on the front of the drive via sfdisk? After that point, the order of dd'ing the bootloader or mkfs.ext4 the partition doesn't really matter.. I have learned a lot from what you have posted on the web, thank you for your work and I look forward to seeing more Products from you. Too bad there is not a centralized location where we can learn all these for the BBB. Well there is this mailing list. 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/d/optout.
[beagleboard] 3.14 Xenomai Kernel
Has anyone worked on getting a 3.14 kernel for the BeagleBone patched with Xenomai support? It looks like the Xenomai folks have settled on 3.14.17, but the BeagleBone ti kernel looks to be up to 3.14.26-ti-r39: https://github.com/beagleboard/linux/tree/3.14.19-ti-r30 ...with lots of recent jumps (3.14.25, 3.14.24, 3.14.23, 3.14.22, and 3.14.19, all in the last two months!). What's the plan for the 3.14 kernel version from the BeagleBone side? -- Charles Steinkuehler char...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [beagleboard] 3.14 Xenomai Kernel
On Mon, Dec 8, 2014 at 10:19 AM, Charles Steinkuehler char...@steinkuehler.net wrote: Has anyone worked on getting a 3.14 kernel for the BeagleBone patched with Xenomai support? It looks like the Xenomai folks have settled on 3.14.17, but the BeagleBone ti kernel looks to be up to 3.14.26-ti-r39: https://github.com/beagleboard/linux/tree/3.14.19-ti-r30 ...with lots of recent jumps (3.14.25, 3.14.24, 3.14.23, 3.14.22, and 3.14.19, all in the last two months!). What's the plan for the 3.14 kernel version from the BeagleBone side? Hi Charles, Well, let's see if we can carve Xenomai's kernel patchset into the patchset by default.. Right now i'm keeping bb.org's 3.14 in sync with: http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-3.14.y The current mainline (v3.14.26) to ti delta is: https://github.com/RobertCNelson/linux-stable-rcn-ee/compare/356a3e1fde11190febb8ace3cdab8694848ed220...9489c8bb9d4fbb15fba8b0d8b58dce012e8b4e14 most of these are actually cherry-picks from mainline (or mainline development) so it's not as crazy as it looks... 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/d/optout.
Re: [beagleboard] Re: PRU 2.1.0 production ready.
On Mon, Dec 8, 2014 at 10:26 AM, Pete Douma pdo...@adops.com wrote: I keep getting: E: Unable to locate package ti-pru-cgt-installer Then you don't have the repo setup. What version? cat /etc/dogtag ? 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/d/optout.
[beagleboard] BBB enable UART DMA 3.8 kernel?
Sorry if this is a dumb question, but how do I configure the AM335x's UARTs to use DMA mode under the 3.8 version of the kernel? Is it already configured to use DMA? After Googling, the closest I can find is someone saying use platform_data to enable DMA, but I'm sort of new to kernel hacking so I'm not sure how I would do that. -- 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: PRU 2.1.0 production ready.
I keep getting: E: Unable to locate package ti-pru-cgt-installer On Friday, October 31, 2014 1:44:21 PM UTC-4, Kridner, Jason wrote: Many of you might find this of interest. Begin forwarded message: *From:* Robert Nelson *Date:* October 31, 2014 at 10:26:26 AM EDT *To:* Kridner, Jason *Subject:* *Re: FW: PRU 2.1.0 production ready.* That's Very cool! wget http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.1.0/ti_cgt_pru_2.1.0_armlinuxa8hf_busybox_installer.sh chmod +x ti_cgt_pru_2.1.0_armlinuxa8hf_busybox_installer.sh sudo ./ti_cgt_pru_2.1.0_armlinuxa8hf_busybox_installer.sh clpru --help 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/d/optout.
Re: [beagleboard] 3.14 Xenomai Kernel
On 12/8/2014 10:26 AM, Robert Nelson wrote: What's the plan for the 3.14 kernel version from the BeagleBone side? Hi Charles, Well, let's see if we can carve Xenomai's kernel patchset into the patchset by default.. What does this mean exactly? Are you offering to maintain a Xenomai patched kernel for the 'Bone?!? Or do you mean I should try applying the Xenomai patches to the latest 3.14.26-ti-r30 kernel? Right now i'm keeping bb.org's 3.14 in sync with: http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-3.14.y The current mainline (v3.14.26) to ti delta is: https://github.com/RobertCNelson/linux-stable-rcn-ee/compare/356a3e1fde11190febb8ace3cdab8694848ed220...9489c8bb9d4fbb15fba8b0d8b58dce012e8b4e14 most of these are actually cherry-picks from mainline (or mainline development) so it's not as crazy as it looks... What, it's only 2,471 patches! whew! -- Charles Steinkuehler char...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [beagleboard] 3.14 Xenomai Kernel
On Mon, Dec 8, 2014 at 10:26 AM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Dec 8, 2014 at 10:19 AM, Charles Steinkuehler char...@steinkuehler.net wrote: Has anyone worked on getting a 3.14 kernel for the BeagleBone patched with Xenomai support? It looks like the Xenomai folks have settled on 3.14.17, but the BeagleBone ti kernel looks to be up to 3.14.26-ti-r39: https://github.com/beagleboard/linux/tree/3.14.19-ti-r30 ...with lots of recent jumps (3.14.25, 3.14.24, 3.14.23, 3.14.22, and 3.14.19, all in the last two months!). What's the plan for the 3.14 kernel version from the BeagleBone side? Hi Charles, Well, let's see if we can carve Xenomai's kernel patchset into the patchset by default.. Right now i'm keeping bb.org's 3.14 in sync with: http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-3.14.y The current mainline (v3.14.26) to ti delta is: https://github.com/RobertCNelson/linux-stable-rcn-ee/compare/356a3e1fde11190febb8ace3cdab8694848ed220...9489c8bb9d4fbb15fba8b0d8b58dce012e8b4e14 most of these are actually cherry-picks from mainline (or mainline development) so it's not as crazy as it looks... Which repo/tag is there master for v3.14.x? http://git.xenomai.org/ 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/d/optout.
Re: [beagleboard] 3.14 Xenomai Kernel
On Mon, Dec 8, 2014 at 10:34 AM, Charles Steinkuehler char...@steinkuehler.net wrote: On 12/8/2014 10:26 AM, Robert Nelson wrote: What's the plan for the 3.14 kernel version from the BeagleBone side? Hi Charles, Well, let's see if we can carve Xenomai's kernel patchset into the patchset by default.. What does this mean exactly? Are you offering to maintain a Xenomai patched kernel for the 'Bone?!? Pretty much yeah. ;) 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/d/optout.
Re: [beagleboard] 3.14 Xenomai Kernel
On 12/8/2014 10:36 AM, Robert Nelson wrote: Which repo/tag is there master for v3.14.x? http://git.xenomai.org/ The latest ipipe patch for 3.14 can be found in the ipipe-3.14 branch of the ipipe repo: http://git.xenomai.org/ipipe.git/log/?h=ipipe-3.14 ...according to: http://xenomai.org/getting-the-i-pipe-patch/ There are occasionally newer versions in some of the developer repos, but I think the 3.14 stuff has been around long enough it's in the main ipipe repo branches. -- Charles Steinkuehler char...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [beagleboard] 3.14 Xenomai Kernel
On 12/8/2014 10:40 AM, Robert Nelson wrote: On Mon, Dec 8, 2014 at 10:34 AM, Charles Steinkuehler What does this mean exactly? Are you offering to maintain a Xenomai patched kernel for the 'Bone?!? Pretty much yeah. ;) Wow! My wife will love you because now I don't need anything else for Christmas! :) fingers crossed this actually works out! THANKS! -- Charles Steinkuehler char...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[beagleboard] Re: How can I use PRU by CCS Compiler?
เมื่อ วันจันทร์ที่ 8 ธันวาคม ค.ศ. 2014, 21 นาฬิกา 50 นาที 21 วินาที UTC+7, Peter Gregory เขียนว่า: I mean /lib/firmware In the /sys/devices/bone_capemgr.9, it's must have more than 5 lists I still cannot insert any devices tree into that by echo And I think because it's have no my device tree on bone_capemgr.9, I have error by run ./pru_loader like this prussdrv_open open failed which according to your pru_loader.c code it's mean it cannot open PRU_EVTOUT_0 which it's in my device tree Maybe I cannot enable PRU by dtbo file right now? -- 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] 3.14 Xenomai Kernel
On Mon, Dec 8, 2014 at 10:45 AM, Charles Steinkuehler char...@steinkuehler.net wrote: On 12/8/2014 10:40 AM, Robert Nelson wrote: On Mon, Dec 8, 2014 at 10:34 AM, Charles Steinkuehler What does this mean exactly? Are you offering to maintain a Xenomai patched kernel for the 'Bone?!? Pretty much yeah. ;) Wow! My wife will love you because now I don't need anything else for Christmas! :) fingers crossed this actually works out! There's only a couple conflicts. ;) From git://git.xenomai.org/ipipe * branchipipe-3.14 - FETCH_HEAD Auto-merging mm/mmap.c Auto-merging mm/memory.c Auto-merging kernel/trace/ring_buffer.c Auto-merging kernel/sched/core.c Auto-merging kernel/power/hibernate.c Auto-merging kernel/fork.c Auto-merging kernel/debug/debug_core.c Auto-merging init/Kconfig Auto-merging include/linux/sched.h Auto-merging include/linux/clocksource.h Auto-merging fs/exec.c CONFLICT (content): Merge conflict in fs/exec.c Auto-merging drivers/tty/serial/8250/8250_core.c Auto-merging drivers/irqchip/irq-gic.c Auto-merging drivers/gpio/gpio-omap.c CONFLICT (content): Merge conflict in drivers/gpio/gpio-omap.c Auto-merging arch/x86/kvm/x86.c CONFLICT (content): Merge conflict in arch/x86/kvm/x86.c Auto-merging arch/x86/kvm/vmx.c Auto-merging arch/x86/kvm/svm.c Auto-merging arch/x86/kernel/xsave.c Auto-merging arch/x86/kernel/vsyscall_64.c Auto-merging arch/x86/kernel/tsc.c Auto-merging arch/x86/kernel/traps.c Auto-merging arch/x86/kernel/smpboot.c Auto-merging arch/x86/kernel/ptrace.c Auto-merging arch/x86/kernel/entry_64.S CONFLICT (content): Merge conflict in arch/x86/kernel/entry_64.S Auto-merging arch/x86/kernel/dumpstack_64.c Auto-merging arch/x86/kernel/cpu/common.c Auto-merging arch/x86/kernel/apic/apic.c Auto-merging arch/x86/include/asm/traps.h Auto-merging arch/x86/include/asm/thread_info.h Auto-merging arch/x86/include/asm/page_64_types.h Auto-merging arch/x86/ia32/ia32entry.S Auto-merging arch/x86/Kconfig Auto-merging arch/powerpc/platforms/pseries/lpar.c Auto-merging arch/powerpc/mm/hash_native_64.c Auto-merging arch/powerpc/Kconfig Auto-merging arch/arm/mm/proc-xscale.S Auto-merging arch/arm/mm/alignment.c Auto-merging arch/arm/mm/Kconfig Auto-merging arch/arm/mach-omap2/timer.c CONFLICT (content): Merge conflict in arch/arm/mach-omap2/timer.c Auto-merging arch/arm/mach-omap2/prm_common.c Auto-merging arch/arm/mach-omap2/pm44xx.c Auto-merging arch/arm/mach-omap2/pm34xx.c Auto-merging arch/arm/mach-omap2/omap4-common.c Auto-merging arch/arm/mach-omap2/omap-wakeupgen.c Auto-merging arch/arm/mach-omap2/io.c Auto-merging arch/arm/mach-omap2/gpmc.c Auto-merging arch/arm/mach-at91/clock.c Auto-merging arch/arm/kernel/traps.c Auto-merging arch/arm/kernel/process.c Auto-merging arch/arm/include/uapi/asm/unistd.h CONFLICT (content): Merge conflict in arch/arm/include/uapi/asm/unistd.h Auto-merging arch/arm/include/asm/thread_info.h CONFLICT (content): Merge conflict in arch/arm/include/asm/thread_info.h Auto-merging arch/arm/boot/dts/omap4.dtsi Auto-merging arch/arm/boot/compressed/head.S Auto-merging arch/arm/Kconfig Automatic merge failed; fix conflicts and then commit the result. I'll cutt a raw diff and use that for a branch ti-linux-xenomai-3.14.y on https://github.com/RobertCNelson/ti-linux-kernel-dev 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/d/optout.
[beagleboard] Re: How can I use PRU by CCS Compiler?
เมื่อ วันจันทร์ที่ 8 ธันวาคม ค.ศ. 2014, 23 นาฬิกา 46 นาที 18 วินาที UTC+7, tinnagit poojeerang เขียนว่า: เมื่อ วันจันทร์ที่ 8 ธันวาคม ค.ศ. 2014, 21 นาฬิกา 50 นาที 21 วินาที UTC+7, Peter Gregory เขียนว่า: I mean /lib/firmware In the /sys/devices/bone_capemgr.9, it's must have more than 5 lists I still cannot insert any devices tree into that by echo And I think because it's have no my device tree on bone_capemgr.9, I have error by run ./pru_loader like this prussdrv_open open failed which according to your pru_loader.c code it's mean it cannot open PRU_EVTOUT_0 which it's in my device tree Maybe I cannot enable PRU by dtbo file right now? But when I try to echo device tree to that list , It's error by Files Exists but it's not shown in lists -- 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] 3.14 Xenomai Kernel
On 12/8/2014 10:52 AM, Robert Nelson wrote: On Mon, Dec 8, 2014 at 10:45 AM, Charles Steinkuehler char...@steinkuehler.net wrote: fingers crossed this actually works out! There's only a couple conflicts. ;) snip I'll cutt a raw diff and use that for a branch ti-linux-xenomai-3.14.y on https://github.com/RobertCNelson/ti-linux-kernel-dev With any luck, they're as simple as the 3.8.13 conflict (one patch didn't apply because some #include lines were removed at the top of the file). I crafted a pre/post patch set to keep the Xenomai kernel patch script happy and haven't had to mess with it since. With the -ti kernel being mostly mainline (closer to mainline than the 3.8.13 kernel probably), it hopefully won't take too much massaging. Let me know if I can help. -- Charles Steinkuehler char...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[beagleboard] Re: PRU 2.1.0 production ready.
BeagleBoard.org BeagleBone Debian Image 2014-05-14 On Friday, October 31, 2014 1:44:21 PM UTC-4, Kridner, Jason wrote: Many of you might find this of interest. Begin forwarded message: *From:* Robert Nelson *Date:* October 31, 2014 at 10:26:26 AM EDT *To:* Kridner, Jason *Subject:* *Re: FW: PRU 2.1.0 production ready.* That's Very cool! wget http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.1.0/ti_cgt_pru_2.1.0_armlinuxa8hf_busybox_installer.sh chmod +x ti_cgt_pru_2.1.0_armlinuxa8hf_busybox_installer.sh sudo ./ti_cgt_pru_2.1.0_armlinuxa8hf_busybox_installer.sh clpru --help 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/d/optout.
Re: [beagleboard] Re: PRU 2.1.0 production ready.
On Mon, Dec 8, 2014 at 11:23 AM, Pete Douma pdo...@adops.com wrote: BeagleBoard.org BeagleBone Debian Image 2014-05-14 Then till you upgrade to: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-11-19 you get to do this manually! wget http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/2.1.0/ti_cgt_pru_2.1.0_armlinuxa8hf_busybox_installer.sh chmod +x ti_cgt_pru_2.1.0_armlinuxa8hf_busybox_installer.sh sudo ./ti_cgt_pru_2.1.0_armlinuxa8hf_busybox_installer.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/d/optout.
[beagleboard] (LCD 7 + RS485) Kernel 3.14 = crash
Hi everyone,
I'm trying to make the RS 485 working on the kernel 3.14 .
One good news, there is already something to support rs485
My problems, it's that with my hello world program, it doesn't last a long
time . I need to switch off the beagle to make the beagle working again
... that not normal.
One thing that you need to know about the rs485 on the kernel 3.14, it's
that you don't need to configure it anymore on your program, it's handled
in the device tree.
get the sources :
http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb
the compiler :
sudo apt-get update ; sudo apt-get install build-essential
device-tree-compiler
the file to modify for ttyO4 :
sudo nano src/arm/am335x-ttyO4.dtsi
modify the file like that :
uart4 {
pinctrl-names = default;
pinctrl-0 = ;
/* No extra delay after/before transmissions */
rs485-rts-delay = 0 0;
/* GPIO0 pin 22 for data direction */
rts-gpio = gpio0 22 GPIO_ACTIVE_HIGH;
/* Enable RS-485 */
linux,rs485-enabled-at-boot-time;
status = okay;
};
then sudo make install
reboot the beagle
and with a simple echo 1234 /dev/ttyO4 the GPIO direction is moving !
Great !
I don't know why, but it crash when I'm sending a packet in a loop.
I also got this message once ( before starting the program ) :
arm login: [ 102.366458] INFO: rcu_preempt detected stalls on CPUs/tasks:
{} (detected by 0, t=2102 jiffies, g=3000, c=2999, q=52)
[ 102.386869] INFO: Stall ended before state dump start
I will make more test later ..
--
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] 3.14 Xenomai Kernel
On Mon, Dec 8, 2014 at 10:58 AM, Charles Steinkuehler char...@steinkuehler.net wrote: On 12/8/2014 10:52 AM, Robert Nelson wrote: On Mon, Dec 8, 2014 at 10:45 AM, Charles Steinkuehler char...@steinkuehler.net wrote: fingers crossed this actually works out! There's only a couple conflicts. ;) snip I'll cutt a raw diff and use that for a branch ti-linux-xenomai-3.14.y on https://github.com/RobertCNelson/ti-linux-kernel-dev With any luck, they're as simple as the 3.8.13 conflict (one patch didn't apply because some #include lines were removed at the top of the file). I crafted a pre/post patch set to keep the Xenomai kernel patch script happy and haven't had to mess with it since. With the -ti kernel being mostly mainline (closer to mainline than the 3.8.13 kernel probably), it hopefully won't take too much massaging. Let me know if I can help. First pass pushed: https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/213ddbfb8b35e7e926d7f9c44ba5b0178aa8d5a2 It's still building here, most of the conflicts where in x86, so i cheated and just disabled ipipe on x86 and ignored those. There was one irq change on omap-gpio (this is where ti changed it a lot) so that might not work... 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/d/optout.
Re: [beagleboard] 3.14 Xenomai Kernel
On Mon, Dec 8, 2014 at 11:32 AM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Dec 8, 2014 at 10:58 AM, Charles Steinkuehler char...@steinkuehler.net wrote: On 12/8/2014 10:52 AM, Robert Nelson wrote: On Mon, Dec 8, 2014 at 10:45 AM, Charles Steinkuehler char...@steinkuehler.net wrote: fingers crossed this actually works out! There's only a couple conflicts. ;) snip I'll cutt a raw diff and use that for a branch ti-linux-xenomai-3.14.y on https://github.com/RobertCNelson/ti-linux-kernel-dev With any luck, they're as simple as the 3.8.13 conflict (one patch didn't apply because some #include lines were removed at the top of the file). I crafted a pre/post patch set to keep the Xenomai kernel patch script happy and haven't had to mess with it since. With the -ti kernel being mostly mainline (closer to mainline than the 3.8.13 kernel probably), it hopefully won't take too much massaging. Let me know if I can help. First pass pushed: https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/213ddbfb8b35e7e926d7f9c44ba5b0178aa8d5a2 It's still building here, most of the conflicts where in x86, so i cheated and just disabled ipipe on x86 and ignored those. There was one irq change on omap-gpio (this is where ti changed it a lot) so that might not work... Yeap dies on compiling omap-gpio.. ;) I'll have to dig into that section more.. 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/d/optout.
[beagleboard] Re: Servo PWM: Getting IOError: [Errno 2] No such file or directory: '/slots'
I too faced this with ubuntu 14.04, done the following steps to overcome such errors got the missing dts files from https://github.com/beagleboard/devicetree-source compiled required files using build file (you should install dtc compiler using *apt-get install device-tree-compiler* and if you face errors with -@ option use wget -c https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh chmod +x dtc.sh ./dtc.sh ) create dts-compile.sh with following code #!/bin/bash echo Compiling the overlay from .dts to .dtbo dtc -O dtb -o am33xx_pwm-00A0.dtbo -b 0 -@ am33xx_pwm-00A0.dts dtc -O dtb -o bone_eqep0-00A0.dtbo -b 0 -@ bone_eqep0-00A0.dts dtc -O dtb -o bone_eqep1-00A0.dtbo -b 0 -@ bone_eqep1-00A0.dts dtc -O dtb -o bone_eqep2-00A0.dtbo -b 0 -@ bone_eqep2-00A0.dts dtc -O dtb -o bone_pwm_P8_13-00A0.dtbo -b 0 -@ bone_pwm_P8_13-00A0.dts dtc -O dtb -o bone_pwm_P8_19-00A0.dtbo -b 0 -@ bone_pwm_P8_19-00A0.dts dtc -O dtb -o bone_pwm_P8_34-00A0.dtbo -b 0 -@ bone_pwm_P8_34-00A0.dts dtc -O dtb -o bone_pwm_P8_36-00A0.dtbo -b 0 -@ bone_pwm_P8_36-00A0.dts dtc -O dtb -o bone_pwm_P8_45-00A0.dtbo -b 0 -@ bone_pwm_P8_45-00A0.dts dtc -O dtb -o bone_pwm_P8_46-00A0.dtbo -b 0 -@ bone_pwm_P8_46-00A0.dts dtc -O dtb -o bone_pwm_P9_14-00A0.dtbo -b 0 -@ bone_pwm_P9_14-00A0.dts dtc -O dtb -o bone_pwm_P9_16-00A0.dtbo -b 0 -@ bone_pwm_P9_16-00A0.dts dtc -O dtb -o bone_pwm_P9_21-00A0.dtbo -b 0 -@ bone_pwm_P9_21-00A0.dts dtc -O dtb -o bone_pwm_P9_22-00A0.dtbo -b 0 -@ bone_pwm_P9_22-00A0.dts dtc -O dtb -o bone_pwm_P9_28-00A0.dtbo -b 0 -@ bone_pwm_P9_28-00A0.dts dtc -O dtb -o bone_pwm_P9_29-00A0.dtbo -b 0 -@ bone_pwm_P9_29-00A0.dts dtc -O dtb -o bone_pwm_P9_31-00A0.dtbo -b 0 -@ bone_pwm_P9_31-00A0.dts dtc -O dtb -o bone_pwm_P9_42-00A0.dtbo -b 0 -@ bone_pwm_P9_42-00A0.dts echo copying files to /lib/firmware cp -f *.dtbo /lib/firmware change the permissions using chmod +x dts-compile.sh Now run the shell script file using ./dts-compile.sh use the following terminal commands to export pwm pins *export SLOTS=/sys/devices/bone_capemgr.*/slots* *export PINS=/sys/kernel/de**bu**g/pinctrl/44e10800.pinmux/pins* *modprobe pwm_test* *echo am33xx_pwm **$**SLOTS* *echo bone_pwm_P8_19 $SLOTS* *echo bone_pwm_P9_21 $SLOTS* * in 'bone_capemgr.*/' is either 8 or 9 depends on your version, most probably 9 for ubuntu 14.04 On Sunday, 7 December 2014 08:14:02 UTC+5:30, Sid Raj wrote: Hi, On my BBB running Ubuntu 14 I am using adafruit py libs to for servo control. But I get the following error. Same with P9_14. Any idea why I am getting this and what I should do to make it go away? Thanks a lot! import Adafruit_BBIO.PWM as PWM PWM.start(P8_13, 95.0, 60) IOError: [Errno 2] No such file or directory: '/slots' Sid -- 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: Servo PWM: Getting IOError: [Errno 2] No such file or directory: '/slots'
I too faced this with ubuntu 14.04, done the following steps to overcome such errors got the missing dts files from https://github.com/venkaty89/devicetree-source/tree/master/arch/arm/boot/dts https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fbeagleboard%2Fdevicetree-sourcesa=Dsntz=1usg=AFQjCNHfhQXHwsjHhX_Z1IblMt9KS-fcwg compiled required files using build file (you should install dtc compiler using *apt-get install device-tree-compiler* and if you face errors with -@ option use wget -c https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh chmod +x dtc.sh ./dtc.sh ) create dts-compile.sh with following code #!/bin/bash echo Compiling the overlay from .dts to .dtbo dtc -O dtb -o am33xx_pwm-00A0.dtbo -b 0 -@ am33xx_pwm-00A0.dts dtc -O dtb -o bone_eqep0-00A0.dtbo -b 0 -@ bone_eqep0-00A0.dts dtc -O dtb -o bone_eqep1-00A0.dtbo -b 0 -@ bone_eqep1-00A0.dts dtc -O dtb -o bone_eqep2-00A0.dtbo -b 0 -@ bone_eqep2-00A0.dts dtc -O dtb -o bone_pwm_P8_13-00A0.dtbo -b 0 -@ bone_pwm_P8_13-00A0.dts dtc -O dtb -o bone_pwm_P8_19-00A0.dtbo -b 0 -@ bone_pwm_P8_19-00A0.dts dtc -O dtb -o bone_pwm_P8_34-00A0.dtbo -b 0 -@ bone_pwm_P8_34-00A0.dts dtc -O dtb -o bone_pwm_P8_36-00A0.dtbo -b 0 -@ bone_pwm_P8_36-00A0.dts dtc -O dtb -o bone_pwm_P8_45-00A0.dtbo -b 0 -@ bone_pwm_P8_45-00A0.dts dtc -O dtb -o bone_pwm_P8_46-00A0.dtbo -b 0 -@ bone_pwm_P8_46-00A0.dts dtc -O dtb -o bone_pwm_P9_14-00A0.dtbo -b 0 -@ bone_pwm_P9_14-00A0.dts dtc -O dtb -o bone_pwm_P9_16-00A0.dtbo -b 0 -@ bone_pwm_P9_16-00A0.dts dtc -O dtb -o bone_pwm_P9_21-00A0.dtbo -b 0 -@ bone_pwm_P9_21-00A0.dts dtc -O dtb -o bone_pwm_P9_22-00A0.dtbo -b 0 -@ bone_pwm_P9_22-00A0.dts dtc -O dtb -o bone_pwm_P9_28-00A0.dtbo -b 0 -@ bone_pwm_P9_28-00A0.dts dtc -O dtb -o bone_pwm_P9_29-00A0.dtbo -b 0 -@ bone_pwm_P9_29-00A0.dts dtc -O dtb -o bone_pwm_P9_31-00A0.dtbo -b 0 -@ bone_pwm_P9_31-00A0.dts dtc -O dtb -o bone_pwm_P9_42-00A0.dtbo -b 0 -@ bone_pwm_P9_42-00A0.dts echo copying files to /lib/firmware cp -f *.dtbo /lib/firmware change the permissions using chmod +x dts-compile.sh Now run the shell script file using ./dts-compile.sh use the following terminal commands to export pwm pins *export SLOTS=/sys/devices/bone_capemgr.*/slots* *export PINS=/sys/kernel/de**bu**g/pinctrl/44e10800.pinmux/pins* *modprobe pwm_test* *echo am33xx_pwm **$**SLOTS* *echo bone_pwm_P8_19 $SLOTS* *echo bone_pwm_P9_21 $SLOTS* * in 'bone_capemgr.*/' is either 8 or 9 depends on your version, most probably 9 for ubuntu 14.04 On Sunday, 7 December 2014 08:14:02 UTC+5:30, Sid Raj wrote: Hi, On my BBB running Ubuntu 14 I am using adafruit py libs to for servo control. But I get the following error. Same with P9_14. Any idea why I am getting this and what I should do to make it go away? Thanks a lot! import Adafruit_BBIO.PWM as PWM PWM.start(P8_13, 95.0, 60) IOError: [Errno 2] No such file or directory: '/slots' Sid -- 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: Servo PWM: Getting IOError: [Errno 2] No such file or directory: '/slots'
I too faced this with ubuntu 14.04, done the following steps to overcome such errors got the missing dts files from https://github.com/venkaty89/devicetree-source/tree/master/arch/arm/boot/dts https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fbeagleboard%2Fdevicetree-sourcesa=Dsntz=1usg=AFQjCNHfhQXHwsjHhX_Z1IblMt9KS-fcwg compiled required files using build file (you should install dtc compiler using *apt-get install device-tree-compiler* and if you face errors with -@ option use wget -c https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh chmod +x dtc.sh ./dtc.sh ) create dts-compile.sh with following code #!/bin/bash echo Compiling the overlay from .dts to .dtbo dtc -O dtb -o am33xx_pwm-00A0.dtbo -b 0 -@ am33xx_pwm-00A0.dts dtc -O dtb -o bone_eqep0-00A0.dtbo -b 0 -@ bone_eqep0-00A0.dts dtc -O dtb -o bone_eqep1-00A0.dtbo -b 0 -@ bone_eqep1-00A0.dts dtc -O dtb -o bone_eqep2-00A0.dtbo -b 0 -@ bone_eqep2-00A0.dts dtc -O dtb -o bone_pwm_P8_13-00A0.dtbo -b 0 -@ bone_pwm_P8_13-00A0.dts dtc -O dtb -o bone_pwm_P8_19-00A0.dtbo -b 0 -@ bone_pwm_P8_19-00A0.dts dtc -O dtb -o bone_pwm_P8_34-00A0.dtbo -b 0 -@ bone_pwm_P8_34-00A0.dts dtc -O dtb -o bone_pwm_P8_36-00A0.dtbo -b 0 -@ bone_pwm_P8_36-00A0.dts dtc -O dtb -o bone_pwm_P8_45-00A0.dtbo -b 0 -@ bone_pwm_P8_45-00A0.dts dtc -O dtb -o bone_pwm_P8_46-00A0.dtbo -b 0 -@ bone_pwm_P8_46-00A0.dts dtc -O dtb -o bone_pwm_P9_14-00A0.dtbo -b 0 -@ bone_pwm_P9_14-00A0.dts dtc -O dtb -o bone_pwm_P9_16-00A0.dtbo -b 0 -@ bone_pwm_P9_16-00A0.dts dtc -O dtb -o bone_pwm_P9_21-00A0.dtbo -b 0 -@ bone_pwm_P9_21-00A0.dts dtc -O dtb -o bone_pwm_P9_22-00A0.dtbo -b 0 -@ bone_pwm_P9_22-00A0.dts dtc -O dtb -o bone_pwm_P9_28-00A0.dtbo -b 0 -@ bone_pwm_P9_28-00A0.dts dtc -O dtb -o bone_pwm_P9_29-00A0.dtbo -b 0 -@ bone_pwm_P9_29-00A0.dts dtc -O dtb -o bone_pwm_P9_31-00A0.dtbo -b 0 -@ bone_pwm_P9_31-00A0.dts dtc -O dtb -o bone_pwm_P9_42-00A0.dtbo -b 0 -@ bone_pwm_P9_42-00A0.dts echo copying files to /lib/firmware cp -f *.dtbo /lib/firmware change the permissions using chmod +x dts-compile.sh Now run the shell script file using ./dts-compile.sh use the following terminal commands to export pwm pins *export SLOTS=/sys/devices/bone_capemgr.*/slots* *export PINS=/sys/kernel/de**bu**g/pinctrl/44e10800.pinmux/pins* *modprobe pwm_test* *echo am33xx_pwm **$**SLOTS* *echo bone_pwm_P8_19 $SLOTS* *echo bone_pwm_P9_21 $SLOTS* * in 'bone_capemgr.*/' is either 8 or 9 depends on your version, most probably 9 for ubuntu 14.04 On Sunday, 7 December 2014 08:14:02 UTC+5:30, Sid Raj wrote: Hi, On my BBB running Ubuntu 14 I am using adafruit py libs to for servo control. But I get the following error. Same with P9_14. Any idea why I am getting this and what I should do to make it go away? Thanks a lot! import Adafruit_BBIO.PWM as PWM PWM.start(P8_13, 95.0, 60) IOError: [Errno 2] No such file or directory: '/slots' Sid -- 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: Servo PWM: Getting IOError: [Errno 2] No such file or directory: '/slots'
if you are using kernel 3.14.x and above, you won't have capemgr. As said by RbertCNelson you could just install 3.8 from the debian repo: sudo apt-get update sudo apt-get install linux-3.8.13-bone68 sudo reboot On Sunday, 7 December 2014 08:14:02 UTC+5:30, Sid Raj wrote: Hi, On my BBB running Ubuntu 14 I am using adafruit py libs to for servo control. But I get the following error. Same with P9_14. Any idea why I am getting this and what I should do to make it go away? Thanks a lot! import Adafruit_BBIO.PWM as PWM PWM.start(P8_13, 95.0, 60) IOError: [Errno 2] No such file or directory: '/slots' Sid -- 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] 3.14 Xenomai Kernel
On Mon, Dec 8, 2014 at 11:40 AM, Robert Nelson robertcnel...@gmail.com wrote:
On Mon, Dec 8, 2014 at 11:32 AM, Robert Nelson robertcnel...@gmail.com
wrote:
On Mon, Dec 8, 2014 at 10:58 AM, Charles Steinkuehler
char...@steinkuehler.net wrote:
On 12/8/2014 10:52 AM, Robert Nelson wrote:
On Mon, Dec 8, 2014 at 10:45 AM, Charles Steinkuehler
char...@steinkuehler.net wrote:
fingers crossed this actually works out!
There's only a couple conflicts. ;)
snip
I'll cutt a raw diff and use that for a branch
ti-linux-xenomai-3.14.y on
https://github.com/RobertCNelson/ti-linux-kernel-dev
With any luck, they're as simple as the 3.8.13 conflict (one patch
didn't apply because some #include lines were removed at the top of the
file). I crafted a pre/post patch set to keep the Xenomai kernel patch
script happy and haven't had to mess with it since.
With the -ti kernel being mostly mainline (closer to mainline than the
3.8.13 kernel probably), it hopefully won't take too much massaging.
Let me know if I can help.
First pass pushed:
https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/213ddbfb8b35e7e926d7f9c44ba5b0178aa8d5a2
It's still building here, most of the conflicts where in x86, so i
cheated and just disabled ipipe on x86 and ignored those.
There was one irq change on omap-gpio (this is where ti changed it a
lot) so that might not work...
Yeap dies on compiling omap-gpio.. ;) I'll have to dig into that section
more..
Well it booted...
http://paste.debian.net/135519/
Not 100% happy..
[2.259383] Switched to clocksource ipipe_tsc
[2.269424]
[2.269449] =
[2.269458] [ INFO: inconsistent lock state ]
[2.269472] 3.14.26-ti-xenomai-r39.1 #1 Not tainted
[2.269480] -
[2.269489] inconsistent {SOFTIRQ-ON-W} - {IN-SOFTIRQ-W} usage.
[2.269500] swapper/0/1 [HC0[0]:SC1[1]:HE0:SE0] takes:
[2.269510] (std_spinlock(zone-lock)-rlock){+.?...}, at:
[c010503c] free_one_page+0x30/0x2d0
[2.269566] {SOFTIRQ-ON-W} state was registered at:
[2.269575] [c00925d8] trace_hardirqs_on_caller+0x150/0x1f0
[2.269595] [c009268c] trace_hardirqs_on+0x14/0x18
[2.269608] [c08b6b74] __ipipe_fast_svc_irq_exit+0x4/0x14
[2.269625] [c08b5b54] _raw_spin_lock+0x4c/0x54
[2.269650] [c010503c] free_one_page+0x30/0x2d0
[2.269663] [c0106478] free_hot_cold_page+0x15c/0x164
[2.269677] [c01064e4] __free_pages+0x64/0x68
[2.269691] [c0106944] free_contig_range+0x70/0xb8
[2.269704] [c0106c84] alloc_contig_range+0x2f8/0x328
[2.269718] [c05704fc] dma_alloc_from_contiguous+0xa0/0x1f4
[2.269740] [c001bf84] __alloc_from_contiguous+0x38/0x12c
[2.269767] [c0c2240c] atomic_pool_init+0x84/0x124
[2.269789] [c0008b34] do_one_initcall+0x100/0x1b4
[2.269804] [c0c1cd60] kernel_init_freeable+0x148/0x1ec
[2.269817] [c08a6d68] kernel_init+0x18/0xf0
[2.269838] [c000f880] ret_from_fork+0x18/0x38
[2.269858] irq event stamp: 223980
[2.269866] hardirqs last enabled at (223979): [c0104904]
free_pages_prepare+0x140/0x204
[2.269881] hardirqs last disabled at (223980): [c01052fc]
__free_pages_ok.part.65+0x20/0xa0
[2.269896] softirqs last enabled at (223456): [c0049f08]
__do_softirq+0x25c/0x3d4
[2.269919] softirqs last disabled at (223950): [c004a3b0]
irq_exit+0xd0/0x10c
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/d/optout.
[beagleboard] Re: Servo PWM: Getting IOError: [Errno 2] No such file or directory: '/slots'
if you are using kernel 3.14.x and above, you won't have capemgr. As said by RbertCNelson you could just install 3.8 from the debian repo: sudo apt-get update sudo apt-get install linux-3.8.13-bone68 sudo reboot if you still face errors in loading pwm device trees due to missing dtbo files, use the following steps sudo apt-get install device-tree-compiler If you face errors with -@ option while compiling use following steps wget -c https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh chmod +x dtc.sh ./dtc.sh get the missing dts files from https://github.com/beagleboard/devicetree-source now at https://github.com/venkaty89/devicetree-source/tree/master/arch/arm/boot/dts or https://github.com/beagleboard/devicetree-source/tree/master/arch/arm/boot/dts compile required files using build file #!/bin/bash echo Compiling the overlay from .dts to .dtbo dtc -O dtb -o am33xx_pwm-00A0.dtbo -b 0 -@ am33xx_pwm-00A0.dts dtc -O dtb -o bone_eqep0-00A0.dtbo -b 0 -@ bone_eqep0-00A0.dts dtc -O dtb -o bone_eqep1-00A0.dtbo -b 0 -@ bone_eqep1-00A0.dts dtc -O dtb -o bone_eqep2-00A0.dtbo -b 0 -@ bone_eqep2-00A0.dts dtc -O dtb -o bone_pwm_P8_13-00A0.dtbo -b 0 -@ bone_pwm_P8_13-00A0.dts dtc -O dtb -o bone_pwm_P8_19-00A0.dtbo -b 0 -@ bone_pwm_P8_19-00A0.dts dtc -O dtb -o bone_pwm_P8_34-00A0.dtbo -b 0 -@ bone_pwm_P8_34-00A0.dts dtc -O dtb -o bone_pwm_P8_36-00A0.dtbo -b 0 -@ bone_pwm_P8_36-00A0.dts dtc -O dtb -o bone_pwm_P8_45-00A0.dtbo -b 0 -@ bone_pwm_P8_45-00A0.dts dtc -O dtb -o bone_pwm_P8_46-00A0.dtbo -b 0 -@ bone_pwm_P8_46-00A0.dts dtc -O dtb -o bone_pwm_P9_14-00A0.dtbo -b 0 -@ bone_pwm_P9_14-00A0.dts dtc -O dtb -o bone_pwm_P9_16-00A0.dtbo -b 0 -@ bone_pwm_P9_16-00A0.dts dtc -O dtb -o bone_pwm_P9_21-00A0.dtbo -b 0 -@ bone_pwm_P9_21-00A0.dts dtc -O dtb -o bone_pwm_P9_22-00A0.dtbo -b 0 -@ bone_pwm_P9_22-00A0.dts dtc -O dtb -o bone_pwm_P9_28-00A0.dtbo -b 0 -@ bone_pwm_P9_28-00A0.dts dtc -O dtb -o bone_pwm_P9_29-00A0.dtbo -b 0 -@ bone_pwm_P9_29-00A0.dts dtc -O dtb -o bone_pwm_P9_31-00A0.dtbo -b 0 -@ bone_pwm_P9_31-00A0.dts dtc -O dtb -o bone_pwm_P9_42-00A0.dtbo -b 0 -@ bone_pwm_P9_42-00A0.dts If you face errors with -@ option while compiling use following steps wget -c https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh chmod +x dtc.sh ./dtc.sh copy compiled dtbo files to /lib/firmware using copy file #!/bin/bash cp -f *.dtbo /lib/firmware load the required dtbo files using bash file load_dtbo #!/bin/bash echo loading device trees export SLOTS=/sys/devices/bone_capemgr.9/slots export PINS=/sys/kernel/debug/pinctrl/44e10800.pinmux/pins modprobe pwm_test echo am33xx_pwm $SLOTS echo bone_pwm_P8_19 $SLOTS echo bone_pwm_P9_21 $SLOTS On Sunday, 7 December 2014 08:14:02 UTC+5:30, Sid Raj wrote: Hi, On my BBB running Ubuntu 14 I am using adafruit py libs to for servo control. But I get the following error. Same with P9_14. Any idea why I am getting this and what I should do to make it go away? Thanks a lot! import Adafruit_BBIO.PWM as PWM PWM.start(P8_13, 95.0, 60) IOError: [Errno 2] No such file or directory: '/slots' Sid -- 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: How can I use PRU by CCS Compiler?
เมื่อ วันจันทร์ที่ 8 ธันวาคม ค.ศ. 2014, 23 นาฬิกา 57 นาที 21 วินาที UTC+7,
tinnagit poojeerang เขียนว่า:
เมื่อ วันจันทร์ที่ 8 ธันวาคม ค.ศ. 2014, 23 นาฬิกา 46 นาที 18 วินาที UTC+7,
tinnagit poojeerang เขียนว่า:
เมื่อ วันจันทร์ที่ 8 ธันวาคม ค.ศ. 2014, 21 นาฬิกา 50 นาที 21 วินาที
UTC+7, Peter Gregory เขียนว่า:
I mean /lib/firmware
In the /sys/devices/bone_capemgr.9, it's must have more than 5 lists
I still cannot insert any devices tree into that by echo
And I think because it's have no my device tree on bone_capemgr.9,
I have error by run ./pru_loader like this prussdrv_open open failed
which according to your pru_loader.c code
it's mean it cannot open PRU_EVTOUT_0 which it's in my device tree
Maybe I cannot enable PRU by dtbo file right now?
But when I try to echo device tree to that list , It's error by Files
Exists but it's not shown in lists
Yeah It's work already...
I try to change your dts file
in your dts file , you use P9.31 is output right?
I saw in table Pin map is used by SPI (http://elinux.org/Ti_AM33XX_PRUSSv2
http://elinux.org/Ti_AM33XX_PRUSSv2)
and I change to use P9.27 on GPIO125 , Offset Reg = 9A4h
and change you c code to simple blink on P9.27
and then it's work right now
Thank You
my C Code:
void main(){
volatile uint32_t gpio;
/* Clear SYSCFG[STANDBY_INIT] to enable OCP master port */
CT_CFG.SYSCFG_bit.STANDBY_INIT = 0;
/* Toggle GPO pins TODO: Figure out which to use */
gpio = 0x0020;
/* TODO: Create stop condition, else it will toggle indefinitely */
while(1){
__R30 ^= gpio;
__delay_cycles(1);
}
/* Halt the PRU core */
__halt();
}
my dts code :
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = MYOVERLAY;
version = 00A0;
/* state the resources this cape uses */
exclusive-use =
// PRU resources used
pruss,
pru0,
// PRU Input pins
P8.16,pr1_pru0_pru_r31_14, // PIN Name and the PRU
port it maps to (see table above)
// PRU Output pins
P9.27,pr1_pru0_pru_r30_5;
// MUX Bit Maps:
// 0x40 = slow slew (0 = fast slew)
// 0x20 = input (0 = output)
// 0x10 = pullup, 0x08 = disabled (0 = pulldown)
// 0x01 to 0x07 = mode 1 to 7
fragment@8 {
target = am33xx_pinmux;
__overlay__ {
pruss_pins: pruss_pins {
pinctrl-single,pins =
0x038 0x06 // P8_16, gpio1[14] mode 6, input pull-up
0x1A4 0x25 // P9_27, gpio3[19] mode 5, output,
pull-down
;
};
};
};
fragment@10 {
target = pruss;
__overlay__ {
status = okay; // This enables the PRU
pinctrl-names = default;
pinctrl-0 = pruss_pins; // This uses our custom mapping
(see above definition)
// This is for documentation only. You can see the pin
mappings by:
// sudo cat /sys/kernel/debug/gpio
any_name1 { // Grouping of pins under this name
pin-names = Input pin description; // one name
per pin defined in gpios. Multiple entries are$
gpios = gpio4 14 1; // gpio? (One based: 1-4
instead of 0-3) bit(0-31) input(1)/output(0). $
};
any_name2 {
pin-names = Output pin description;
gpios = gpio2 19 0;
};
};
};
};
Thank you for your all support
--
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: chipsee beaglebone lcd/dvi expansion kernel support
Hi Fernando.. the issues looks like typical nodejs modules installations
issues.
Did you install nodejs yourself or it came on the image?
There are a few but major changes regarding how to access the gpios between
the kernel 3.2 and 3.8.. so I recommend you make sure you have the right
nodejs version installed. And also reinstall all the modules by the package
manager.
On Thu, Dec 4, 2014 at 9:54 PM, Fernando Derkoski bril...@gmail.com wrote:
Hi there I installed the image that came with the dvd, it works, but I
cannot access the GPIO with node, with octalbonescript this is the
error CapeMgr not found: undefined
/usr/local/lib/node_modules/octalbonescript/index.js:155
var n = pin.gpio;
^
TypeError: Cannot read property 'gpio' of undefined
with bonescript:
/usr/local/lib/node_modules/bonescript/index.js:161
if(typeof resp.err != 'undefined') {
^
TypeError: Cannot read property 'err' of undefined
Anyone have a solution?
On Tuesday, October 7, 2014 5:31:24 PM UTC-3, Mahammad Mostafa wrote:
Hi.. for the debian image.. I think it is already available under recent
Chipsee 2014 DVD.. image file name is: BBB_Exp_Debian20140522.img.xz
Please check Chipsee customer support for it, they are very friendly.
On Tue, Oct 7, 2014 at 9:15 PM, giorg...@gmail.com wrote:
I'm also interested in debian image
giorg...@gmail.com
Il giorno domenica 5 ottobre 2014 14:41:44 UTC+2, frs...@yahoo.com ha
scritto:
Two questions:
1. how do I stop the image from looking for internet? I just want it to
run on its own and boot up quickly. I don't want to connect to the
internet.
2. I think chipsee finally has a debian image. Does anyone have a copy?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the
Google Groups BeagleBoard group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/beagleboard/Y-rcKPITy0Q/unsubscribe.
To unsubscribe from this group and all its topics, 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 a topic in the
Google Groups BeagleBoard group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/Y-rcKPITy0Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
beagleboard+unsubscr...@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: How Device Tree Overlay Works
A good tutorial here:
http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/
simple example:
cd /sys/class/gpio
cd gpio60
echo 60 export
echo out direction
echo 1 value
good luck
Jan
On Tuesday, December 9, 2014 1:41:10 AM UTC+11, Hemant Kapoor wrote:
Hello All,
I am a newbie to Linux and trying to figure out how device tree overlay
works...
So after googling for many days, I came up with below device tree:
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = MY-LED;
version = 00A0;
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
P9.12,/* GPIO*/
/* the hardware ip uses */
gpio0;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
bb_mygpio_pins: pinmux_bb_mygpio_pins {
pinctrl-single,pins =
0x870 0x07/*
output mode | MODE7, see Pin_Configuration.pdf in BBB */
;
};
};
};
fragment@1 {
target = ocp;/* not sure why it is not gpio0 */
__overlay__ {
status = okay;
pinctrl-names = default;
pinctrl-0 = bb_mygpio_pins;
};
};
};
I was able to build the dtc and generated MY-LED-00A0.dtbo
I then copied the MY-LED-00A0.dtbo to /lib/firmware
Then i echoed it to slots:
echo MY-LED $SLOTS
and cat $SLOTS gives me below result:
root@beaglebone:/lib/firmware# cat $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
9: ff:P-O-L Override Board Name,00A0,Override Manuf,MY-LED
By looks of this, MY_LED seems to be loaded...
The main confusion is how can I use MY-LED?
Where are the files for MY-LED present?
Any help or guidance is much appreciated.
--
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: How Device Tree Overlay Works
You need to do
echo 60 export
Before
cd gpio60
On Dec 9, 2014 2:32 AM, janszymanski12...@gmail.com wrote:
A good tutorial here:
http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/
simple example:
cd /sys/class/gpio
cd gpio60
echo 60 export
echo out direction
echo 1 value
good luck
Jan
On Tuesday, December 9, 2014 1:41:10 AM UTC+11, Hemant Kapoor wrote:
Hello All,
I am a newbie to Linux and trying to figure out how device tree overlay
works...
So after googling for many days, I came up with below device tree:
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = MY-LED;
version = 00A0;
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
P9.12,/* GPIO*/
/* the hardware ip uses */
gpio0;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
bb_mygpio_pins: pinmux_bb_mygpio_pins {
pinctrl-single,pins =
0x870 0x07/*
output mode | MODE7, see Pin_Configuration.pdf in BBB */
;
};
};
};
fragment@1 {
target = ocp;/* not sure why it is not gpio0
*/
__overlay__ {
status = okay;
pinctrl-names = default;
pinctrl-0 = bb_mygpio_pins;
};
};
};
I was able to build the dtc and generated MY-LED-00A0.dtbo
I then copied the MY-LED-00A0.dtbo to /lib/firmware
Then i echoed it to slots:
echo MY-LED $SLOTS
and cat $SLOTS gives me below result:
root@beaglebone:/lib/firmware# cat $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
9: ff:P-O-L Override Board Name,00A0,Override Manuf,MY-LED
By looks of this, MY_LED seems to be loaded...
The main confusion is how can I use MY-LED?
Where are the files for MY-LED present?
Any help or guidance is much appreciated.
--
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.
--
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: chipsee beaglebone lcd/dvi expansion kernel support
Bill, I tried your advice and the .sh file doesn't fun. I am using Debian and the cpu monitor usage runs at 100% when I do this. But it fails to write anything to the sd card. After some back and forth with chipsee customer support, I received a message to update a line from --device) shift; device=$1; shift; ;; to --device) shift; device=$1p; shift; ;; I am not that familiar with linux as one can tell, but it seems the change just appends a p to what ever I type for the device. I can upload a copy of the zip to dropbox or something if anyone wants to look at it. On Monday, December 8, 2014 10:35:29 AM UTC-5, William Pretty Security wrote: Hi; If I understand you correctly, you need to use either “su” or “sudo” but not both. If you enter: sudo . /mksdcard.sh /dev/sdX It will prompt you for a password. Just use the password that you used to login. Bill No one could make a greater mistake than he who did nothing because he could do only a little. All that is necessary for the triumph of evil is that good men do nothing Edmond Burke *(1729 - 1797)* http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book *From:* beagl...@googlegroups.com javascript: [mailto: beagl...@googlegroups.com javascript:] *Sent:* Sunday, December 07, 2014 4:00 PM *To:* beagl...@googlegroups.com javascript: *Cc:* xris@googlemail.com javascript: *Subject:* [beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support Hello all, I am new to Beaglebone Black (making the jump from the arduino/chipkit world) and am having some difficulty with this Chipsee 7 capacitive cape. I feel I am banging my head against the wall over something simple, but could some one provide a walk through for just getting started with the display. I have the BBB working to an external display via HDMI, but am not able to get the lcd to work unless I use an existing .img. I am trying to use one of Chipsee's provided prebuilt images, but am having trouble. Chipsee's directions state to use: sudo su ./mksdcard.sh /dev/sdX (X in this instance is a after checking with fdisk -l) But I keep getting either no passwd for ./mksdcard.sh. If I drop the sudo su I get permission denied. Any help would be very much appreciated. 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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5577 / Virus Database: 4235/8695 - Release Date: 12/07/14 -- 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] Serial over USB
I am looking for more information on running Serial over USB from a linux desktop host to the BBB device. Some information on the web seems out of date, at least on debian 7.7. other information is very helpful. I am summarizing here some of what I have learned myself first: a sending desktop linux can send information to the BBB over /dev/ttyACM0. a recipient BBB linux can receive information on /dev/ttyGS0 . this is part of the g_multi kernel module and thus works out of the box on debian 7.7. this can be tested as bbb# cat /dev/ttyGS0 desktop# echo hello /dev/ttyACM0 and the bbb should now echo hello. the comm is buffered, although I am not sure on which side (desktop or bbb). this is obvious from looking at the desktop immediately after a fresh boot: desktop# cat /dev/ttyACM0 which will still return the log in information from the boot on the first use. after the buffer is full, the device blocks and waits. information about the port settings can be found (and potentially set, though I don't think anything is needed) with stty -F /dev/ttyGS0 -a however, I believe that some of this are just pretend you are rs232 wrong. this is because I just wrote a little perl program that sends 1Mbyte into the device and then closes. this takes about 1.5 seconds. This would suggest a raw speed of about 7 Mbaud, a little bit faster than the 9.6 Kbaud that stty tells me. I am guessing that the serial port over USB uses the USB 1.1 full-speed protocol that caps out at 12 Mbaud. I believe hi-speed 480 Mbaud connections require block operations. the serial comm speed is interesting to compare to the usb mass storage speed. A dd from the desktop host to the mounted BBB mass-storage device partition over USB produces 21 Mbaud. so, the serial connection is about 1/3 of what the BBB is capable of over hi-speed USB mass storage. the eMMC limits out at about 70Mbaud local, which is itself about three times the speed of the mass storage driver over the USB 2.0 connection. (and remember that USB 2.0 is itself limited to 480Mbaud. I also tried to measure the speed over the usb0 ethernet with dd and netcat [nc] to see how close this could get, but I failed.) hope this helps. * one question: I have lost some information sent forth and back, which I believe is due to the bbb issuing (from /var/log/syslog) a serial-getty@ttyGS0.service.holdoff time over, scheduling restart is it possible to force ttyGS0 to always be available, and never to want to restart? * I may write a different driver that sits on top of the mass storage driver and communicates over a small shared storage area. it's a crazy idea, but it could be faster than serial-over-usb if I know that I will be dealing in blocks of 512 bytes and relatively easy to debug and synchronize. -- 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: How Device Tree Overlay Works
Thanks Jan and Dacobi for your valuable comments.
There is one small confusion. I declared the pin to be an output pin in my
device tree overlay:
0x870 0x07/* output mode | MODE7, see Pin_Configuration.pdf in BBB
*/
but after exporting pin as you guys mentioned and looking at the direction,
I get it as 'in'
root@beaglebone:/sys/class/gpio/gpio60# cat direction
in
The below steps described by Jan could be done without the use of device
overlay
cd /sys/class/gpio
cd gpio60
echo 60 export
echo out direction
echo 1 value
So why do we need device overlay :(
Please help me get rid of this confusion. It is driving me mad
HK!
On Tuesday, 9 December 2014 01:42:08 UTC, Dacobi wrote:
You need to do
echo 60 export
Before
cd gpio60
On Dec 9, 2014 2:32 AM, janszyma...@gmail.com javascript: wrote:
A good tutorial here:
http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/
simple example:
cd /sys/class/gpio
cd gpio60
echo 60 export
echo out direction
echo 1 value
good luck
Jan
On Tuesday, December 9, 2014 1:41:10 AM UTC+11, Hemant Kapoor wrote:
Hello All,
I am a newbie to Linux and trying to figure out how device tree overlay
works...
So after googling for many days, I came up with below device tree:
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = MY-LED;
version = 00A0;
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
P9.12,/* GPIO*/
/* the hardware ip uses */
gpio0;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
bb_mygpio_pins: pinmux_bb_mygpio_pins {
pinctrl-single,pins =
0x870 0x07/*
output mode | MODE7, see Pin_Configuration.pdf in BBB */
;
};
};
};
fragment@1 {
target = ocp;/* not sure why it is not gpio0
*/
__overlay__ {
status = okay;
pinctrl-names = default;
pinctrl-0 = bb_mygpio_pins;
};
};
};
I was able to build the dtc and generated MY-LED-00A0.dtbo
I then copied the MY-LED-00A0.dtbo to /lib/firmware
Then i echoed it to slots:
echo MY-LED $SLOTS
and cat $SLOTS gives me below result:
root@beaglebone:/lib/firmware# cat $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
9: ff:P-O-L Override Board Name,00A0,Override Manuf,MY-LED
By looks of this, MY_LED seems to be loaded...
The main confusion is how can I use MY-LED?
Where are the files for MY-LED present?
Any help or guidance is much appreciated.
--
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 javascript:.
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] very quick questions: startup of lxde, exports, usb babble, and shutdown
dear bbb experts: robert nelson's debian-lxde-7.7 image [1] is it possible first to boot to a console, and then to start lxde with startx? (I looked for /etc/init.d/lx*, but there was nothing there.) [2] the mass storage driver exports its BEAGLEBONE partition, seemingly as a whole device (not as a partition). thus, the host computer mounts /dev/sdb (if there is only one other sda) with the BBB's 96MB partition. I looked in /etc/* whether I could find what enables this behavior, but failed. [3] the log tells me about musb Babble interrupts to its host (powering) computer. I have tried this on multiple bbb's and cables. is this normal? (I also wonder if there could still be some gremlins in the USB drivers. if I plug a keyboard into the host bbb port, and then I try a couple of times to insert/remove the BBB gadget port connection, it doesn't connect the mass storage any longer. maybe the keyboard is defective, but the ports are different.) [4] how does lxde shut down? the command line shutdown now and reboot -p do not do it for me. but the gui lxde powerdown does. /iaw -- 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.
