[beagleboard] Loading custom capes on Debian
Hello there, I am suing bbb and a Debian Console image. I am strying to locate the place where the tree overlays are located but I cant. I tried greping for BB-UART1 for example but I cant find it. Even though I can export it to slots. I have added my custom cape to /lib/firmware/ but when I try to export it to slots it cannot find the file. In the regular image all tree-overlays are stotred in /lib/firmware/ and in my image that folder is empty. I would really aprichiate any help, this is very urgent for me and I dont have much time :( -- 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] Loading custom capes on Debian
What kernel are you using? (what is the output from uname -a ?) On Mon, Nov 24, 2014 at 12:11 AM, bremenpl breme...@gmail.com wrote: Hello there, I am suing bbb and a Debian Console image. I am strying to locate the place where the tree overlays are located but I cant. I tried greping for BB-UART1 for example but I cant find it. Even though I can export it to slots. I have added my custom cape to /lib/firmware/ but when I try to export it to slots it cannot find the file. In the regular image all tree-overlays are stotred in /lib/firmware/ and in my image that folder is empty. I would really aprichiate any help, this is very urgent for me and I dont have much time :( -- 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] Loading custom capes on Debian
root@beaglebone:/# uname -a Linux beaglebone 3.8.13-bone64 #1 SMP Thu Aug 21 21:24:58 UTC 2014 armv7l GNU/Linux W dniu 2014-11-24 o 09:20, Jason Lange pisze: What kernel are you using? (what is the output from uname -a ?) On Mon, Nov 24, 2014 at 12:11 AM, bremenpl breme...@gmail.com mailto:breme...@gmail.com wrote: Hello there, I am suing bbb and a Debian Console image. I am strying to locate the place where the tree overlays are located but I cant. I tried greping for BB-UART1 for example but I cant find it. Even though I can export it to slots. I have added my custom cape to /lib/firmware/ but when I try to export it to slots it cannot find the file. In the regular image all tree-overlays are stotred in /lib/firmware/ and in my image that folder is empty. I would really aprichiate any help, this is very urgent for me and I dont have much time :( -- 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 mailto: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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/DwM-75kDnRc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Bremenpl -- 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] Loading custom capes on Debian
I don't have much experience with device tree overlays so I might not be able to help, but what is the exact command you are using to echo it into the slot? On Mon, Nov 24, 2014 at 12:24 AM, Bremenpl breme...@gmail.com wrote: root@beaglebone:/# uname -a Linux beaglebone 3.8.13-bone64 #1 SMP Thu Aug 21 21:24:58 UTC 2014 armv7l GNU/Linux W dniu 2014-11-24 o 09:20, Jason Lange pisze: What kernel are you using? (what is the output from uname -a ?) On Mon, Nov 24, 2014 at 12:11 AM, bremenpl breme...@gmail.com wrote: Hello there, I am suing bbb and a Debian Console image. I am strying to locate the place where the tree overlays are located but I cant. I tried greping for BB-UART1 for example but I cant find it. Even though I can export it to slots. I have added my custom cape to /lib/firmware/ but when I try to export it to slots it cannot find the file. In the regular image all tree-overlays are stotred in /lib/firmware/ and in my image that folder is empty. I would really aprichiate any help, this is very urgent for me and I dont have much time :( -- 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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/DwM-75kDnRc/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. -- Bremenpl -- 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] Loading custom capes on Debian
root@beaglebone:/sys/devices/bone_capemgr.9# echo BB-BONELT_HDMIN1 slots -bash: echo: write error: No such file or directory For some reason he doesnt see my .dtbo file in lib/firmware/ but or the other hand there are no other .dtbo files there. They are somewhere, because I can echo BB-UART1 for example, I just cant figue out where. I dont know where to put my .dtbo file or how to enable /lib/firmware/ directory for .dtbo files W dniu 2014-11-24 o 09:50, Jason Lange pisze: I don't have much experience with device tree overlays so I might not be able to help, but what is the exact command you are using to echo it into the slot? On Mon, Nov 24, 2014 at 12:24 AM, Bremenpl breme...@gmail.com mailto:breme...@gmail.com wrote: root@beaglebone:/# uname -a Linux beaglebone 3.8.13-bone64 #1 SMP Thu Aug 21 21:24:58 UTC 2014 armv7l GNU/Linux W dniu 2014-11-24 o 09:20, Jason Lange pisze: What kernel are you using? (what is the output from uname -a ?) On Mon, Nov 24, 2014 at 12:11 AM, bremenpl breme...@gmail.com mailto:breme...@gmail.com wrote: Hello there, I am suing bbb and a Debian Console image. I am strying to locate the place where the tree overlays are located but I cant. I tried greping for BB-UART1 for example but I cant find it. Even though I can export it to slots. I have added my custom cape to /lib/firmware/ but when I try to export it to slots it cannot find the file. In the regular image all tree-overlays are stotred in /lib/firmware/ and in my image that folder is empty. I would really aprichiate any help, this is very urgent for me and I dont have much time :( -- 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 mailto: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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/DwM-75kDnRc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Bremenpl -- 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 mailto: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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/DwM-75kDnRc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Bremenpl -- 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] Change I2C bus for video communication
Okay, I have managed to load the tree overlay by hand from /lib/firmware/. What was wrong was that I havent followed the naming style. I have changed the name of .dtbo file to BB-BONELT-HDMIN1-00A0.dtbo and I could load the tree overlay by hand. Although, the overlay didnt want to load automatically after placing an apropriate line in uEnv.txt. root@beaglebone:/sys/devices/bone_capemgr.9# dmesg | grep .dtbo [0.680671] bone-capemgr bone_capemgr.9: slot #7: Requesting part number/version based 'BB-BONELT-HDMIN1-00A0.dtbo [0.680686] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 'BB-BONELT-HDMIN1-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [0.994941] bone-capemgr bone_capemgr.9: failed to load firmware 'BB-BONELT-HDMIN1-00A0.dtbo' [1.013699] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware 'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0' [1.013715] bone-capemgr bone_capemgr.9: slot #4: dtbo 'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree [ 102.139293] bone-capemgr bone_capemgr.9: slot #8: Requesting part number/version based 'BB-BONELT-HDMIN1-00A0.dtbo [ 102.139310] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware 'BB-BONELT-HDMIN1-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 102.142979] bone-capemgr bone_capemgr.9: slot #8: dtbo 'BB-BONELT-HDMIN1-00A0.dtbo' loaded; converting to live tree I am not sure if I turned off the standard HDMI overlay, I just commented the enables lines in uEnv.txt, now my slots file looks like this: root@beaglebone:/sys/devices/bone_capemgr.9# 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 I have loaded the HDMIN1 tree overlay by hand, because it failed to load at boot. I dont know if thats the case but I got no visual on the monitor connected to my external hdmi circuit. I have tried changing and the recompiling it for both I2C1 and I2C2 as I was not sure whats the proper naming style. The I2C 1 in software is I2C2 on header (that is the bus i am connected to using hdmi socket). i2c = i2c1; I dont know now either the problem lies in the hardware I have created or the wrongly configured software. I would really aprichiate any help in this matter. I have copied the circuit for HDMI nearly fully from HDMI circuit for Beaglebone Mx so it seems to be correct. I have also soldered everything really carefully. I would really really aprichiate some more help. W dniu 2014-11-21 o 17:06, Robert Nelson pisze: On Fri, Nov 21, 2014 at 10:04 AM, Bremenpl breme...@gmail.com wrote: I am not very good at tree overlays, but from the one you have provided me i believe i would be abble to reduce it only to modify the LCD pins (I also need to disable mcasp, because I only use video and the pins for mcasp are used as other peripherals). I thing I tried to find the place in this code that turns off the I2C-0 and turns on I2C-1 but I couldnt. The non-audio varient is here: https://github.com/beagleboard/linux/blob/3.8/firmware/capes/cape-boneblack-hdmin-00A0.dts#L94 Regards, -- Bremenpl -- 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] Change I2C bus for video communication
I am not sure if I turned off the standard HDMI overlay, I just commented the enables lines in uEnv.txt, now my slots file looks like this: root@beaglebone:/sys/devices/bone_capemgr.9# 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 You have disabled the HDMI overlays, if they were loaded the relevant slots (5 and 6) would start with ff:P-O-L as it does for slot 4. (I believe the L stands for Loaded) -- 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] Change I2C bus for video communication
If you want to load a custom cape at boot you need to follow these instructions: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Loading_custom_capes On Mon, Nov 24, 2014 at 1:46 AM, Jason Lange j.b.la...@gmail.com wrote: I am not sure if I turned off the standard HDMI overlay, I just commented the enables lines in uEnv.txt, now my slots file looks like this: root@beaglebone:/sys/devices/bone_capemgr.9# 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 You have disabled the HDMI overlays, if they were loaded the relevant slots (5 and 6) would start with ff:P-O-L as it does for slot 4. (I believe the L stands for Loaded) -- 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] Change I2C bus for video communication
In that case after the disabling I have enabled my module by hand (BB-BONELT-HDMIN1): root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN 9: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONELT-HDMIN1 But i still get no visual on the attached monitor :(. The monitor is in standby so he doesnt get any signal. W dniu 2014-11-24 o 10:46, Jason Lange pisze: I am not sure if I turned off the standard HDMI overlay, I just commented the enables lines in uEnv.txt, now my slots file looks like this: root@beaglebone:/sys/devices/bone_capemgr.9# mailto:root@beaglebone:/sys/devices/bone_capemgr.9# 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 You have disabled the HDMI overlays, if they were loaded the relevant slots (5 and 6) would start with ff:P-O-L as it does for slot 4. (I believe the L stands for Loaded) -- 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/qQTZm20XGoo/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Bremenpl -- 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] Change I2C bus for video communication
On Mon, Nov 24, 2014 at 1:52 AM, Bremenpl breme...@gmail.com wrote: In that case after the disabling I have enabled my module by hand (BB-BONELT-HDMIN1): root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN 9: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONELT-HDMIN1 But i still get no visual on the attached monitor :(. The monitor is in standby so he doesnt get any signal. :( I wish you the best of luck. It's 2am here so I'm going to bed. -- 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] Change I2C bus for video communication
Thanks for help with the boot loading of tree overlay, it works. But monitor still doesnt display anything :/. At least I know its not because of loading after boot. W dniu 2014-11-24 o 10:56, Jason Lange pisze: On Mon, Nov 24, 2014 at 1:52 AM, Bremenpl breme...@gmail.com mailto:breme...@gmail.com wrote: In that case after the disabling I have enabled my module by hand (BB-BONELT-HDMIN1): root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN 9: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONELT-HDMIN1 But i still get no visual on the attached monitor :(. The monitor is in standby so he doesnt get any signal. :( I wish you the best of luck. It's 2am here so I'm going to bed. -- 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/qQTZm20XGoo/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Bremenpl -- 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 UART async_low_latency does not seem to work. still 10ms latency!
Hi all i am writing some software using the OMAP_SERIAL drivers to send and receive data from a c program (TERMIOS). I am seeing large delays 10ms ticks when sending and receiving data on the UARTS. In the normal linux driver there is a option called ASYNC_LOW_LATENCY. When i am setting this flag via IOCTL i was expecting this latency to drop. But it seems ti be ignored by the OMAP_SERIAL driver. I have tried to set the option both via the following code snippet and via the STTY command line interface. Any information on this or any way to get the latency down would be much appreciated. /Thomas -- 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] Change I2C bus for video communication
Some update on the progress: I figured out that I have switched SDA and SCL lines for the monitor connection through HDMI. I have flipped that to proper position and I can see additional devices on the bus: root@beaglebone:~# i2cdetect -y -r 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- 4a 4b -- -- -- -- 50: 50 -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 60: -- 61 -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@beaglebone:~# 0x20 - I/O expander 0x61 - external DAC 0x68 - RTC clock 0x20, 0x37, 0x3a, 0x4a, 0x4b and 0x50 appear after I connect the monitor ro hdmi connector. I think I have figured out that I have to put i2c = i2c2; in the overlay file, as I think it reffers to the hardware number. Now when I boot BeagleBone Black in the debug console I see: . . . Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.338954] omap2_mbox_probe: platform not supported [0.493953] tps65217-bl tps65217-bl: no platform data provided [0.558115] bone-capemgr bone_capemgr.9: slot #0: No cape found [0.595223] bone-capemgr bone_capemgr.9: slot #1: No cape found [0.632332] bone-capemgr bone_capemgr.9: slot #2: No cape found [0.662506] bone-capemgr bone_capemgr.9: bone: Invalid signature '825a93cf' at slot 3 [0.670687] bone-capemgr bone_capemgr.9: slot #3: No cape found [0.689417] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [0.751741] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [0.763488] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [0.770796] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single Loading, please wait... systemd-fsck[210]: rootfs: clean, 21580/04 files, 121672/444160 blocks systemd-fsck[326]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN systemd-fsck[326]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters [6.224809] libphy: PHY 4a101000.mdio:01 not found [6.229881] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 10.703450] dummy 1-0034: Error -121 writing to cec:0xff [ 10.740063] tda998x 1-0070: Error -121 reading from 0xa [ 10.781054] tda998x 1-0070: Error -121 writing to 0xa [ 10.837748] tda998x 1-0070: Error -121 reading from 0xa [ 10.861162] tda998x 1-0070: Error -121 writing to 0xa [ 10.917824] tda998x 1-0070: Error -121 reading from 0x1 [ 10.941245] tda998x 1-0070: Error -121 writing to 0x1 [ 10.972464] tda998x 1-0070: Error -121 reading from 0x1 [ 11.003772] tda998x 1-0070: Error -121 writing to 0x1 [ 11.029803] tda998x 1-0070: Error -121 writing to REG_CURPAGE [ 11.065182] tda998x 1-0070: Error -121 writing to 0x200 [ 11.095575] tda998x 1-0070: Error -121 writing to 0x201 [ 11.128734] tda998x 1-0070: Error -121 writing to 0x202 [ 11.165874] tda998x 1-0070: Error -121 writing to 0x203 [ 11.189995] tda998x 1-0070: Error -121 writing to 0x204 [ 11.217379] tda998x 1-0070: Error -121 writing to 0x205 [ 11.230326] tda998x 1-0070: Error -121 writing to 0x20e [ 11.242030] tda998x 1-0070: Error -121 writing to 0x211 [ 11.253725] tda998x 1-0070: Error -121 writing to 0x207 [ 11.260694] tda998x 1-0070: Error -121 writing to 0x208 [ 11.271538] tda998x 1-0070: Error -121 writing to 0x209 [ 11.284844] tda998x 1-0070: Error -121 writing to 0x20a [ 11.294595] tda998x 1-0070: Error -121 writing to 0x206 [ 11.305084] tda998x 1-0070: Error -121 writing to REG_CURPAGE [ 11.313653] tda998x 1-0070: Error -121 reading from 0x0 [ 11.319751] tda998x 1-0070: Error -121 reading from 0x2 [ 11.328249] tilcdc 4830e000.fb: no encoders/connectors found [ 11.334233] tilcdc 4830e000.fb: failed to initialize mode setting Debian GNU/Linux 7 beaglebone ttyO0 default username:password is [debian:temppwd] Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian The IP Address for eth0 is: 10.10.10.37 The IP Address for usb0 is: 192.168.7.2 beaglebone login: There are some errors regarding reading data from TDA chip. When i placed i2c1 in the tree overlay file it just said one line about hdmi i2c problem. Looking forward to your answer. -- Bremenpl -- 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: [Issue] BeagleBone Black Random Reboot
Hey i do have some updates regarding this! We have now ran 10 bbb boards with a strap between 5v vcc and the v+ input on the USB connector. These now all have an uprime of 10+ days. The controls that are powered from the same power supply but do not have the strap has an average uptime of 8-9 hours. This makes me think that this has to do with the driver initialisation of the PMIC. I am hoping that this information will help someone to continue the research in the restart/ reboot problem. -- 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] Change I2C bus for video communication
I wonder, Maybe there has to be more software changed than only tree overlay for i2c? I am using the chip that BeagleboneMx used. It doesnt use hotplug and CEC for example... -- 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: BeagleBone PCB stackup
Graham, John, Thanks for the comments. I finally found the layer stackup document for the BBB (revB4). Strangely enough I could not find it in a readable format from: http://elinux.org/Beagleboard:BeagleBoneBlack#Hardware_Files I found it at the below page for an older BBB version: https://github.com/SweedJesus/Beaglebone-Black-Stuff/tree/master/Docs/Beaglebone%20Black/BBB_PCB/BeagleBone_Black_RevB4_MFG From the beaglebone_black_RevB4_NOLOGO_FAB.pdf enclosed file looking at the different info I can see: - TOP and BOTTOM layers are:1/2 oz + 150 microinches of plating (ie 0.150 mils) - INNER layers are: 1 oz which seems different from what is defined from the BBB Altium PCB stackup (beaglebone_black_RevB4.pcbDoc): - TOP and BOTTOM layers are: 2.4 mils - Inner layers are: 1.2 mils Using the below convert 1/2 oz should be 0.88 mils and 1 oz 1.37 mils: http://www.referencedesigner.com/cal/cal_02.php Am I missing something in the oz to mils conversion? Even if the Layer stack-up table from the .pdf file says that all dimension are in INCHES it looks like that the that it is oz and mils instead. In both document the total board height is 62 mils. AnBer On Wednesday, February 8, 2012 9:00:30 AM UTC+1, manatarms wrote: Dear All Does someone have the stackup of the BeagleBone PCB? I couldn't find it on the hardware design page and it would help many people who want to do their own design. -- 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. BeagleBone_Black_RevB4_FAB.pdf Description: Adobe PDF document
[beagleboard] Kernel 3.13 and above: How to enable dcan_1 and GPIOs
Hi folks! For some reasons (mainly the kernel support for IEEE 802.11s) I need to use Debian (kernel 3.13 or higher; I’m currently running 3.16.1-bone4) on my BBB. For my project, I will also use the CAN interface of the BBB and some IO pins (mainly for LEDs and switches...). This is my first BBB project so I searched the web for the easiest / best solution for using the GPIO pins of my BBBs. In many tutorials about BBB GPIO and can-bus the use of the capemgr is suggested. But as you all know there is no capemgr in 3.16. Now I would really need your help to find the best way to enable the can-bus (dcan_1) and also control some other GPIO pins. Can I do this from userspace some how? Or do I have to reconfigure and rebuild the kernel? @GPIO pins: I think the easiest solution is to use echo [GPIO No.] /sys/class/gpio/export and then set the value direction etc. using echo. Am I right here? Thanks a lot for your help and hints, Marco -- 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: USB-Hub: unable to enumerate USB device
Hi,
I am still stuck with this problem. I found out, that the hardware is
definitely working - even with a Raspberry Pi running a 3.6.11 kernel the
USB hub is recogniced, so I am sure it is a software issue.
I updated to the latest kernel version in rcn-ee.net jessie repository
(3.18.0-rc6-bone1). With this kernel, I don't receive those unable to
enumerate USB device errors anymore, but while booting up I get the
following timeout:
udevadm settle - timeout of 120 seconds reached, the event queue contains:
/sys/devices/ocp/4740.usb/47401c00.usb/musb-hdrc.1.auto/usb1 (1431)
/sys/devices/ocp/4740.usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-0:1.0 (
1432)
I see, that there is a USB-Hub cape available (
http://elinux.org/USB_HUB_Cape). Does anybody know what chip they are using
- or does anybody have experiences with a USB hub chip that is working with
the BeagleBone Black? I found an I/O cape from Titan
(http://www.titan.tw/product/USB_2COM_BB.html) which is built on a chip
from Genesys Logic. The powered usb hub I have here and that is working
well, is built on a chip from Cypress (CY7C65640-LFC). So I could just have
a new pcb board designed which is built on one of those chips and forget
about the SMSC chip, but I cannot believe, that one of the most popular usb
hub chips of all is just not working with the BeagleBone Black.
I don't know anymore what else to try. I'd be glad for any advice...
Best regards,
Stefan
Am Mittwoch, 12. November 2014 23:25:28 UTC+2 schrieb Stefan Feilmeier:
Hello,
Please help me with the following problem. I am not much of a
hardware-expert, but till now I was able to resolve quite all of my
BeagleBone Black related problems with the extensive information available
online. Only with this problem I am now stuck for days...
I got a custom (not by me) made board providing a USB-Hub (from SMSC) and
a USB-to-RS485 (FTDI) converter. When I connect it to the the Beaglebone
Black on its USB-Host interface I constantly get messages like the
following, with the device number counting up forever:
[ 17.600794] usb 1-1: new high-speed USB device number 25 using
musb-hdrc
[ 17.673073] hub 1-0:1.0: unable to enumerate USB device on port 1
Also no leds are turning on on the custom board. The Beaglebone is running
on Debian with the following kernel - but I also tried without success
another Beaglebone Black with a more recent kernel.
root@debian:~# uname -a
Linux debian 3.8.13-bone67 #1 SMP Wed Sep 24 18:32:44 UTC 2014 armv7l
GNU/Linux
When I connect the same board via USB to a Linux laptop, it works
perfectly fine with the following messages, including the custom boards'
leds turning on:
usb 1-3: new high-speed USB device number 3 using ehci-pci
usb 1-3: New USB device found, idVendor=0424, idProduct=2514
usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-3:1.0: USB hub found
hub 1-3:1.0: 4 ports detected
usb 1-3.4: new full-speed USB device number 4 using ehci-pci
usb 1-3.4: New USB device found, idVendor=0403, idProduct=6015
usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-3.4: Product: FT230X Basic UART
usb 1-3.4: Manufacturer: FTDI
...
Also on a Windows Machine the board works fine. Results of usbview.exe:
[Port2] : Generic USB Hub
External Hub:
USB#VID_0424PID_2514#6109c578c02#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
Is Port User Connectable: yes
Is Port Debug Capable:no
Companion Port Number:0
Companion Hub Symbolic Link Name:
Protocols Supported:
USB 1.1: yes
USB 2.0: yes
USB 3.0: no
Hub Power:Self Power
Hub type: USB 2.0 Hub
Number of Ports: 4
Power switching: Individual
Compound device: Yes
Over-current Protection: Individual
High speed capable: Yes
High speed: Yes
Multiple transaction translations capable: Yes
Performs multiple transaction translations simultaneously: Yes
Hub wakes when device is connected:No
Hub is bus powered: No
Hub is root: No
---===Device Information===---
ConnectionStatus:
Current Config Value: 0x01 - Device Bus Speed: High (is
not SuperSpeed or higher capable)
Device Address:0x02
Open Pipes: 1
===Device Descriptor===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0200
bDeviceClass: 0x09 - This is a HUB Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x02
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor:0x0424 = SMSC
idProduct:
[beagleboard] Re: USB-Hub: unable to enumerate USB device
Hi,
sorry for spaming the mailinglist. Out of desperation I just tried one more
experiment. If I attach the powered usb hub directly to the BeagleBone
and connect my custom made usb hub on the powered usb hub, I receive
the following messages:
[ 49.784746] usb 1-1.1: device not accepting address 11, error -71
[ 50.794745] usb 1-1.1: device not accepting address 14, error -71
...
[ 55.144832] hub 1-1.1:1.0: hub_port_status failed (err = -71)
[ 55.151082] hub 1-1.1:1.0: hub_port_status failed (err = -71)
...
[ 55.399949] hub 1-1.1:1.0: activate -- -19
Any clue?
Thanks for any answer.
Best regards,
Stefan
Am Montag, 24. November 2014 14:51:17 UTC+2 schrieb Stefan Feilmeier:
Hi,
I am still stuck with this problem. I found out, that the hardware is
definitely working - even with a Raspberry Pi running a 3.6.11 kernel the
USB hub is recogniced, so I am sure it is a software issue.
I updated to the latest kernel version in rcn-ee.net jessie repository
(3.18.0-rc6-bone1). With this kernel, I don't receive those unable to
enumerate USB device errors anymore, but while booting up I get the
following timeout:
udevadm settle - timeout of 120 seconds reached, the event queue contains:
/sys/devices/ocp/4740.usb/47401c00.usb/musb-hdrc.1.auto/usb1 (1431)
/sys/devices/ocp/4740.usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-0:1.0
(1432)
I see, that there is a USB-Hub cape available (
http://elinux.org/USB_HUB_Cape). Does anybody know what chip they are
using - or does anybody have experiences with a USB hub chip that is
working with the BeagleBone Black? I found an I/O cape from Titan (
http://www.titan.tw/product/USB_2COM_BB.html) which is built on a chip
from Genesys Logic. The powered usb hub I have here and that is working
well, is built on a chip from Cypress (CY7C65640-LFC). So I could just have
a new pcb board designed which is built on one of those chips and forget
about the SMSC chip, but I cannot believe, that one of the most popular usb
hub chips of all is just not working with the BeagleBone Black.
I don't know anymore what else to try. I'd be glad for any advice...
Best regards,
Stefan
Am Mittwoch, 12. November 2014 23:25:28 UTC+2 schrieb Stefan Feilmeier:
Hello,
Please help me with the following problem. I am not much of a
hardware-expert, but till now I was able to resolve quite all of my
BeagleBone Black related problems with the extensive information available
online. Only with this problem I am now stuck for days...
I got a custom (not by me) made board providing a USB-Hub (from SMSC) and
a USB-to-RS485 (FTDI) converter. When I connect it to the the Beaglebone
Black on its USB-Host interface I constantly get messages like the
following, with the device number counting up forever:
[ 17.600794] usb 1-1: new high-speed USB device number 25 using
musb-hdrc
[ 17.673073] hub 1-0:1.0: unable to enumerate USB device on port 1
Also no leds are turning on on the custom board. The Beaglebone is
running on Debian with the following kernel - but I also tried without
success another Beaglebone Black with a more recent kernel.
root@debian:~# uname -a
Linux debian 3.8.13-bone67 #1 SMP Wed Sep 24 18:32:44 UTC 2014 armv7l
GNU/Linux
When I connect the same board via USB to a Linux laptop, it works
perfectly fine with the following messages, including the custom boards'
leds turning on:
usb 1-3: new high-speed USB device number 3 using ehci-pci
usb 1-3: New USB device found, idVendor=0424, idProduct=2514
usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-3:1.0: USB hub found
hub 1-3:1.0: 4 ports detected
usb 1-3.4: new full-speed USB device number 4 using ehci-pci
usb 1-3.4: New USB device found, idVendor=0403, idProduct=6015
usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-3.4: Product: FT230X Basic UART
usb 1-3.4: Manufacturer: FTDI
...
Also on a Windows Machine the board works fine. Results of usbview.exe:
[Port2] : Generic USB Hub
External Hub:
USB#VID_0424PID_2514#6109c578c02#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
Is Port User Connectable: yes
Is Port Debug Capable:no
Companion Port Number:0
Companion Hub Symbolic Link Name:
Protocols Supported:
USB 1.1: yes
USB 2.0: yes
USB 3.0: no
Hub Power:Self Power
Hub type: USB 2.0 Hub
Number of Ports: 4
Power switching: Individual
Compound device: Yes
Over-current Protection: Individual
High speed capable: Yes
High speed: Yes
Multiple transaction translations capable: Yes
Performs multiple transaction translations simultaneously: Yes
Hub wakes when device is connected:No
Hub is bus powered: No
Hub is
Re: [beagleboard] Re: BeagleBone PCB stackup
AnBer: I realize that it is in writing on the Internet, therefore it must be true. But, the board as documented by SweedJesus is a non-standard and unusual construction for PC boards, therefore there is a slight chance that the information is wrong. I would suggest that you use the dimensions suggested by myself and John. Please also realize that the dimensions and parameters in building PC boards that affect your EM modeling are typically +/- 10 percent, sometimes +/- 20 percent, so do not spend a lot of time chasing decimal places for the input to your modeling program. --- Graham == On Mon, Nov 24, 2014 at 6:12 AM, AnBer ant.bert...@gmail.com wrote: Graham, John, Thanks for the comments. I finally found the layer stackup document for the BBB (revB4). Strangely enough I could not find it in a readable format from: http://elinux.org/Beagleboard:BeagleBoneBlack#Hardware_Files I found it at the below page for an older BBB version: https://github.com/SweedJesus/Beaglebone-Black-Stuff/tree/master/Docs/Beaglebone%20Black/BBB_PCB/BeagleBone_Black_RevB4_MFG From the beaglebone_black_RevB4_NOLOGO_FAB.pdf enclosed file looking at the different info I can see: - TOP and BOTTOM layers are:1/2 oz + 150 microinches of plating (ie 0.150 mils) - INNER layers are: 1 oz which seems different from what is defined from the BBB Altium PCB stackup (beaglebone_black_RevB4.pcbDoc): - TOP and BOTTOM layers are: 2.4 mils - Inner layers are: 1.2 mils Using the below convert 1/2 oz should be 0.88 mils and 1 oz 1.37 mils: http://www.referencedesigner.com/cal/cal_02.php Am I missing something in the oz to mils conversion? Even if the Layer stack-up table from the .pdf file says that all dimension are in INCHES it looks like that the that it is oz and mils instead. In both document the total board height is 62 mils. AnBer On Wednesday, February 8, 2012 9:00:30 AM UTC+1, manatarms wrote: Dear All Does someone have the stackup of the BeagleBone PCB? I couldn't find it on the hardware design page and it would help many people who want to do their own design. -- 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/OUpHBFIA1uc/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 to Enable Beaglebone Black Power On Self-Test (POST)?
Hi Hanks, It seems that it is not supported. Please see the official response from TI below. http://e2e.ti.com/support/embedded/linux/f/354/p/374578/1318202.aspx Thanks, Lei On Friday, November 21, 2014 4:30:42 PM UTC-5, Hanks wrote: Hi, Lei: Did you get the answer? I just want to do the similar thing... Thanks On Thursday, October 9, 2014 12:50:30 PM UTC-7, Lei Wang wrote: Hi, I need to perform memory test at BBB boot. I'd like to perform memory POST test as documented in doc/README.memory-test. However I have difficulty to enable the tests. u-boot version: u-boot-2013.10 I added below (3) lines to the file am335x_evm.h to enable memory POST. #define CONFIG_POST #define CONFIG_SYS_POST_MEMORY #define CONFIG_SYS_POST_MEM_REGIONS I've got errors when I build: ... include/post.h:60:2: error: #error _POST_WORD_ADDR currently not implemented for this platform! . It seems that post,h file suggests that am335x platform is not supported by POST. I wonder if someone could give me some guidance on this topic. Thanks a lot! Lei Wang PS I also tried with the latest u-boot release (v2014.10-rc3). I got the same error. -- 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: building X-loader (MLO) from source for an xM Rev C board
Could you tell me whether what kind of Issue I would have after running make CROSS_COMPILE=arm-none-linux-gnueabi- ift I'm getting two error, which is pertaining to arm gcc and the other is Error 127 start.io On Wednesday, 18 May 2011 15:23:52 UTC-7, Jerry Doty wrote: I am building MLO from source using the following commands (codesourcery 2009q1 tool-chain): git clone git://gitorious.org/x-load-omap3/mainline.git x-loader cd x-loader make CROSS_COMPILE=arm-none-linux-gnueabi- distclean make CROSS_COMPILE=arm-none-linux-gnueabi- omap3530beagle_config make CROSS_COMPILE==arm-none-linux-gnueabi- ift This creates an x-load.bin.ift file which I rename to MLO and install to a microSD card following the instructions given at http://elinux.org/BeagleBoardBeginners. The board boots and I get the standard U-boot banner of: U-Boot 2010.03 (May 18 2011 - 14:27:48) OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, OMAP3 Beagle board + LPDDR/NAND .. But I don't get an X-loader banner. Instead of seeing: Texas Instruments X-Loader 1.4.4ss (Mar 8 2011 - 08:51:11) Beagle xM Reading boot sector Loading u-boot.bin from mmc I get garbage printed to the console. When I replace the MLO file I generated with the binary that shipped with the board, it works. Has anyone hand luck re-building X-Loader (MLO) for the xM Rev C board? If so, can you please offer some advice? -- 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: 3.17.1-rc4 sudden reset
I have just ported Linux kernel 3.17.3 to our board. This stops the system going into OTG probing when the g_ether module is loaded. It still does a single OTG probe when initially loaded but there is no every 2 seconds probe. If this fixes things for all USB modules, I don't know and I don't know in which kernel version between 3.12.10 and 3.17.3 it was fixed. Not sure if the vanilla kernel 3.17.3 will work on the Beaglebone. -- 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 using Debian 3.13 (without capemgr) - how to enable can-bus and work with GPIO
Hi folks! For some reasons (mainly the kernel support for IEEE 802.11s) I need to use Debian (kernel 3.13 or higher; I’m currently running 3.16.1-bone4) on my BBB. For my project, I will also use the CAN interface of the BBB and some IO pins (mainly for LEDs and switches...). This is my first BBB project so I searched the web for the easiest / best solution for using the GPIO pins of my BBBs. In many tutorials about BBB GPIO and can-bus the use of the capemgr is suggested. But as you all know there is no capemgr in 3.16. Now I would really need your help to find the best way to enable the can-bus (dcan_1) and also control some other GPIO pins. Can I do this from userspace some how? Or do I have to reconfigure and rebuild the kernel? Thanks a lot for your help and hints, Marco -- 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 to Enable Beaglebone Black Power On Self-Test (POST)?
There is no power on self test on the board. Gerald On Mon, Nov 24, 2014 at 8:19 AM, lxw6...@njit.edu wrote: Hi Hanks, It seems that it is not supported. Please see the official response from TI below. http://e2e.ti.com/support/embedded/linux/f/354/p/374578/1318202.aspx Thanks, Lei On Friday, November 21, 2014 4:30:42 PM UTC-5, Hanks wrote: Hi, Lei: Did you get the answer? I just want to do the similar thing... Thanks On Thursday, October 9, 2014 12:50:30 PM UTC-7, Lei Wang wrote: Hi, I need to perform memory test at BBB boot. I'd like to perform memory POST test as documented in doc/README.memory-test. However I have difficulty to enable the tests. u-boot version: u-boot-2013.10 I added below (3) lines to the file am335x_evm.h to enable memory POST. #define CONFIG_POST #define CONFIG_SYS_POST_MEMORY #define CONFIG_SYS_POST_MEM_REGIONS I've got errors when I build: ... include/post.h:60:2: error: #error _POST_WORD_ADDR currently not implemented for this platform! . It seems that post,h file suggests that am335x platform is not supported by POST. I wonder if someone could give me some guidance on this topic. Thanks a lot! Lei Wang PS I also tried with the latest u-boot release (v2014.10-rc3). I got the same error. -- 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/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.
[beagleboard] BBB as router Ethernet to other peripherals
Hello, could anyone direct me to right way of doing BBB as Virtual router. Main functions it will be doing are: - receive data packets already encapsulated in IPv6+UDP headers from it's peripherals, - will need to send these packets to server defined in these headers destination address fields, - receive packets from server, - send them to designated device on its peripherals according to receiver address. So far my biggest question is how can I on BBB connect to some server and send him that data which I received so server would send me back reply (would know that source address is within my local network), also ideally as I understand server application should receive already unwrapped RAW data which was sent to BBB already in IPv6+UDP header. Thank you in advance for any valuable replies. Laurynas. -- 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.
It appears that the issue is known for a long time: several registers of the LAN8710A Ethernet transceiver sometimes get wrong values at power-up, in spite of correct pin strapping configurations. One of those wrong values is PHYAD (PHY address in the Special Modes Register), which is erroneously initialized to 2, while the processor expects it to be 0. This makes it impossible for the processor to communicate with the transceiver and override those wrong values. Here http://e2e.ti.com/support/arm/sitara_arm/f/791/t/335017.aspx, they suggest that this issue is inherent in the LAN8710A by Microchip, and may be caused by some interference from the clock signal. However, Microchip did not admit that. The messages within this topic propose 3 main solutions: 1) Rebuilt the device tree to make it somehow work with a PHY address that can take on 0 or 2, or probably some other values 2) Remove C24 capacitor (this is not safe) 3) Change the file drivers/net/ethernet/ti/davinci_mdio.c and rebuild the Linux (this patch, as far as I understand, will update the device tree in such a way that other, non-zero PHY addresses, will become also acceptable) I have tried to do another thing: to rewrite wrong register values with U-Boot, using commands like mdio write 2 18 0xe0, and I managed to make the content of those registers looking like that of a successfully started transceiver (including the PHYAD and MODE). However, to successfully apply these changes, a reset with RESET button is required. And if I just run reset command in U-Boot, the transceiver doesn't work properly after reboot, even though it already has the right PHY address: 0. In this case the registers look like as if the auto-negotiation fails, and as if the link partner (i.e. the processor) doesn't have auto-negotiation ability (the Auto Negotiation Expansion Register contains 0). If that worked, it would be possible to append all required rewriting commands into bootcmd variable, thus forcing U-Boot to rewrite wrong values automatically. But there is another obstacle on this way: the U-boot I have (2014.10-dirty) does not have saveenv command, for some reason. So, I cannot save any changes in environmental variables there. If anyone solved this problem by modifying the device tree or by some U-Boot script, please share the details. On Monday, November 24, 2014 8:18:31 AM UTC+1, Jerin George wrote: As suggested in this discussion i moved to 3.14.1 kernel and everything went well for the first 48 hours. After that i could see that the ETH stopped responding for close to 10 seconds. Then it came back. Test set up:- I'm using BBB for Data acquisition thru ETH. For testing i have connected BBB and 2 PC in a switch. One PC is running a data acquisition software to collect data from BBB. Another PC is running the software Total Network Monitor and it keeps on logging the Network status by pinging to both BBB the other PC. After 48 Hours :- I could see that the Total Network monitor reported that link to BBB was lost for close to 10 seconds. Is this a known issue ? Is there any fix to this. regards, Jerin On Saturday, 22 November 2014 14:25:03 UTC+5:30, alexschn...@gmail.com wrote: But the SW can do that only when the transceiver chip is always in a writable state, which is unfortunately not the case. On Saturday, November 22, 2014 1:38:54 AM UTC+1, Gerald wrote: All the SW has to do itvwrite to the registers and not rely on the straps. Hmm I have been saying that for 3+ years now. Gerald On Friday, November 21, 2014, alexschn...@gmail.com wrote: Hi Gerald, I meant strap values, not connections on the board. As far as I understand it, correct strappings alone cannot always ensure correct bits in the respective registers of the transceiver chip. The power-on and reset timing is also important, and this timing, unlike strappings, is different at least for some revisions. In my experiments, a reset performed with RESET button never resolved the phy not found problem. A power-on reset as well as a reset with POWER button helped, but not always. Cannot the transceiver sometimes enter into some unresponsive state, which makes it impossible for the processor to override the strappings? Alex On Thursday, November 20, 2014 9:50:56 PM UTC+1, Gerald wrote: If you have what you think are he correct trappings, let me know. They are the same for all revisions. Also, if you reset the board after it is up, the strappings are overridden by the states on those pins from the processor that override the strapping options. Gerald On Thu, Nov 20, 2014 at 12:39 PM, alexschn...@gmail.com wrote: Hello, This Ethernet trouble also happens with my BeagleBone Black boards, quite frequently on Rev C (PCB Rev B6), and very rarely on Rev A6 (PCB Rev B5). I tried various Linux kernels, including the latest one from here
Re: [beagleboard] Send Raw or hex data out the serial port using bonescript
On Sat, Nov 22, 2014 at 7:49 PM, John Mladenik john5...@sbcglobal.net
wrote:
So it worked but once I let the board sit not being powered overnight it
stopped working. Do you or anyone know how to get the UART2 working and
stay working once powered down and then turned back on?
Once power cycled, you would need to start up the program again so that the
serial port could be properly opened for writing. I would have the
bonescript code in, say, /home/debian/doSerial.js, and run that
automatically on every reboot. There are a number of ways to do this. One
quick way is try to add a line in /etc/crontab to run this command on
@reboot:
@reboot rootcd /home/debian
NODE_PATH=/usr/local/lib/node_modules export NODE_PATH doSerial.js
Assuming you are using debian image, /dev/ttyO1 and /dev/ttyO2 have
rw-rw--- as their permission. So you either need to run it as root or add
your desired user to the dialout group to be able to write to these serial
interfaces.
If doSerial.js crashes for any reason, you could use a process monitor to
restart it. Supervisord http://supervisord.org/, forever
https://github.com/nodejitsu/forever, pm2 https://github.com/Unitech/pm2,
are some options to explore.
On Wednesday, November 19, 2014 3:44:26 PM UTC-8, George Lu wrote:
On Wed, Nov 19, 2014 at 3:26 PM, John Mladenik john...@sbcglobal.net
wrote:
I need to be able to send raw data out of the serial port using
Bonescript command b.serialWrite.I set up an HTML Bonescript to send
data and then looked on the logic analyzer to see what bit pattern is sent
out. The pattern is always the ASCII value of the character whether the
variable is a text or number.
Does anyone know how to pass to b.serialWrite a value so that the UART
outputs that value?
so I want to have
var port = '/dev/ttyO2'; // set UART port
var data = 0x55 ;
b.serialWrite(port, data );
and for the bit pattern coming out of the UART to be 01010101
I tried using String.fromCharCode(data); but this only works for
values up to 127 (0x7F) since that is all ASCII goes to. This must not
support extended ASCII?
here is my html/javascript to test this functionality
html
body
Uart Byte:br
input type=number name=value id='value'/
button onclick=uartWr()SEND/button
/body
head
script src=/bonescript.js/script
script
function uartWr() {
var b = require('bonescript');
var port = '/dev/ttyO2'; // set UART port
var data = document.getElementById('value').value;
// set baud rate and buffer size
var options = {
baudrate: 9600
};
b.serialWrite(port, data );
}
/script
/head
/html
I recall BoneScript uses https://github.com/voodootikigod/node-serialport
for serial port interface.
You should be able to send raw binary with b.serialWrite(port, [0x55]);
Data should be a buffer (http://nodejs.org/api/buffer.html).
--
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.
[beagleboard] TLV320AIC3104 Sample rate problem
Hello, I'm using an Audio Cape Rev. B connected to BeagleBone Black (MCLK=12MHz) and I'm trying to record audio at sample rate 8KHz. Recording and playback using ALSA is OK, but when playing the recorded samples on PC you can hear that the actual sample rate is lower (the pitch shifted to a lower tone). I have added debug messages throughout the alsa driver tlv320aic3x.c, and I found out that the PLL parameters are computed correctly as in TLV320AIC3104 Datasheet Table found at page 27. (p: 1 j: 8 d: 1920 r: 1). Has anyone else encountered a problem like this? Can someone with more experience check the driver? Kernel: https://github.com/beagleboard/linux , commit 2bcc89c, 3.14.19+. Best regards, Catalin Crenguta -- 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] Issue when building kernel for Beagleboard Black
Thank you very much, it works fine now. I think, it might be usefull to indicate this in your web page. Is it also possible to build the initrd during the building process? Regards -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Shutdown PMIC
Hi, Is there a way to shutdown the PMIC after a system shutdown, if there is a battery, See this link and the patch ... https://groups.google.com/forum/#!searchin/beagleboard/power$20down$20battery/beagleboard/K7DuusrJ6G4/WqgYqwoH9gkJ With linux-dev-3.8.13-bone67 there isn't arch/arm/mach-omap2/board-am335xevm.c !? How to do the modification ? 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.
Re: [beagleboard] Issue when building kernel for Beagleboard Black
On Mon, Nov 24, 2014 at 10:09 AM, Eric L laeuf...@gmail.com wrote: Thank you very much, it works fine now. I think, it might be usefull to indicate this in your web page. Is it also possible to build the initrd during the building process? If you build 'on' target you can generate the initrd... Just the way it is.. 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] Where is i2c_smbus_xxxx_xxx() functions?
Dear forum, I have now verified my I2C devices using Python. I need to re-code them in C. I find i2c driver dokumented here: https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/i2c/dev-interface The documentation complies with my 3.8.13-bone67 compiled and installed kernel source (KERNEL/drivers/i2c/i2c-core.c) Problem: No file in /usr/include/* contains the prototypes for the documented *i2c_smbus__()* functions. I can open/read/write to the /dev/i2c-x devices using standard read(), write() and ioctl(), but I find no higher level i2c functions. What is my problem? Please advice. Best regards Terje Froysa -- 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] Loading custom capes on Debian
I suspect it is a problem with your dtbo file. I believe that some of the dtbo files that used to be installed in /lib/firmware have been essentially compiled in to the kernel in an attempt to fix some other issues. My dtbo for my XBee cape is still in /lib/firmware and it works fine. Doesn't automatically load off EEPROM at boot, but the running echo XbeeFullCape0001/sys/devices/bone_capemgr.9/slots as root works. On Mon, Nov 24, 2014 at 3:57 AM, Bremenpl breme...@gmail.com wrote: root@beaglebone:/sys/devices/bone_capemgr.9# echo BB-BONELT_HDMIN1 slots -bash: echo: write error: No such file or directory For some reason he doesnt see my .dtbo file in lib/firmware/ but or the other hand there are no other .dtbo files there. They are somewhere, because I can echo BB-UART1 for example, I just cant figue out where. I dont know where to put my .dtbo file or how to enable /lib/firmware/ directory for .dtbo files W dniu 2014-11-24 o 09:50, Jason Lange pisze: I don't have much experience with device tree overlays so I might not be able to help, but what is the exact command you are using to echo it into the slot? On Mon, Nov 24, 2014 at 12:24 AM, Bremenpl breme...@gmail.com wrote: root@beaglebone:/# uname -a Linux beaglebone 3.8.13-bone64 #1 SMP Thu Aug 21 21:24:58 UTC 2014 armv7l GNU/Linux W dniu 2014-11-24 o 09:20, Jason Lange pisze: What kernel are you using? (what is the output from uname -a ?) On Mon, Nov 24, 2014 at 12:11 AM, bremenpl breme...@gmail.com wrote: Hello there, I am suing bbb and a Debian Console image. I am strying to locate the place where the tree overlays are located but I cant. I tried greping for BB-UART1 for example but I cant find it. Even though I can export it to slots. I have added my custom cape to /lib/firmware/ but when I try to export it to slots it cannot find the file. In the regular image all tree-overlays are stotred in /lib/firmware/ and in my image that folder is empty. I would really aprichiate any help, this is very urgent for me and I dont have much time :( -- 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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/DwM-75kDnRc/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. -- Bremenpl -- 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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/DwM-75kDnRc/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. -- Bremenpl -- 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] Loading custom capes on Debian
On Mon, Nov 24, 2014 at 2:57 AM, Bremenpl breme...@gmail.com wrote: root@beaglebone:/sys/devices/bone_capemgr.9# echo BB-BONELT_HDMIN1 slots -bash: echo: write error: No such file or directory btw: `dmesg | tail` will give you more info one the error above.. For some reason he doesnt see my .dtbo file in lib/firmware/ but or the other hand there are no other .dtbo files there. They are somewhere, because I can echo BB-UART1 for example, I just cant figue out where. I dont know where to put my .dtbo file or how to enable /lib/firmware/ directory for .dtbo files They are built in.. 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] Loading custom capes on Debian
I have solved the issue, the problem was the naming. Thank you. Now I struggle with the hdmi: https://groups.google.com/forum/embed/?place=forum/beagleboardshowsearch=trueshowpopout=trueshowtabs=truehideforumtitle=trueparenturl=http%3A%2F%2Fbeagleboard.org%2FCommunity%2FForums%2F#!searchin/beagleboard/Change$20I2C$20bus$20for$20video$20communication/beagleboard/qQTZm20XGoo/nR44xDiBCb8J W dniu 2014-11-24 o 17:47, Robert Nelson pisze: On Mon, Nov 24, 2014 at 2:57 AM, Bremenpl breme...@gmail.com wrote: root@beaglebone:/sys/devices/bone_capemgr.9# echo BB-BONELT_HDMIN1 slots -bash: echo: write error: No such file or directory btw: `dmesg | tail` will give you more info one the error above.. For some reason he doesnt see my .dtbo file in lib/firmware/ but or the other hand there are no other .dtbo files there. They are somewhere, because I can echo BB-UART1 for example, I just cant figue out where. I dont know where to put my .dtbo file or how to enable /lib/firmware/ directory for .dtbo files They are built in.. Regards, -- Bremenpl -- 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] What's the size of blue LEDs on BBB?
What's the size of those blue SMD LEDs that are on BBB? 1206? 0805? -- 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] What's the size of blue LEDs on BBB?
On 24-11-2014 18:52, Energia wrote: What's the size of those blue SMD LEDs that are on BBB? 1206? 0805? -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. Probably 0603 ? -- Bas -- 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] expand rootfs to sd card.
thanks, works now. On Sunday, November 23, 2014 9:14:56 PM UTC-5, RobertCNelson wrote: On Sun, Nov 23, 2014 at 7:52 PM, earless gunc...@gmail.com javascript: wrote: I booted from an sdcard and ran the following commands grow the partition to the entire size of the sdcard(16GB) sudo cd /opt/scripts/tools sudo git pull sudo ./grow_partition.sh sudo shutdown -r now after reboot i ran df -h but the rootfs shows its size as 1.6G and im using 1.5G. I was expecting to see size at around 16G so I dont think it expanded the partition. am i missing something?? Try again, with a 16GB card, it'll take a little bit for the 'expand' function to work on extX.. 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] Change I2C bus for video communication
On Mon, Nov 24, 2014 at 5:28 AM, Bremenpl breme...@gmail.com wrote: Some update on the progress: I figured out that I have switched SDA and SCL lines for the monitor connection through HDMI. I have flipped that to proper position and I can see additional devices on the bus: root@beaglebone:~# i2cdetect -y -r 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- 4a 4b -- -- -- -- 50: 50 -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 60: -- 61 -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@beaglebone:~# 0x20 - I/O expander 0x61 - external DAC 0x68 - RTC clock 0x20, 0x37, 0x3a, 0x4a, 0x4b and 0x50 appear after I connect the monitor ro hdmi connector. I think I have figured out that I have to put i2c = i2c2; in the overlay file, as I think it reffers to the hardware number. Now when I boot BeagleBone Black in the debug console I see: . . . Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.338954] omap2_mbox_probe: platform not supported [0.493953] tps65217-bl tps65217-bl: no platform data provided [0.558115] bone-capemgr bone_capemgr.9: slot #0: No cape found [0.595223] bone-capemgr bone_capemgr.9: slot #1: No cape found [0.632332] bone-capemgr bone_capemgr.9: slot #2: No cape found [0.662506] bone-capemgr bone_capemgr.9: bone: Invalid signature '825a93cf' at slot 3 [0.670687] bone-capemgr bone_capemgr.9: slot #3: No cape found [0.689417] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [0.751741] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [0.763488] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [0.770796] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single Loading, please wait... systemd-fsck[210]: rootfs: clean, 21580/04 files, 121672/444160 blocks systemd-fsck[326]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN systemd-fsck[326]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters [6.224809] libphy: PHY 4a101000.mdio:01 not found [6.229881] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 10.703450] dummy 1-0034: Error -121 writing to cec:0xff [ 10.740063] tda998x 1-0070: Error -121 reading from 0xa [ 10.781054] tda998x 1-0070: Error -121 writing to 0xa [ 10.837748] tda998x 1-0070: Error -121 reading from 0xa [ 10.861162] tda998x 1-0070: Error -121 writing to 0xa [ 10.917824] tda998x 1-0070: Error -121 reading from 0x1 [ 10.941245] tda998x 1-0070: Error -121 writing to 0x1 [ 10.972464] tda998x 1-0070: Error -121 reading from 0x1 [ 11.003772] tda998x 1-0070: Error -121 writing to 0x1 [ 11.029803] tda998x 1-0070: Error -121 writing to REG_CURPAGE [ 11.065182] tda998x 1-0070: Error -121 writing to 0x200 [ 11.095575] tda998x 1-0070: Error -121 writing to 0x201 [ 11.128734] tda998x 1-0070: Error -121 writing to 0x202 [ 11.165874] tda998x 1-0070: Error -121 writing to 0x203 [ 11.189995] tda998x 1-0070: Error -121 writing to 0x204 [ 11.217379] tda998x 1-0070: Error -121 writing to 0x205 [ 11.230326] tda998x 1-0070: Error -121 writing to 0x20e [ 11.242030] tda998x 1-0070: Error -121 writing to 0x211 [ 11.253725] tda998x 1-0070: Error -121 writing to 0x207 [ 11.260694] tda998x 1-0070: Error -121 writing to 0x208 [ 11.271538] tda998x 1-0070: Error -121 writing to 0x209 [ 11.284844] tda998x 1-0070: Error -121 writing to 0x20a [ 11.294595] tda998x 1-0070: Error -121 writing to 0x206 [ 11.305084] tda998x 1-0070: Error -121 writing to REG_CURPAGE [ 11.313653] tda998x 1-0070: Error -121 reading from 0x0 [ 11.319751] tda998x 1-0070: Error -121 reading from 0x2 why are you still pointing to the tda998x driver? https://github.com/beagleboard/linux/blob/3.8/Documentation/devicetree/bindings/drm/tilcdc/tfp410.txt#L16 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] GPIO Header Pins that can be muxed to the PRU
From what I can tell, there are just a few pins on the expansion headers that can be mapped into R30/R31 of the PRU units. If you are using the LCD or HDMI (I'm using 4DCape-43T) and eMMC, most of the pins are allocated. PRU0 has 7 pins for direct mapping PRU1 has 1 pin for input only. Header pin : PRU? outreg-bit, inreg-bit - usage P9-31: PRU0 R30-0, R31-0 - available for use P9-29: PRU0 R30-1, R31-1 - available for use P9-30: PRU0 R30-2, R31-2 - used by LCD P9-28: PRU0 R30-3, R31-3 - available for use P9-42: PRU0 R30-4, R31-4 - available for use P9-27: PRU0 R30-5, R31-5 - used by LCD P9-41: PRU0 R30-6, R31-6 - available for use P9-25: PRU0 R30-7, R31-7 - available for use P8-12: PRU0 R30-14- used by eMMC P8-16: PRU0 R31-14- used by eMMC P8-11: PRU0 R30-15- used by eMMC P8-15: PRU0 R31-15- used by eMMC P9-24: PRU0 R31-16- used by LCD P9-41: PRU0 R31-16- available for use P8-45: PRU1 R30-0, R31-0 - used by LCD P8-46: PRU1 R30-1, R31-1 - used by LCD P8-43: PRU1 R30-2, R31-2 - used by LCD P8-44: PRU1 R30-3, R31-3 - used by LCD P8-41: PRU1 R30-4, R31-4 - used by LCD P8-42: PRU1 R30-5, R31-5 - used by LCD P8-39: PRU1 R30-6, R31-6 - used by LCD P8-40: PRU1 R30-7, R31-7 - used by LCD P8-27: PRU1 R30-8, R31-8 - used by LCD P8-29: PRU1 R30-9, R31-9 - used by LCD P8-28: PRU1 R30-10, R31-10 - used by LCD P8-30: PRU1 R30-11, R31-11 - used by LCD P8-21: PRU1 R30-12, R31-12 - used by LCD P8-20: PRU1 R30-13, R31-13 - used by LCD P9-26: PRU1 R31-16 - available for use I was hoping to get 10 pins (8 out, 2 in) mapped to PRU0 registers for fast access. Will I have to use memory mapped access to get 10 GPIO pins? Are there tricks to the PRU pin mapping I'm missing? 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] Re: [Issue] BeagleBone Black Random Reboot
I think I have found the reason for this. See the 3.17.1-rc4 sudden reset https://groups.google.com/forum/#%21category-topic/beagleboard/beaglebone-black/RMOTnQBgIo8 thread. On Monday, November 24, 2014 11:28:17 AM UTC, Thomas O wrote: Hey i do have some updates regarding this! We have now ran 10 bbb boards with a strap between 5v vcc and the v+ input on the USB connector. These now all have an uprime of 10+ days. The controls that are powered from the same power supply but do not have the strap has an average uptime of 8-9 hours. This makes me think that this has to do with the driver initialisation of the PMIC. I am hoping that this information will help someone to continue the research in the restart/ reboot problem. -- 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] Extend GPIO
Hello all ! What is the best way to play with 96 gpio on the beagle board black ? I have not found cape to extend gpio ... I need to receive 80 contact closure. TIA cre4tix -- 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] Extend GPIO
Can you build a custom cape? Using 10 74HC165 chips (parallel in / serial out cascadable) and the Beaglebone SPI would do it. -- 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] Change I2C bus for video communication
Do I have to place this part:
dvicape {
compatible = ti,tilcdc,tfp410;
i2c = i2c2;
pinctrl-names = default;
pinctrl-0 = bone_dvi_cape_dvi_00A1_pins;
powerdn-gpio = gpio2 31 0;
};
In the overlay file you have provided me erlier instead of HDMI part? Or
do I have to get rid of more? I am not sure which parts exacly can go.
W dniu 2014-11-24 o 20:55, Robert Nelson pisze:
On Mon, Nov 24, 2014 at 5:28 AM, Bremenpl breme...@gmail.com wrote:
Some update on the progress:
I figured out that I have switched SDA and SCL lines for the monitor
connection through HDMI. I have flipped that to proper position and I can
see additional devices on the bus:
root@beaglebone:~# i2cdetect -y -r 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: 30 -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- 4a 4b -- -- -- --
50: 50 -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: -- 61 -- -- -- -- -- -- 68 -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@beaglebone:~#
0x20 - I/O expander
0x61 - external DAC
0x68 - RTC clock
0x20, 0x37, 0x3a, 0x4a, 0x4b and 0x50 appear after I connect the monitor ro
hdmi connector.
I think I have figured out that I have to put i2c = i2c2; in the overlay
file, as I think it reffers to the hardware number.
Now when I boot BeagleBone Black in the debug console I see:
.
.
.
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[0.338954] omap2_mbox_probe: platform not supported
[0.493953] tps65217-bl tps65217-bl: no platform data provided
[0.558115] bone-capemgr bone_capemgr.9: slot #0: No cape found
[0.595223] bone-capemgr bone_capemgr.9: slot #1: No cape found
[0.632332] bone-capemgr bone_capemgr.9: slot #2: No cape found
[0.662506] bone-capemgr bone_capemgr.9: bone: Invalid signature
'825a93cf' at slot 3
[0.670687] bone-capemgr bone_capemgr.9: slot #3: No cape found
[0.689417] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset'
failed
[0.751741] pinctrl-single 44e10800.pinmux: pin 44e10854 already
requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[0.763488] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
-22
[0.770796] pinctrl-single 44e10800.pinmux: could not request pin 21 on
device pinctrl-single
Loading, please wait...
systemd-fsck[210]: rootfs: clean, 21580/04 files, 121672/444160 blocks
systemd-fsck[326]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
systemd-fsck[326]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters
[6.224809] libphy: PHY 4a101000.mdio:01 not found
[6.229881] net eth0: phy 4a101000.mdio:01 not found on slave 1
[ 10.703450] dummy 1-0034: Error -121 writing to cec:0xff
[ 10.740063] tda998x 1-0070: Error -121 reading from 0xa
[ 10.781054] tda998x 1-0070: Error -121 writing to 0xa
[ 10.837748] tda998x 1-0070: Error -121 reading from 0xa
[ 10.861162] tda998x 1-0070: Error -121 writing to 0xa
[ 10.917824] tda998x 1-0070: Error -121 reading from 0x1
[ 10.941245] tda998x 1-0070: Error -121 writing to 0x1
[ 10.972464] tda998x 1-0070: Error -121 reading from 0x1
[ 11.003772] tda998x 1-0070: Error -121 writing to 0x1
[ 11.029803] tda998x 1-0070: Error -121 writing to REG_CURPAGE
[ 11.065182] tda998x 1-0070: Error -121 writing to 0x200
[ 11.095575] tda998x 1-0070: Error -121 writing to 0x201
[ 11.128734] tda998x 1-0070: Error -121 writing to 0x202
[ 11.165874] tda998x 1-0070: Error -121 writing to 0x203
[ 11.189995] tda998x 1-0070: Error -121 writing to 0x204
[ 11.217379] tda998x 1-0070: Error -121 writing to 0x205
[ 11.230326] tda998x 1-0070: Error -121 writing to 0x20e
[ 11.242030] tda998x 1-0070: Error -121 writing to 0x211
[ 11.253725] tda998x 1-0070: Error -121 writing to 0x207
[ 11.260694] tda998x 1-0070: Error -121 writing to 0x208
[ 11.271538] tda998x 1-0070: Error -121 writing to 0x209
[ 11.284844] tda998x 1-0070: Error -121 writing to 0x20a
[ 11.294595] tda998x 1-0070: Error -121 writing to 0x206
[ 11.305084] tda998x 1-0070: Error -121 writing to REG_CURPAGE
[ 11.313653] tda998x 1-0070: Error -121 reading from 0x0
[ 11.319751] tda998x 1-0070: Error -121 reading from 0x2
why are you still pointing to the tda998x driver?
https://github.com/beagleboard/linux/blob/3.8/Documentation/devicetree/bindings/drm/tilcdc/tfp410.txt#L16
Regards,
--
Bremenpl
--
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] Change I2C bus for video communication
On Mon, Nov 24, 2014 at 2:13 PM, Bremenpl breme...@gmail.com wrote:
Do I have to place this part:
dvicape {
compatible = ti,tilcdc,tfp410;
i2c = i2c2;
pinctrl-names = default;
pinctrl-0 = bone_dvi_cape_dvi_00A1_pins;
powerdn-gpio = gpio2 31 0;
};
In the overlay file you have provided me erlier instead of HDMI part? Or do
I have to get rid of more? I am not sure which parts exacly can go.
compatible = ti,tilcdc,tfp410;
Chooses the tfp410 driver...
--
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: Extend GPIO
Or, building on Peter's idea, consider using six each TI PCA9555. 16 inputs or outputs per IC, I2C interface, all can share the same I2C bus they are per-pin configurable. including generating an interrupt on state change of any or all I/O pins. Or search on TI web site for bus extender PCA9555 Remote 16-Bit I2C And SMBus I/O Expander With Interrupt Output And Configuration Registers I/O data rates would be limited to what you can push through an I2C bus. --- Graham == On Monday, November 24, 2014 11:07:22 AM UTC-6, cre4tix wrote: Hello all ! What is the best way to play with 96 gpio on the beagle board black ? I have not found cape to extend gpio ... I need to receive 80 contact closure. TIA cre4tix -- 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] Change I2C bus for video communication
This is the output on debug serial now:
.
.
.Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[0.338981] omap2_mbox_probe: platform not supported
[0.493971] tps65217-bl tps65217-bl: no platform data provided
[0.558187] bone-capemgr bone_capemgr.9: slot #0: No cape found
[0.595295] bone-capemgr bone_capemgr.9: slot #1: No cape found
[0.632402] bone-capemgr bone_capemgr.9: slot #2: No cape found
[0.669512] bone-capemgr bone_capemgr.9: slot #3: No cape found
[0.688174] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset'
failed
[0.749856] pinctrl-single 44e10800.pinmux: pin 44e10854 already
requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[0.761544] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8)
status -22
[0.768813] pinctrl-single 44e10800.pinmux: could not request pin 21
on device pinctrl-single
Loading, please wait...
systemd-fsck[205]: rootfs: clean, 21581/04 files, 122520/444160 blocks
systemd-fsck[290]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
systemd-fsck[290]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters
[6.507830] tilcdc 4830e000.fb: no encoders/connectors found
[6.513806] tilcdc 4830e000.fb: failed to initialize mode setting
There is still no visual. It says:
... tilcdc..
Does that mean hes not using the driver for tfp410?
Also, could you please confirm either the I2C2 in the tree overlay is
the I2C2 on the header? I am still not certain.
W dniu 2014-11-24 o 21:12, Robert Nelson pisze:
On Mon, Nov 24, 2014 at 2:13 PM, Bremenpl breme...@gmail.com wrote:
Do I have to place this part:
dvicape {
compatible = ti,tilcdc,tfp410;
i2c = i2c2;
pinctrl-names = default;
pinctrl-0 = bone_dvi_cape_dvi_00A1_pins;
powerdn-gpio = gpio2 31 0;
};
In the overlay file you have provided me erlier instead of HDMI part? Or do
I have to get rid of more? I am not sure which parts exacly can go.
compatible = ti,tilcdc,tfp410;
Chooses the tfp410 driver...
--
Bremenpl
--
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] Change I2C bus for video communication
On Mon, Nov 24, 2014 at 2:34 PM, Bremenpl breme...@gmail.com wrote: This is the output on debug serial now: . . .Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.338981] omap2_mbox_probe: platform not supported [0.493971] tps65217-bl tps65217-bl: no platform data provided [0.558187] bone-capemgr bone_capemgr.9: slot #0: No cape found [0.595295] bone-capemgr bone_capemgr.9: slot #1: No cape found [0.632402] bone-capemgr bone_capemgr.9: slot #2: No cape found [0.669512] bone-capemgr bone_capemgr.9: slot #3: No cape found [0.688174] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [0.749856] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [0.761544] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [0.768813] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single Loading, please wait... systemd-fsck[205]: rootfs: clean, 21581/04 files, 122520/444160 blocks systemd-fsck[290]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN systemd-fsck[290]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters [6.507830] tilcdc 4830e000.fb: no encoders/connectors found [6.513806] tilcdc 4830e000.fb: failed to initialize mode setting There is still no visual. It says: ... tilcdc.. Does that mean hes not using the driver for tfp410? Also, could you please confirm either the I2C2 in the tree overlay is the I2C2 on the header? I am still not certain. Verfiy: https://github.com/derekmolloy/boneDeviceTree/tree/master/docs 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] Change I2C bus for video communication
I know those sheets. Even thought it says that pinumux is I2C2, in the software for i2ctools i reffer to nr 1 not nr 2. Thats why I am confused. W dniu 2014-11-24 o 21:36, Robert Nelson pisze: On Mon, Nov 24, 2014 at 2:34 PM, Bremenpl breme...@gmail.com wrote: This is the output on debug serial now: . . .Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.338981] omap2_mbox_probe: platform not supported [0.493971] tps65217-bl tps65217-bl: no platform data provided [0.558187] bone-capemgr bone_capemgr.9: slot #0: No cape found [0.595295] bone-capemgr bone_capemgr.9: slot #1: No cape found [0.632402] bone-capemgr bone_capemgr.9: slot #2: No cape found [0.669512] bone-capemgr bone_capemgr.9: slot #3: No cape found [0.688174] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [0.749856] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [0.761544] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [0.768813] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single Loading, please wait... systemd-fsck[205]: rootfs: clean, 21581/04 files, 122520/444160 blocks systemd-fsck[290]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN systemd-fsck[290]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters [6.507830] tilcdc 4830e000.fb: no encoders/connectors found [6.513806] tilcdc 4830e000.fb: failed to initialize mode setting There is still no visual. It says: ... tilcdc.. Does that mean hes not using the driver for tfp410? Also, could you please confirm either the I2C2 in the tree overlay is the I2C2 on the header? I am still not certain. Verfiy: https://github.com/derekmolloy/boneDeviceTree/tree/master/docs Regards, -- Bremenpl -- 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] Change I2C bus for video communication
is the tilcdc part correct? W dniu 2014-11-24 o 21:36, Robert Nelson pisze: On Mon, Nov 24, 2014 at 2:34 PM, Bremenpl breme...@gmail.com wrote: This is the output on debug serial now: . . .Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.338981] omap2_mbox_probe: platform not supported [0.493971] tps65217-bl tps65217-bl: no platform data provided [0.558187] bone-capemgr bone_capemgr.9: slot #0: No cape found [0.595295] bone-capemgr bone_capemgr.9: slot #1: No cape found [0.632402] bone-capemgr bone_capemgr.9: slot #2: No cape found [0.669512] bone-capemgr bone_capemgr.9: slot #3: No cape found [0.688174] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [0.749856] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [0.761544] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [0.768813] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single Loading, please wait... systemd-fsck[205]: rootfs: clean, 21581/04 files, 122520/444160 blocks systemd-fsck[290]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN systemd-fsck[290]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters [6.507830] tilcdc 4830e000.fb: no encoders/connectors found [6.513806] tilcdc 4830e000.fb: failed to initialize mode setting There is still no visual. It says: ... tilcdc.. Does that mean hes not using the driver for tfp410? Also, could you please confirm either the I2C2 in the tree overlay is the I2C2 on the header? I am still not certain. Verfiy: https://github.com/derekmolloy/boneDeviceTree/tree/master/docs Regards, -- Bremenpl -- 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
Below are some handy links for creating custom builds of OpenJDK and OpenJFX. - Building OpenJFX https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX - Building OpenJFX For ARM https://wiki.openjdk.java.net/display/OpenJFX/Cross+Building+for+ARM+Hard+Float - Official Debian GIT For OpenJFX https://github.com/Debian/openjfx (GIT Hub) - How To Build And Package OpenJDK 8 With OpenJFX On Linux https://github.com/hgomez/obuildfactory/wiki/How-to-build-and-package-OpenJDK-8-with-OpenJFX-on-Linux (x86 only) H Looks as though Debian officially has some packaging for OpenJFX, however they would need to also have packaging for OpenJDK 8 too in order for OpenJFX to work. Wonder if the packaging targets x86 only or if it extends to ARM as well. Robert - If you have time can you please look into this one. On Monday, 24 November 2014 09:44:00 UTC+13, RobertCNelson wrote: On Sun, Nov 23, 2014 at 2:06 PM, Nick Apperley napp...@gmail.com javascript: wrote: Managed to get OpenJFX (open source version of JavaFX) working on the BBB, however it is running on Ubuntu. Got a sample JavaFX program (Ensemble) working by accident on X11 by specifying a renderer that isn't supported by OpenJFX. Key part here is that you must specify the unsupported renderer otherwise no JavaFX program will start, and some errors will appear in the terminal. Automatic renderer detection with OpenJFX is currently broken. Hey Nick, I'd love to see your setup that got it working on ubuntu. I can setup a *.deb package on: http://repos.rcn-ee.net/ 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
Wonder if the OpenJFX package (package name?) has been uploaded to the Debian Unstable repository yet. On Tuesday, 25 November 2014 10:02:35 UTC+13, Nick Apperley wrote: Below are some handy links for creating custom builds of OpenJDK and OpenJFX. - Building OpenJFX https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX - Building OpenJFX For ARM https://wiki.openjdk.java.net/display/OpenJFX/Cross+Building+for+ARM+Hard+Float - Official Debian GIT For OpenJFX https://github.com/Debian/openjfx (GIT Hub) - How To Build And Package OpenJDK 8 With OpenJFX On Linux https://github.com/hgomez/obuildfactory/wiki/How-to-build-and-package-OpenJDK-8-with-OpenJFX-on-Linux (x86 only) H Looks as though Debian officially has some packaging for OpenJFX, however they would need to also have packaging for OpenJDK 8 too in order for OpenJFX to work. Wonder if the packaging targets x86 only or if it extends to ARM as well. Robert - If you have time can you please look into this one. On Monday, 24 November 2014 09:44:00 UTC+13, RobertCNelson wrote: On Sun, Nov 23, 2014 at 2:06 PM, Nick Apperley napp...@gmail.com wrote: Managed to get OpenJFX (open source version of JavaFX) working on the BBB, however it is running on Ubuntu. Got a sample JavaFX program (Ensemble) working by accident on X11 by specifying a renderer that isn't supported by OpenJFX. Key part here is that you must specify the unsupported renderer otherwise no JavaFX program will start, and some errors will appear in the terminal. Automatic renderer detection with OpenJFX is currently broken. Hey Nick, I'd love to see your setup that got it working on ubuntu. I can setup a *.deb package on: http://repos.rcn-ee.net/ 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
On Mon, Nov 24, 2014 at 3:08 PM, Nick Apperley napper...@gmail.com wrote: Wonder if the OpenJFX package (package name?) has been uploaded to the Debian Unstable repository yet. It's there: https://packages.qa.debian.org/o/openjfx.html Just a few build errors: https://buildd.debian.org/status/package.php?p=openjfxsuite=unstable 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
Thanks for the update. Damm, oh well there is the option to do a custom OpenJFX build. Hardest part is to do a custom build of OpenJDK 8 for ARM. Having great difficulty in tracking down good documentation in this area, specifically for the ARM side. Might be worth looking at the CACAO and JamVM JREs (Java 8 compatible?) and seeing if they will be compatible with the OpenJFX runtime. On Tuesday, 25 November 2014 10:12:24 UTC+13, RobertCNelson wrote: On Mon, Nov 24, 2014 at 3:08 PM, Nick Apperley napp...@gmail.com javascript: wrote: Wonder if the OpenJFX package (package name?) has been uploaded to the Debian Unstable repository yet. It's there: https://packages.qa.debian.org/o/openjfx.html Just a few build errors: https://buildd.debian.org/status/package.php?p=openjfxsuite=unstable 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
On Mon, Nov 24, 2014 at 3:25 PM, Nick Apperley napper...@gmail.com wrote: Thanks for the update. Damm, oh well there is the option to do a custom OpenJFX build. Hardest part is to do a custom build of OpenJDK 8 for ARM. Having great difficulty in tracking down good documentation in this area, specifically for the ARM side. Might be worth looking at the CACAO and JamVM JREs (Java 8 compatible?) and seeing if they will be compatible with the OpenJFX runtime. well less errors on armhf than openjfx. ;) https://buildd.debian.org/status/package.php?p=openjdk-8suite=unstable 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
Is there a successful build of OpenJDK 8u20 for armhf? On Tuesday, 25 November 2014 10:35:43 UTC+13, RobertCNelson wrote: On Mon, Nov 24, 2014 at 3:25 PM, Nick Apperley napp...@gmail.com javascript: wrote: Thanks for the update. Damm, oh well there is the option to do a custom OpenJFX build. Hardest part is to do a custom build of OpenJDK 8 for ARM. Having great difficulty in tracking down good documentation in this area, specifically for the ARM side. Might be worth looking at the CACAO and JamVM JREs (Java 8 compatible?) and seeing if they will be compatible with the OpenJFX runtime. well less errors on armhf than openjfx. ;) https://buildd.debian.org/status/package.php?p=openjdk-8suite=unstable 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
On Mon, Nov 24, 2014 at 3:57 PM, Nick Apperley napper...@gmail.com wrote: Is there a successful build of OpenJDK 8u20 for armhf? I'll fire up a build and see. ;) 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
Thanks for that. Discovered that JamVM isn't an actual JRE since it relies on the class libraries which are available in OpenJDK. JamVM is only a JVM (Java Virtual Machine). From the outset JamVM *might* be able to run JavaFX programs since it is compatible with OpenJDK 8. IcedTea (OpenJDK derivative) uses JamVM as its JVM. Originally JamVM was designed to perform well on very resource constrained embedded devices. Now JamVM can be used on Linux PCs (x86/AMD64). On Tuesday, 25 November 2014 10:59:26 UTC+13, RobertCNelson wrote: On Mon, Nov 24, 2014 at 3:57 PM, Nick Apperley napp...@gmail.com javascript: wrote: Is there a successful build of OpenJDK 8u20 for armhf? I'll fire up a build and see. ;) 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
Hopefully if the custom build of OpenJDK 8 works then that can be adjusted to work on the stable Debian/Ubuntu images for the BBB. On Tuesday, 25 November 2014 10:59:26 UTC+13, RobertCNelson wrote: On Mon, Nov 24, 2014 at 3:57 PM, Nick Apperley napp...@gmail.com javascript: wrote: Is there a successful build of OpenJDK 8u20 for armhf? I'll fire up a build and see. ;) 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
On Mon, Nov 24, 2014 at 4:21 PM, Nick Apperley napper...@gmail.com wrote: Hopefully if the custom build of OpenJDK 8 works then that can be adjusted to work on the stable Debian/Ubuntu images for the BBB. If the test build goes thru, i'll just add it to: https://github.com/rcn-ee/repos So it'll end up on repos.rcn-ee.net :) 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: JavaFX 8 on BeagleBone Black (SGX driver problem?)
Excellent, highly appreciated :) On Tuesday, 25 November 2014 11:23:20 UTC+13, RobertCNelson wrote: On Mon, Nov 24, 2014 at 4:21 PM, Nick Apperley napp...@gmail.com javascript: wrote: Hopefully if the custom build of OpenJDK 8 works then that can be adjusted to work on the stable Debian/Ubuntu images for the BBB. If the test build goes thru, i'll just add it to: https://github.com/rcn-ee/repos So it'll end up on repos.rcn-ee.net :) 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: Starting Up Programs Automatically With LXDE
Seems as though there is some strange differences in behaviour going on between the ARM version of LXDE and the x86 version with the way programs are automatically started, specifically the Java ones. Would it be possible to have Robert Nelson look into this issue with LXDE? On Thursday, 20 November 2014 13:15:06 UTC+13, William Hermans wrote: Eric, perhaps this is a post worthy of stackoverlfow ? There are plenty of very knowledgeable individuals who may have had similar experience with embedded versus PC Java implementations. I honestly do not know much about Java in either case, but my gut instinct tells me this problem has to do with the different platform implementations. On Wed, Nov 19, 2014 at 4:06 PM, Charles Steinkuehler cha...@steinkuehler.net javascript: wrote: On 11/19/2014 2:29 AM, Eric Apperley wrote: - this command, when added to the shell script in the user's home directory does not successfully execute on the Beaglebone (it does on a PC running LUbuntu): java -jar /home/organ/jOrgan-3_20/jorgan.jar I don't know what might be causing your particular problem, but looking at your command above some generic *nix debugging tips come to mind: * Try specifying a full path to everything (ie: /path/to/java -jar ..) * Are there any environment variables that might affect the operation of java if they are present or absent? * Check all runtime assumptions (effective user, ulimits, environment, I/O redirects, etc). Often things like cron scripts and startup scripts execute in peculiar environments that cause weird head-scratching behavior. -- Charles Steinkuehler cha...@steinkuehler.net javascript: -- 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.
Re: [beagleboard] Re: Starting Up Programs Automatically With LXDE
Nick, how about setting up a shell script, something simple that fires up an already included binary when you log in. That is, to make sure it's not the Java library ? Assuming you have not done so already. On Mon, Nov 24, 2014 at 3:53 PM, Nick Apperley napper...@gmail.com wrote: Seems as though there is some strange differences in behaviour going on between the ARM version of LXDE and the x86 version with the way programs are automatically started, specifically the Java ones. Would it be possible to have Robert Nelson look into this issue with LXDE? On Thursday, 20 November 2014 13:15:06 UTC+13, William Hermans wrote: Eric, perhaps this is a post worthy of stackoverlfow ? There are plenty of very knowledgeable individuals who may have had similar experience with embedded versus PC Java implementations. I honestly do not know much about Java in either case, but my gut instinct tells me this problem has to do with the different platform implementations. On Wed, Nov 19, 2014 at 4:06 PM, Charles Steinkuehler cha...@steinkuehler.net wrote: On 11/19/2014 2:29 AM, Eric Apperley wrote: - this command, when added to the shell script in the user's home directory does not successfully execute on the Beaglebone (it does on a PC running LUbuntu): java -jar /home/organ/jOrgan-3_20/jorgan.jar I don't know what might be causing your particular problem, but looking at your command above some generic *nix debugging tips come to mind: * Try specifying a full path to everything (ie: /path/to/java -jar ..) * Are there any environment variables that might affect the operation of java if they are present or absent? * Check all runtime assumptions (effective user, ulimits, environment, I/O redirects, etc). Often things like cron scripts and startup scripts execute in peculiar environments that cause weird head-scratching behavior. -- 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. -- 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] serial UART async_low_latency does not seem to work. still 10ms latency!
speed up to 921600bps or more if your remote uart can work 2014-11-24 19:17 GMT+08:00 Thomas O skjor...@gmail.com: Hi all i am writing some software using the OMAP_SERIAL drivers to send and receive data from a c program (TERMIOS). I am seeing large delays 10ms ticks when sending and receiving data on the UARTS. In the normal linux driver there is a option called ASYNC_LOW_LATENCY. When i am setting this flag via IOCTL i was expecting this latency to drop. But it seems ti be ignored by the OMAP_SERIAL driver. I have tried to set the option both via the following code snippet and via the STTY command line interface. Any information on this or any way to get the latency down would be much appreciated. /Thomas -- 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] serial UART async_low_latency does not seem to work. still 10ms latency!
And if you really want the low latency instead of output throw http://git.omapzoom.org/?p=kernel/omap.git;a=blob;f=drivers/tty/serial/omap-serial.c;h=f3aed1f4766742cac97419ff214577b58d19e01b;hb=7e6408234000c6526dae3f55c851adbcaae2d9ef#l1460 Try use lower fifo water marker , Try up-port.fifosize = 8; This might cause data overflow , No guarantee about this ,just try it 2014-11-25 9:53 GMT+08:00 liyaoshi liyao...@gmail.com: speed up to 921600bps or more if your remote uart can work 2014-11-24 19:17 GMT+08:00 Thomas O skjor...@gmail.com: Hi all i am writing some software using the OMAP_SERIAL drivers to send and receive data from a c program (TERMIOS). I am seeing large delays 10ms ticks when sending and receiving data on the UARTS. In the normal linux driver there is a option called ASYNC_LOW_LATENCY. When i am setting this flag via IOCTL i was expecting this latency to drop. But it seems ti be ignored by the OMAP_SERIAL driver. I have tried to set the option both via the following code snippet and via the STTY command line interface. Any information on this or any way to get the latency down would be much appreciated. /Thomas -- 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.
[beagleboard] Accessing and controlling PMIC, TPS65217C, from shell
Hi All, I connected a rechargeable Li+ battery to my BBB TP5, TP6, TP7, and TP8. I shorted TP5 and TP6 and added a 10uF decoupling capacitor. In addition, I connected TS to GND with a 9K resistor which is 10K || 75K according to the datasheet and the board boots fine from battery. Now my question is that how can I monitor the battery status(how much they are charged) or change the setting of PMIC, TPS65127C from shell. For instance, I would like to set the charging voltage to 4.2 rather than the default 4.1V. Or I would like to turn on/off WLED etc. Is there a tool, like Alsamixer, for this? if not what would be the best approach for controlling PMIC from shell? I posted it here because PMIC uses I2C interface to talk to AM335x. https://lh4.googleusercontent.com/-E-wdJPfnG5U/VHPNaDDU9WI/AAo/tEjegAyAzAM/s1600/bbb-batt-srm.jpg https://lh3.googleusercontent.com/-d7FQ9BVS6J4/VHPNtiSxI4I/AAw/3_g2aL5Q2K4/s1600/bbb-batt1.jpg Thanks for your time and consideration. -- 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] Beagle bone taking input from a kinect through the microsoft DSS
Hello I'm trying to get the kinect to send its gesture data to my beagle bone with the microsoft dss framework. I know that there's already a multitude of different ways to get the beagle bone to recognize data from the kinect directly but for my project I need it to go through the dss. Any tips or hints will be 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] serial UART async_low_latency does not seem to work. still 10ms latency!
And another way try CONFIG_OMAP_32K_TIMER_HZ=1024 in your kernel CONFIG 2014-11-25 9:59 GMT+08:00 liyaoshi liyao...@gmail.com: And if you really want the low latency instead of output throw http://git.omapzoom.org/?p=kernel/omap.git;a=blob;f=drivers/tty/serial/omap-serial.c;h=f3aed1f4766742cac97419ff214577b58d19e01b;hb=7e6408234000c6526dae3f55c851adbcaae2d9ef#l1460 Try use lower fifo water marker , Try up-port.fifosize = 8; This might cause data overflow , No guarantee about this ,just try it 2014-11-25 9:53 GMT+08:00 liyaoshi liyao...@gmail.com: speed up to 921600bps or more if your remote uart can work 2014-11-24 19:17 GMT+08:00 Thomas O skjor...@gmail.com: Hi all i am writing some software using the OMAP_SERIAL drivers to send and receive data from a c program (TERMIOS). I am seeing large delays 10ms ticks when sending and receiving data on the UARTS. In the normal linux driver there is a option called ASYNC_LOW_LATENCY. When i am setting this flag via IOCTL i was expecting this latency to drop. But it seems ti be ignored by the OMAP_SERIAL driver. I have tried to set the option both via the following code snippet and via the STTY command line interface. Any information on this or any way to get the latency down would be much appreciated. /Thomas -- 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] Accessing and controlling PMIC, TPS65217C, from shell
As I know , if only 2 wires , you can not access the Li+battery status , you can just get voltage value from PMU There always another 1 wire to get the communication with MCU in battery module 2014-11-25 8:52 GMT+08:00 resandevinw...@gmail.com: Hi All, I connected a rechargeable Li+ battery to my BBB TP5, TP6, TP7, and TP8. I shorted TP5 and TP6 and added a 10uF decoupling capacitor. In addition, I connected TS to GND with a 9K resistor which is 10K || 75K according to the datasheet and the board boots fine from battery. Now my question is that how can I monitor the battery status(how much they are charged) or change the setting of PMIC, TPS65127C from shell. For instance, I would like to set the charging voltage to 4.2 rather than the default 4.1V. Or I would like to turn on/off WLED etc. Is there a tool, like Alsamixer, for this? if not what would be the best approach for controlling PMIC from shell? I posted it here because PMIC uses I2C interface to talk to AM335x. https://lh4.googleusercontent.com/-E-wdJPfnG5U/VHPNaDDU9WI/AAo/tEjegAyAzAM/s1600/bbb-batt-srm.jpg https://lh3.googleusercontent.com/-d7FQ9BVS6J4/VHPNtiSxI4I/AAw/3_g2aL5Q2K4/s1600/bbb-batt1.jpg Thanks for your time and consideration. -- 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] How to communicate USB-to-serial through USB hub (ttyACM0)
check your usb hub power supply ? 2014-11-25 0:29 GMT+08:00 Teis Draiby t...@teis.net: I am currently communicating between my Beaglebone and a Maple board via a serial connection directly through a USB cable. This works well. (LeafLabs Maple is an Arduino-like board with an on-board USB connector) Due to power requirements I want to relpace the direct USB connection with a power supplied USB hub but when connecting the Maple board this way I do no longer see the serial device listed. I am new to Linux/Debian and am unsure what to do from here, and if it's even possible to perform serial communication through an USB hub. - Direct USB(Beaglebone)-to-USB(Maple) serial communication (works) - Beaglebone terminal: # uname -a Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l GNU/Linux # lsusb *Bus 001 Device 003: ID 1eaf:0004* Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # ls /dev/ttyA* */dev/ttyACM0* Serial communication through USB hub (missing serial device?) Beaglebone terminal: # lsusb *Bus 001 Device 002: ID 05e3:0612 Genesys Logic, Inc.*- this only shows up when using a special hd-USB cable. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # ls /dev/ttyA* ls: cannot access /dev/ttyA*: No such file or directory # ls /dev/ttyU* ls: cannot access /dev/ttyU*: No such file or directory Any advice from here is greatly appreciated. thanks, Teis -- 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.
[beagleboard] tslib not working.
I built Qt4 from source with tslib support using -qt-mouse-tslib in the configuration options. I am able to run qt applications just fine but the touch screen isn't working. How do i make sure i have tslib installed? I tried apt-get install tslib-bin and get the error Unable to locate package tslib-bin. How do I install tslib? -- 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: tslib not working.
also when i trun ts-calibrate i get command not found. Does this mean i dont have tslib installed? On Monday, November 24, 2014 9:33:34 PM UTC-5, earless wrote: I built Qt4 from source with tslib support using -qt-mouse-tslib in the configuration options. I am able to run qt applications just fine but the touch screen isn't working. How do i make sure i have tslib installed? I tried apt-get install tslib-bin and get the error Unable to locate package tslib-bin. How do I install tslib? -- 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: tslib not working.
https://www.google.com/search?q=debian+package++tslib-bin william@arm:~$ apt-cache search libts-bin libts-bin - touch screen library utilities william@arm:~$ On Mon, Nov 24, 2014 at 7:45 PM, earless gunclu...@gmail.com wrote: also when i trun ts-calibrate i get command not found. Does this mean i dont have tslib installed? On Monday, November 24, 2014 9:33:34 PM UTC-5, earless wrote: I built Qt4 from source with tslib support using -qt-mouse-tslib in the configuration options. I am able to run qt applications just fine but the touch screen isn't working. How do i make sure i have tslib installed? I tried apt-get install tslib-bin and get the error Unable to locate package tslib-bin. How do I install tslib? -- 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: tslib not working.
google is always your best resource concerning packages. Then once you have established the package name, apt-cache search package_name is how one finds out if it exists for armhf. On Mon, Nov 24, 2014 at 7:59 PM, William Hermans yyrk...@gmail.com wrote: https://www.google.com/search?q=debian+package++tslib-bin william@arm:~$ apt-cache search libts-bin libts-bin - touch screen library utilities william@arm:~$ On Mon, Nov 24, 2014 at 7:45 PM, earless gunclu...@gmail.com wrote: also when i trun ts-calibrate i get command not found. Does this mean i dont have tslib installed? On Monday, November 24, 2014 9:33:34 PM UTC-5, earless wrote: I built Qt4 from source with tslib support using -qt-mouse-tslib in the configuration options. I am able to run qt applications just fine but the touch screen isn't working. How do i make sure i have tslib installed? I tried apt-get install tslib-bin and get the error Unable to locate package tslib-bin. How do I install tslib? -- 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] How to communicate USB-to-serial through USB hub (ttyACM0)
Expanding on what liyaoshi just posted. I remember someone else having a similar problem but with a different device. His solution was to cut the power wire feeding back from the USB hub back into the beaglebone. However, as said above he / she used a different device, and the device its self was not showing up at all under lsusb output. Also, I'm fairly sure the USB hub was self powered. On Mon, Nov 24, 2014 at 7:14 PM, liyaoshi liyao...@gmail.com wrote: check your usb hub power supply ? 2014-11-25 0:29 GMT+08:00 Teis Draiby t...@teis.net: I am currently communicating between my Beaglebone and a Maple board via a serial connection directly through a USB cable. This works well. (LeafLabs Maple is an Arduino-like board with an on-board USB connector) Due to power requirements I want to relpace the direct USB connection with a power supplied USB hub but when connecting the Maple board this way I do no longer see the serial device listed. I am new to Linux/Debian and am unsure what to do from here, and if it's even possible to perform serial communication through an USB hub. - Direct USB(Beaglebone)-to-USB(Maple) serial communication (works) - Beaglebone terminal: # uname -a Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l GNU/Linux # lsusb *Bus 001 Device 003: ID 1eaf:0004* Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # ls /dev/ttyA* */dev/ttyACM0* Serial communication through USB hub (missing serial device?) Beaglebone terminal: # lsusb *Bus 001 Device 002: ID 05e3:0612 Genesys Logic, Inc.*- this only shows up when using a special hd-USB cable. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # ls /dev/ttyA* ls: cannot access /dev/ttyA*: No such file or directory # ls /dev/ttyU* ls: cannot access /dev/ttyU*: No such file or directory Any advice from here is greatly appreciated. thanks, Teis -- 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. -- 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] UARTs enabled but don't work on Debian!
Ok Sorry, I am trying to send characters out the UART2 on a BBB Rev C using
HTML Javascript SEE program below: This worked before and stopped working,
not sure why. Be patient with my I am a newbie a month or so into
learning HTML. Javascript, linux, beaglebone, but only working on it part
time outside of my regular job.
I have a logic analyzer connected to P9 Pins 20 21 which are the UART2 TX
and RX line. When I send the data using below program the TX pin does not
toggle so no data comes out of the TX pin.
When this worked it sent the data using program below and if I input a 5 a
value of 0x05 was shifted out of the UART2 on the TX pin.My goal is to
get the UART2 to work after power up without having to type in a bunch of
commands before running the HTML/Javscript.
When I type
cat /sys/devices/bone_capemgr.*/slots
I get the following:
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
7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART2
I did add the following line to my uEnv.txt file
capemgr.enable_partno=BB-UART2
But this didn't seem to make a difference either way.Any suggestions
would be appreciated.
Example code below here ***
// UART2 TX Test filename = uartwr.html
html
body
Uart Byte:br
input type=number name=value id='value'/
button onclick=uartWr()SEND/button
/body
head
script src=/bonescript.js/script
script
function uartWr() {
var b = require('bonescript');
// set baud rate and buffer size
var port = '/dev/ttyO2'; // set UART port
var data = document.getElementById('value').value;
var options = { baudrate: 9600, buffer: 100} ;
b.serialOpen(port, options, onSerial);//
function onSerial(x) {
var b = require('bonescript');
if (x.err) {
console.log('***ERROR*** ' + JSON.stringify(x));
}
if (x.event == 'open') {
console.log('***OPENED***');
}
if (x.event == 'data') {
console.log(String(x.data));
}
}
b.serialWrite(port, [data] );
}
/script
/head
/html
Example code Above here ***
On Saturday, November 22, 2014 7:52:22 PM UTC-8, William Hermans wrote:
John, detailed description is required. Dont work is pretty vague and
leaves a lot of room for guessing.
On Sat, Nov 22, 2014 at 8:41 PM, John Mladenik john...@sbcglobal.net
javascript: wrote:
Robert,
I am having the same problem with UART2 (the only UART I need to work)
but mine worked in the past. It even worked through re-power until the
BBB sat overnight unpowered. I went through all of the steps I found in
links to make it work, but none of the steps were anything like yours.I
am a newbie to software and linux so I don't really understand what you are
saying to do. . Can you tell me what exactly your program and compile are
doing? Will it work for UART2.
When you said The pins aren't mixed to the peripheral. did you mean
MUXED instead of mixed?
so you have a dtb file that you compile into a dts file? Since /src/arm
does no exist on my BBB do I need to create that folder to copy the file
into it?I assume it is changing the mux configuration of the UART pins
to be connected in the ARM to the UART iinstead of the GPIO?
Sorry of my questions seem dumb, but that is what I feel like, I spent at
least 10-12 hours to get the UART to work the first time and when it
stopped working the next day it set me back weeks in my project. :(
On Friday, November 14, 2014 1:12:22 PM UTC-8, RobertCNelson wrote:
http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb
The pins aren't mixed to the peripheral.
Example enable this
https://github.com/RobertCNelson/dtb-rebuilder/
blob/3.14-ti/src/arm/am335x-boneblack.dts#L78
And run...
make ; sudo make install ; sudo reboot
On Nov 14, 2014 2:46 PM, m.jafa...@gmail.com wrote:
I've been playing around with my BBB for about a month now and got
everything up and running. Today I spent the whole day to get UART
loopback
to work on Debian. It simply doesn't work! Tried with Qt (cross-compiled
and all samples are working), QSerialPortInfo::availablePorts().count()
returns zero. At first I thought it can be a QtSerialPort issue. So I did
a
loop back on UART1 and UART2 (P9.21 connected to P9.26 and P9.22 connected
to P9.24). Then opened minicom -b 9600 -D /dev/ttyO1 and minicom -b
9600
-D /dev/ttyO2 in two separate terminals. I expected to see whatever I
type
in each one of the terminals on the other one. But that wasn't the case.
Nothing happens! Any idea what's wrong?
Here's some info about my setup:
*Fresh install of
BBB-eMMC-flasher-debian-7.7-console-armhf-2014-10-29-2gb.img.xz. Didn't
modify anything. *
Re: [beagleboard] Send Raw or hex data out the serial port using bonescript
I'm sorry your answer raised more questions I am a newbie and don't
understand
On Monday, November 24, 2014 7:43:55 AM UTC-8, George Lu wrote:
On Sat, Nov 22, 2014 at 7:49 PM, John Mladenik john...@sbcglobal.net
javascript: wrote:
So it worked but once I let the board sit not being powered overnight it
stopped working. Do you or anyone know how to get the UART2 working and
stay working once powered down and then turned back on?
Once power cycled, you would need to start up the program again so that
the serial port could be properly opened for writing. I would have the
bonescript code in, say, /home/debian/doSerial.js, and run that
automatically on every reboot. There are a number of ways to do this. One
quick way is try to add a line in /etc/crontab to run this command on
@reboot:
I do not have a directory named /etc/crontab nor do I have a file named
doSerial.js on my Beaglebone. Do I need to create this directory and
file? If so what do I put in the file? The bonescript/javascript code I
am using is embedded in the HTML file given above in original post, that I
browse to from chrome.When the UART is working when I browse to the
HTML on the Beaglebone and click send to send the data entered in the HTML.
@reboot rootcd /home/debian
NODE_PATH=/usr/local/lib/node_modules export NODE_PATH doSerial.js
Assuming you are using debian image, /dev/ttyO1 and /dev/ttyO2 have
rw-rw--- as their permission. So you either need to run it as root or add
your desired user to the dialout group to be able to write to these serial
interfaces.
ttyO2 is in the /dev folder and has crw-rw---T permissions set. I only
have a single user that is what it was configured as when I got the BBB and
I am pretty sure it is a root user. No password I just use root as the
username to log in.
when I run the HTML/Javascript above ithe chrome debugger does say open
each time I click send.
If doSerial.js crashes for any reason, you could use a process monitor to
restart it. Supervisord http://supervisord.org/, forever
https://github.com/nodejitsu/forever, pm2
https://github.com/Unitech/pm2, are some options to explore.
On Wednesday, November 19, 2014 3:44:26 PM UTC-8, George Lu wrote:
On Wed, Nov 19, 2014 at 3:26 PM, John Mladenik john...@sbcglobal.net
wrote:
I need to be able to send raw data out of the serial port using
Bonescript command b.serialWrite.I set up an HTML Bonescript to send
data and then looked on the logic analyzer to see what bit pattern is sent
out. The pattern is always the ASCII value of the character whether the
variable is a text or number.
Does anyone know how to pass to b.serialWrite a value so that the UART
outputs that value?
so I want to have
var port = '/dev/ttyO2'; // set UART port
var data = 0x55 ;
b.serialWrite(port, data );
and for the bit pattern coming out of the UART to be 01010101
I tried using String.fromCharCode(data); but this only works for
values up to 127 (0x7F) since that is all ASCII goes to. This must not
support extended ASCII?
here is my html/javascript to test this functionality
html
body
Uart Byte:br
input type=number name=value id='value'/
button onclick=uartWr()SEND/button
/body
head
script src=/bonescript.js/script
script
function uartWr() {
var b = require('bonescript');
var port = '/dev/ttyO2'; // set UART port
var data = document.getElementById('value').value;
// set baud rate and buffer size
var options = {
baudrate: 9600
};
b.serialWrite(port, data );
}
/script
/head
/html
I recall BoneScript uses https://github.com/
voodootikigod/node-serialport for serial port interface.
You should be able to send raw binary with b.serialWrite(port, [0x55]);
Data should be a buffer (http://nodejs.org/api/buffer.html).
--
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] uSD Disconnects; Reset Fails with CCCCC; Re-Insert Boots
My Rev.A6 BBB had been running solidly 24/7 for months, with only explainable software-related crashes. But in the last week it has just hung twice, with no relation to software functions, nothing unusual in the logs, and D2/3/4 on solid. It is powered by an analog regulator from my solar house battery system with huge and redundant battery banks, so there is really no chance of a power glitch. It runs the RCN distro of Ubuntu 14.04, from a 16 GB SanDisk uSD. When it hangs and I press Reset without cycling power, I get no user LEDs, but I do get a series of C characters on the console port. My A6 SRM says: --- Without holding the [boot] switch, the board will boot try to boot from the eMMC. If it is empty, then it will try booting from the microSD slot, followed by the serial port, and then the USB port. --- But that is for a power cycle boot. Reset alone, with constant power, does not change the boot mode. Apparently that means does not change between eMMC default and uSD default for the first try, but still allows for Serial or USB boot if the default local storage fails. Later it says: --- On boot, the processor will look for the SPIO0 port first, then microSD on the MMC0 port, followed by USB0 and UART0. In the event there is no microSD card and the eMMC is empty, USB0 or UART0 could be used as the board source. --- It is not clear whether USB and UART/Serial are checked in a particular order, or are continuously checked. My experience seems to suggest that Serial, at least, is continuously checked, and that uSD is also continuously checked: If I remove the uSD while the C is streaming on the console, nothing obvious happens. If I then re-insert the uSD, booting begins instantly and proceeds normally! So, I'm guessing the uSD somehow loses contact with its socket, and an access from the BBB fails and hangs Linux, with the LED that seems to indicate uSD access on solid. But I can't see any problem inside the uSD socket, and the contacts on the uSD itself look perfect. And this uSD socket has a relatively easy life compared to those in my phone or other portable/remote devices, which have never glitched on me. So what else could this be? An electrical failure inside the uSD card? Guess I should try a power-cycle reboot without mechanical disturbance next time it happens... -- 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] a question about asking questions
Hi, I have still unresolved issue (no answer here for how to make pwm_P8_13 low on boot? ) and therefore trying to figure out if my question is: - too easy - too difficult - not interesting enough - other? As I see there is generally a number of unanswered questions, would it be possible for the moderator to give an indication in a simple style, something like: too easy, google it yourself or whatever, to avoid frustration. Jan -- 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] Change I2C bus for video communication
This is my current overlay file: http://pastie.org/private/j91tplpqnhymvvig1pc0rw Can you please tell me either there is still anything wrong? I Still cant get the video to work :( W dniu poniedziałek, 24 listopada 2014 21:36:51 UTC+1 użytkownik RobertCNelson napisał: On Mon, Nov 24, 2014 at 2:34 PM, Bremenpl brem...@gmail.com javascript: wrote: This is the output on debug serial now: . . .Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.338981] omap2_mbox_probe: platform not supported [0.493971] tps65217-bl tps65217-bl: no platform data provided [0.558187] bone-capemgr bone_capemgr.9: slot #0: No cape found [0.595295] bone-capemgr bone_capemgr.9: slot #1: No cape found [0.632402] bone-capemgr bone_capemgr.9: slot #2: No cape found [0.669512] bone-capemgr bone_capemgr.9: slot #3: No cape found [0.688174] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [0.749856] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [0.761544] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [0.768813] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single Loading, please wait... systemd-fsck[205]: rootfs: clean, 21581/04 files, 122520/444160 blocks systemd-fsck[290]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN systemd-fsck[290]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters [6.507830] tilcdc 4830e000.fb: no encoders/connectors found [6.513806] tilcdc 4830e000.fb: failed to initialize mode setting There is still no visual. It says: ... tilcdc.. Does that mean hes not using the driver for tfp410? Also, could you please confirm either the I2C2 in the tree overlay is the I2C2 on the header? I am still not certain. Verfiy: https://github.com/derekmolloy/boneDeviceTree/tree/master/docs 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.
