[beagleboard] Re: Error with http://repos.rcn-ee.net/debian/dists/wheezy/Release
Robert Nelson robertcnel...@gmail.com wrote: On Wed, Aug 12, 2015 at 9:03 AM, c...@isbd.net wrote: I'm trying to update an old[is] BBB debian installation. When I do 'apt-get update' it mostly works but I'm getting the following errors:- Get:6 http://repos.rcn-ee.net wheezy Release [2,169 B] Err http://repos.rcn-ee.net wheezy Release W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repos.rcn-ee.net wheezy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D284E608A4C46402 W: Failed to fetch http://repos.rcn-ee.net/debian/dists/wheezy/Release W: Some index files failed to download. They have been ignored, or old ones used instead. How do I get things to catch up properly? Grab the newer keyring: wget https://rcn-ee.com/repos/debian/pool/main/r/rcn-ee-archive-keyring/rcn-ee-archive-keyring_2015.07.05~bpo70+20150705+1_all.deb sudo dpkg -i rcn-ee-archive-keyring_2015.07.05~bpo70+20150705+1_all.deb then: sudo apt-get update will be happy.. Brilliant, thanks Robert, my BBB is happy again! :-) -- Chris Green · -- 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 doesn't sometimes start. Only Power LED is on
Please let us know how the jumping RX to 3V3 line works out. If I recall correctly, the RX line is pulled down to ground which didn't make sense to me as generally an asserted RX state is considered idle (if memory serves me correctly). What resistance are you using? Modifying u-boot is not something I want to do if I don't have to. On Wednesday, June 3, 2015 at 2:04:29 PM UTC-5, AQG Chris wrote: We are dealing with the same issue - we found another complaint of the same thing, in which the user identifies phantom characters on the UART during startup causing the board to go into u-boot. If you don't have a display attached or a serial connection available, u-boot looks a lot like a solid power LED and nothing else. link to that thread: http://andicelabs.com/2014/07/beaglebone-black-boot-issues/ That user apparently was able to modify u-boot to look for a certain character instead of any keystroke. In the limiting testing I've done, it seems that the problem also doesn't occur if you have a serial connection hooked up to UART0. I'm now experimenting with jumping the RX line of UART0 to 3.3v, and so far haven't had the issue again. -- 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] Image 2015-7-26, kernel 4.1.3-ti-r6
I have version 4.1.4-ti-r8.1 operating on a total of 21 boards now. Uptime 18h for most of them, one even 1 day 20h, without any reboot. Good work! I understand this is a development build from Robert, is there a planning for something that is released more officially? Thanks a lot for all effort! -- Günter (dl4mea) -- 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 OpenSuse 13.2 no video output
Hi, The BBB is running fine under the Debian image on the eMMC I have been able to use on several displays through the uHDMI connector and also using the 4DCAPE-70T LCD http://www.4dsystems.com.au/product/4DCAPE_70T/ So I'm sure my hardware is OK. For a new project I need to use OpenSuse on the BBB. I have tested the latest 13.2 images http://download.opensuse.org/ports/armv7hl/distribution/13.2/appliances/ *openSUSE-13.2-ARM-JeOS-beaglebone.armv7l-1.12.1-Build33.5.raw.xz* *openSUSE-13.2-ARM-XFCE-beaglebone.armv7l-1.12.1-Build33.8.raw.xz* OpenSuse is booting and I'm able to connect to the board through SSH but I'm not able to have video on the HDMI output or on the 4DCAPE-70T which is my goal. Under JeOS I tried the following I install this package *xf86-video-omap| X.Org X server -- Omapdrm display driver* which has installed the following 97 packages *Mesa Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 bundle-lang-common-ar cpp cpp48 esound-daemon fontconfig fonts-config ft2demos hicolor-icon-theme hicolor-icon-theme-branding-openSUSE libFLAC8 libLLVM libSDL-1_2-0 libX11-xcb1 libXaw7 libXdamage1 libXdmcp6 libXext6 libXfixes3 libXfont1 libXft2 libXi6 libXinerama1 libXmu6 libXmuu1 libXpm4 libXrandr2 libXrender1 libXtst6 libXxf86vm1 libaudiofile1 libcloog-isl4 libdrm2 libdrm_freedreno1 libdrm_nouveau2 libdrm_omap1 libdrm_radeon1 libepoxy0 libesd0 libevdev2 libfontenc1 libfreetype6 libgbm1 libisl10 libmpc3 libmpfr4 libmtdev1 libogg0 libpciaccess0 libpixman-1-0 libpng16-16 libpulse0 libsndfile1 libspeex1 libvorbis0 libvorbisenc2 libwayland-client0 libwayland-server0 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-sync1 libxcb-xfixes0 libxkbfile1 libxshmfence1 linuxconsoletools luit mkfontdir mkfontscale sessreg xbitmaps xdm xf86-input-evdev xf86-input-joystick xf86-input-keyboard xf86-input-mouse xf86-input-synaptics xf86-input-void xf86-input-wacom xf86-video-fbdev xf86-video-modesetting xf86-video-omap xf86-video-vesa xkbcomp xkeyboard-config xorg-x11-driver-video xorg-x11-fonts-core xorg-x11-server xrandr xrdb xterm yast2-branding-openSUSE yast2-x11* But the screen is not found see Xorg log below. If somebody has an advice to help it will me great. Thanks in advance, Matthieu *linux:~ # cat /var/log/Xorg.0.log* *[17.842]* *X.Org X Server 1.16.1* *Release Date: 2014-09-21* *[17.842] X Protocol Version 11, Revision 0* *[17.842] Build Operating System: openSUSE SUSE LINUX* *[17.842] Current Operating System: Linux linux 3.16.7-11-default #1 SMP Sat Apr 4 12:46:09 UTC 2015 (4c49729) armv7l* *[17.843] Kernel command line: root=/dev/disk/by-id/mmc-SL16G_0x28cf527e-part2 loader=uboot disk=/dev/disk/by-id/mmc-SL16G_0x28cf527e resume=/dev/disk/by-id/mmc-SL16G_0x28cf527e-part3 plymouth.enable=0 console=ttyO0* *[17.843] Build Date: 12 June 2015 07:53:26PM* *[17.843]* *[17.843] Current version of pixman: 0.32.6* *[17.843]Before reporting problems, check http://wiki.x.org* *to make sure that you have the latest version.* *[17.843] Markers: (--) probed, (**) from config file, (==) default setting,* *(++) from command line, (!!) notice, (II) informational,* *(WW) warning, (EE) error, (NI) not implemented, (??) unknown.* *[17.845] (==) Log file: /var/log/Xorg.0.log, Time: Thu Jan 1 01:00:17 1970* *[17.852] (==) Using config directory: /etc/X11/xorg.conf.d* *[17.853] (==) Using system config directory /usr/share/X11/xorg.conf.d* *[17.864] (==) No Layout section. Using the first Screen section.* *[17.864] (==) No screen section available. Using defaults.* *[17.864] (**) |--Screen Default Screen Section (0)* *[17.865] (**) | |--Monitor default monitor* *[17.865] (==) No device specified for screen Default Screen Section.* *Using the first device section listed.* *[17.865] (**) | |--Device fb gfx* *[17.865] (==) No monitor specified for screen Default Screen Section.* *Using a default monitor configuration.* *[17.866] (==) Automatically adding devices* *[17.866] (==) Automatically enabling devices* *[17.866] (==) Automatically adding GPU devices* *[17.869] (WW) The directory /usr/share/fonts/Type1/ does not exist.* *[17.869]Entry deleted from font path.* *[17.869] (WW) The directory /usr/share/fonts/100dpi does not exist.* *[17.869]Entry deleted from font path.* *[17.871] (WW) The directory /usr/share/fonts/ghostscript/ does not exist.* *[17.871]Entry deleted from font path.* *[17.871] (WW) The directory /usr/share/fonts/cyrillic does not exist.* *[17.871]Entry deleted from font path.* *[17.871] (WW) The directory /usr/share/fonts/misc/sgi does not exist.* *[17.871]Entry deleted from font path.* *[17.871] (WW) The directory /usr/share/fonts/truetype/ does not exist.* *[17.871]Entry deleted from font path.* *[17.871] (==)
Re: [beagleboard] Re: Do ADC filenames ever change, if so when?
On Wed, Aug 12, 2015 at 9:14 AM, c...@isbd.net wrote: Robert Nelson robertcnel...@gmail.com wrote: On Tue, Aug 11, 2015 at 3:42 PM, c...@isbd.net wrote: Robert Nelson robertcnel...@gmail.com wrote: On Fri, Aug 7, 2015 at 11:36 AM, c...@isbd.net wrote: I have a BBB running Debian GNU/Linux 7, 3.8.13-bone47 kernel. I.e. pretty standard. My raw ADC files are to be found at:- /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage0_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage1_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage2_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage3_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage4_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage5_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage6_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage7_raw Currently I use a find() function written in python which walks the /sys/devices tree to find these files, but it's very slow. If I hard code the file names how often, if at all, will they need changing? ... and/or is there an easier way to find them, i.e. is there a configuration file somewhere that tells me where they are (or at least the non-constant bits of the path)? You should also see them here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/sysfs-bus-iio#n91 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw KernelVersion: 2.6.35 Contact: linux-...@vger.kernel.org Description: Raw (unscaled) differential voltage measurement equivalent to channel Y - channel Z where these channel numbers apply to the physically equivalent inputs when non differential readings are separately available. In differential only parts, then all that is required is a consistent labeling. Units after application of scale and offset are millivolts. That isn't really what I was asking for Robert. Actually it was... Walk: /sys/bus/iio/devices/iio* Well, very nearly! :-) If I 'cd /sys/bus/iio/devices/iio*' I get to '/sys/bus/iio/devices/iio:device0', is there any way of knowing that it's 'iio:device0'? It's still sort of clumsy doing a Python walk to find the files. well the tscadc label: https://github.com/beagleboard/linux/blob/3.8/firmware/capes/BB-ADC-00A0.dts#L37 is here: root@beaglebone:~# cat /sys/bus/iio/devices/iio\:device0/name tiadc Regards, -- Robert Nelson https://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: Do ADC filenames ever change, if so when?
Robert Nelson robertcnel...@gmail.com wrote: On Tue, Aug 11, 2015 at 3:50 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Aug 11, 2015 at 3:42 PM, c...@isbd.net wrote: Robert Nelson robertcnel...@gmail.com wrote: On Fri, Aug 7, 2015 at 11:36 AM, c...@isbd.net wrote: I have a BBB running Debian GNU/Linux 7, 3.8.13-bone47 kernel. I.e. pretty standard. My raw ADC files are to be found at:- /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage0_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage1_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage2_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage3_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage4_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage5_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage6_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage7_raw Currently I use a find() function written in python which walks the /sys/devices tree to find these files, but it's very slow. If I hard code the file names how often, if at all, will they need changing? ... and/or is there an easier way to find them, i.e. is there a configuration file somewhere that tells me where they are (or at least the non-constant bits of the path)? You should also see them here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/sysfs-bus-iio#n91 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw KernelVersion: 2.6.35 Contact: linux-...@vger.kernel.org Description: Raw (unscaled) differential voltage measurement equivalent to channel Y - channel Z where these channel numbers apply to the physically equivalent inputs when non differential readings are separately available. In differential only parts, then all that is required is a consistent labeling. Units after application of scale and offset are millivolts. That isn't really what I was asking for Robert. Actually it was... Walk: /sys/bus/iio/devices/iio* You can get one name here: root@beaglebone:~# cat /sys/bus/iio/devices/iio\:device0/name tiadc What I want though is the names of the files with the values in, i.e.:- /sys/bus/iio/devices/iio:device0/in_voltage0_raw but device0 should also be set-able somewhere.. I don't want to set it, I just want to know its value! :-) Thanks though, you've taken me to a much faster way of finding the files at least. -- Chris Green · -- 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] No working leases in persistent database - sleeping(cannot connect BeagleboneBlack to wireless)
Yesterday beaglebone black(bbb) was connected to wireless using both router and mobile wireless hotspot. But today interestingly it is not successful to establish wireless connection through router, but can connect via mobile hotspot. What kind of router setting may be causing this? I didn't change any settings' configuration of the router, it was just powered off when I left the office and powered on today morning. Router's firewall was disabled, and port triggering for ssh port was added yesterday(to remotely connect to the bbb from other PCs). I did reboot the router several times, but this did not solve it. /etc/network/interfaces content is as followings auto lo iface lo inet loopback auto wlan0 iface wlan0 inet dhcp wpa-ssid orubaTech wpa-psk password If you're interested. After ifup --force wlan0 it is returning No working leases in persistent database - sleeping message. Can you please help me to figure out what is causing this? Thanks. This problem is very similar to this guys problem link http://stackoverflow.com/questions/30514452/cannot-connect-beaglebone-black-debian-to-network-via-usb-wifi-antennae/31968754#31968754 -- 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] Button S2 Power not working using Kernel 3.14
Thanks Robert. But I'm using sysvinit, and without udev this board. Other suggestion? Em terça-feira, 11 de agosto de 2015 18:52:27 UTC-3, RobertCNelson escreveu: On Tue, Aug 11, 2015 at 4:43 PM, Cleiton Bueno cleito...@gmail.com javascript: wrote: Customize a Linux distribution with Yocto Project, at the very end I need to enable the functionality of the Pushbutton S2 to shutdown the plate. Double check your systemd settings: https://github.com/RobertCNelson/boot-scripts/blob/master/mods/wheezy-systemd-poweroff.diff the tp65217 hit mainline systemd around 221... Regards, -- Robert Nelson https://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] Image 2015-7-26, kernel 4.1.3-ti-r6
Hi Günter, On Wed, Aug 12, 2015 at 10:22 AM, Koellner Guenter dl4...@yahoo.de wrote: I have version 4.1.4-ti-r8.1 operating on a total of 21 boards now. Uptime 18h for most of them, one even 1 day 20h, without any reboot. Good work! I understand this is a development build from Robert, is there a planning for something that is released more officially? So r8.1 was just r8 with the one revert for testing. On 4 of my test boxes running that revert, 4 have reached an uptime of over 5 days. To date, I've enabled that revert in my scripts for all these kernels.. 4.1.4-ti-r9 4.1.5-bone15 4.2.0-rc6-bone2 Regards, -- Robert Nelson https://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] Button S2 Power not working using Kernel 3.14
On Wed, Aug 12, 2015 at 10:36 AM, Cleiton Bueno cleitonrbu...@gmail.com wrote: Thanks Robert. But I'm using sysvinit, and without udev this board. Other suggestion? Well There was a hack in 3.8 to map the keypress to the KEY_BUTTON https://github.com/beagleboard/linux/commit/23a12b82250887340a29d94fbabe7346dfeed817 Regards, -- Robert Nelson https://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] BBB OpenSuse 13.2 no video output
On Wed, Aug 12, 2015 at 10:16 AM, mclaire@gmail.com wrote: Hi, The BBB is running fine under the Debian image on the eMMC I have been able to use on several displays through the uHDMI connector and also using the 4DCAPE-70T LCD So I'm sure my hardware is OK. For a new project I need to use OpenSuse on the BBB. I have tested the latest 13.2 images openSUSE-13.2-ARM-JeOS-beaglebone.armv7l-1.12.1-Build33.5.raw.xz openSUSE-13.2-ARM-XFCE-beaglebone.armv7l-1.12.1-Build33.8.raw.xz OpenSuse is booting and I'm able to connect to the board through SSH but I'm not able to have video on the HDMI output or on the 4DCAPE-70T which is my goal. Under JeOS I tried the following I install this package xf86-video-omap| X.Org X server -- Omapdrm display driver Well... The am335x used on the beaglebone black, does not have the omap display ip block. Use fbdev as modesetting is to unstable. Then grab this xorg.conf https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-HDMI Regards, -- Robert Nelson https://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] Image 2015-7-26, kernel 4.1.3-ti-r6
Hello Robert, what is the difference between 4.1.4-ti-r9 and 4.1.5-bone15 and which one is the one recommended for future use? Cheers, Günter Am 12.08.2015 um 17:38 schrieb Robert Nelson: Hi Günter, On Wed, Aug 12, 2015 at 10:22 AM, Koellner Guenter dl4...@yahoo.de wrote: I have version 4.1.4-ti-r8.1 operating on a total of 21 boards now. Uptime 18h for most of them, one even 1 day 20h, without any reboot. Good work! I understand this is a development build from Robert, is there a planning for something that is released more officially? So r8.1 was just r8 with the one revert for testing. On 4 of my test boxes running that revert, 4 have reached an uptime of over 5 days. To date, I've enabled that revert in my scripts for all these kernels.. 4.1.4-ti-r9 4.1.5-bone15 4.2.0-rc6-bone2 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.
Re: [beagleboard] update_kernel.sh broken
This worked... Yea, that's like night and day after the 'git pull'. Process control on flashing the factory boards? I don't know if you need '--recursive' somewhere on your git scripts... or if it's just baked into the file tree... Attempting to upgrade and possibly downgrade my board if the kernel upgrade doesn't fix my device-tree issue with ADC. On Saturday, August 8, 2015 at 5:04:13 AM UTC-7, RobertCNelson wrote: Odd that file has been obsolete for a year.. Run: git reset HEAD --hard On Aug 8, 2015 12:30 AM, Duane Davis demi...@gmail.com javascript: wrote: root@beaglebone:/opt/scripts/tools# git pull Updating a4d0fe2..5fb4833 error: Your local changes to the following files would be overwritten by merge: tools/beaglebone-black-eMMC-flasher.sh Please, commit your changes or stash them before you can merge. Aborting I haven't made any changes to this file. This is a new board, just received it today, so I haven't done anything to it other than setting up networking. -- 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] Image 2015-7-26, kernel 4.1.3-ti-r6
all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. 2 days and still nothing. unfortunately gotta reboot though, need to test some other bug on MUSB. Thanks for testing Felipe. We might have a weird config setting that's causing it.. Can you attache your .config that lasted for 2 days and i'll start running comparisons of that against our kitchen sink config on my bbb farm.. Regards, -- Robert Nelson https://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: [Beaglebone Black, ADC, C++, Eclipse, crosscompiling]First steps: is this doable?
For PRU recommend you have a look at https://github.com/abhishek-kakkar/BeagleLogic and also from memory there was a similar CRO application On Wednesday, 12 August 2015 19:54:02 UTC+10, TJF wrote: Hi! Host CPU and TSC_ADC_SS have different clock domains. Internal ADC clock rate is 24 MHz. The theoretical maximum sample rate is 1.6 Msamples/s (= 15 cycles@24MHz in single shot mode) or 1.74 Msamples/s (= 14 cycles in continous mode). In praxis it's 200 ksamples/s. The PRUSS are first choise for real time tasks with high timing accuracy. Below 10 ksamples/s the CPU latency (due to Linux non-real-time-ness) is small (less than 10 % on a vanilla system). When you need concrete hints, you'll have to specify your timing requirements: - Is the external clock a regular pulse train? - What frequency? - Which maximum latency is required between clock pulse and ADC sample? BR Am Mittwoch, 12. August 2015 08:34:02 UTC+2 schrieb Valeria M.: Hi TJF, thanks for your reply! I was hoping not to have to resort to use PRUs D: , for now the low accuracy given by the ADC clock will have to do. (btw why 10 kHz accuracy? it's caused by Linux non-real-time-ness? Otherwise ADC clock frequency should be 1,6 MHz max right?) Other random question: I suppose that if I sync the BBB system clock to an external clock the ADC's one won't be affected by it right? I mean they have different time 'domain'. Corss-compiling I'll be able to debug my procject. Valeria Il giorno martedì 11 agosto 2015 21:45:09 UTC+2, TJF ha scritto: Hi Valeria! The FSM module in the TSC_ADC_SS can either get triggered by software or by an external hardware event (TIMER4-7 or PRU_ICSS pr1_host_intr0). See SRM chapter 12 http://www.ti.com/lit/pdf/spruh73 for details. The best way how to synchronize with an external clock depends on the clock frequency and the timming accuracy requirements. For high accuracy or above ~10 KHz you may need customized software. But below that frequency you may be happy with a simple solution: The ADC operates at a fast sampling rate and the host CPU just reads the current value when the external clock fires. This is feasible with libpruio http://beagleboard.org/project/libpruio/. (You may see some latency when the host CPU is busy by any system interrupt.) BR BTW: Cross-compiling adds further problems. Why not compiling on the BBB? -- 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] Beaglebone Black Wifi Managed and Master mode
I know there are several threads regarding wifi but many of these are outdated so thought I'd start a new thread, asking if anyone has been successful adding USB WiFi to debian 3.8.13-boneX where they are able to connect to existing access points AND configure the wifi to act as an access point (master mode) using hostapd. If you have been successful with both modes, I'd really appreciate you sharing which USB adapter you used and specifically the chipset. To date I have been using the RT5370 chipset with very reliable communications in both client (managed) and ap (master) mode - my issue is supply of these USB devices and I am looking for backup solutions. If we can collect sufficient info I will update wiki with this info to assist other users. Thanks Colin -- 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] Image 2015-7-26, kernel 4.1.3-ti-r6
On Wed, Aug 12, 2015 at 03:23:03PM -0500, Robert Nelson wrote: all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. 2 days and still nothing. unfortunately gotta reboot though, need to test some other bug on MUSB. Thanks for testing Felipe. We might have a weird config setting that's causing it.. Can you attache your .config that lasted for 2 days and i'll start running comparisons of that against our kitchen sink config on my bbb farm.. I'm using omap2plus_defconfig. Also, please leave a few boards running a vanilla kernel, a tag from Linus, then we can compare bb.org vs vanilla. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
[beagleboard] ADC generic_buffer.c issues || Accessing ADC from own kernel module
Hoping you guys can help me out on this: Goal: High sample rate of one ADC line via a kernel module and a corresponding user space app Now I know the PRU would be great for this- and I plan on also writing a pru version to bench mark the diff but I'm currently trying to get it done with a kernel module and its turned into one of those annoying obsessions that should work and damn it-- I am going to make it work So the goal is almost identical to the generic_buffer.c application referenced on this wiki [ http://processors.wiki.ti.com/index.php/AM335x_ADC_Driver's_Guide] but I've been fight it for awhile with no results. Current version: Linux beaglebone 3.8.13-bone70 1: pulled there git repo 2: applied the patch to get rid of the trigger stuff found here 3: compiled: gcc --static generic_buffer.c -o generic_buffer 4: Issues happen now because sysfs seem to be so different, I'm not sure contionous mode can be turned on? ./generic_buffer -n tiadc -l 256 -c 1 iio device number being used is 0 Problem reading scan element information diag /sys/bus/iio/devices/iio:device0 5: This error leads down the rabbit hole to this semi unhelpful blog post: https://e2e.ti.com/support/arm/sitara_arm/f/791/t/365886 yielding an errata about `Continuous capture mode is not supported in the 3.12 kernel`; great we are still rocking a 3.8.13 kernel thus should be fine? -- Couple questions: 1: Is there bbb kernel version that plays nice with the iio driver that will allow this generic_buffer.c to work? if so details please 2: if not has anyone modified this demo app to make things work? I've seen a couple posts about it here 2: Is there any information to say screw it and read the adc values directly in my own ko? I've seen instructions on gpio but not the adc lines. -- 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] ADC generic_buffer.c issues || Accessing ADC from own kernel module
On 08/12/2015 06:51 PM, Maro wrote:
So the goal is almost identical to the generic_buffer.c application
referenced on this wiki [
http://processors.wiki.ti.com/index.php/AM335x_ADC_Driver's_Guide]
It shouldn't matter, but if you are willing to upgrade the kernel (ubuntu
14.04, Linux kernel 4.1.4-ti-r9),
you could follow the updated version instead:
http://processors.wiki.ti.com/index.php/Linux_Core_ADC_User's_Guide
I just used Robert Nelson kernel (linux-image-4.1.4-ti-r9) and updated/added
the required entry
to the device tree:
tscadc@44e0d000 {
compatible = ti,am3359-tscadc;
reg = 0x44e0d000 0x1000;
interrupt-parent = 0x1;
interrupts = 0x10;
ti,hwmods = adc_tsc;
status = okay;
linux,phandle = 0xc5;
phandle = 0xc5;
tsc {
compatible = ti,am3359-tsc;
};
adc {
#io-channel-cells = 0x1;
compatible = ti,am3359-adc;
linux,phandle = 0xc6;
phandle = 0xc6;
ti,adc-channels = 0 1 2 3 4 5 6 7;
};
};
I didn't try with the .c application with this version yet, but I can read the
raw values directly:
(AN4 connected to the board analog ground)
~$ cat /sys/bus/iio/devices/iio\:device0/in_voltage4_raw
12
(AN4 connected to the board 1.8V )
~$ cat /sys/bus/iio/devices/iio\:device0/in_voltage4_raw
4083
cheers,
Nuno
--
--
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] Windows 10 Bone_D64.exe Failing
I have just upgraded to Windows 10 on a machine that I have not previously connected my BBB to. I had success on other windows 8 machines as well as SSHing using Putty. I have spent SOME time searching forums and not finding much at all on Windows 10. During the install of the Bone_D64.exe, the driver the status returned on all the drivers is Install Failed. Let the flaming begin. Or hopefully there is someone out there that has encountered and concurred this. -- 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] Windows 10 Bone_D64.exe Failing
On Aug 12, 2015 10:13 PM, mscleavite jeff.s...@gmail.com wrote: I have just upgraded to Windows 10 on a machine that I have not previously connected my BBB to. I had success on other windows 8 machines as well as SSHing using Putty. I have spent SOME time searching forums and not finding much at all on Windows 10. During the install of the Bone_D64.exe, the driver the status returned on all the drivers is Install Failed. Let the flaming begin. Or hopefully there is someone out there that has encountered and concurred this. You know the rules, first to upgrade gets to fix the issues. ;) Driver source: https://github.com/beagleboard/beaglebone-getting-started/tree/master/Drivers/Windows/src But there is a bigger issue, the signing key expired and Jason's working on getting that updated. 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] How can I check the camera data ??
The photo is my camera output data
8-bit to 16-bit data by attaching to upgrading to a 2-byte hex
Then I'm not sure what to do to try to change the HEX code to an image file
(BMP).
The code is marked in red
https://lh3.googleusercontent.com/-v6Xc18X2hNg/VcwJebXb3eI/FEo/MSnmbY5U-6o/s1600/%2525C1%2525A6%2525B8%2525F1_%2525BE%2525F8%2525C0%2525BD.png
#include stdio.h
#include linux/i2c.h
#include linux/i2c-dev.h
#include sys/ioctl.h
#include fcntl.h
#include errno.h
#include time.h
#include sys/stat.h
#include string.h
#include unistd.h
int i2c_open();
int i2c_write(int handle, unsigned char* buf, unsigned int length);
int i2c_write_byte(int handle, unsigned char val);
int i2c_write_ignore_nack(int handle, unsigned char addr_w, unsigned char*
buf, unsigned int length);
int i2c_close(int handle);
int delay_ms(unsigned int msec);
void init_ov7670();
void wr_rst_on();
void wr_rst_off();
void rd_rst_on();
void rd_rst_off();
void rd_en_on();
void rd_en_off();
void wr_en_on();
void wr_en_off();
void rd_clk_hi();
void rd_clk_lo();
void t_rst_off();
void t_rst_on();
int vsync();
void read_data();
/***
*** i2c function **
**/
int i2c_open(){
int file;
char filename[16];
sprintf(filename, /dev/i2c-1);
if((file=open(filename, O_RDWR))0){
fprintf(stderr, i2c_open error: %s\n, strerror(errno));
return(file);
}
if(ioctl(file, I2C_SLAVE, 0x21)){
fprintf(stderr, i2c_open error: %s\n, strerror(errno));
return(file);
}
return(file);
}
int i2c_write(int handle, unsigned char* buf, unsigned int length){
if(write(handle, buf, length) != length){
fprintf(stderr, i2c_write error: %s\n, strerror(errno));
return(-1);
}
return(length);
}
int i2c_write_byte(int handle, unsigned char val){
if(write(handle, val, 1)!=1){
fprintf(stderr, i2c_write_byte error: s\n, strerror(errno));
return(1);
}
return(1);
}
int i2c_write_ignore_nack(int handle, unsigned char addr_w, unsigned char*
buf, unsigned int length){
struct i2c_rdwr_ioctl_data msgset;
struct i2c_msg msgs[1];
msgs[0].addr=addr_w;
msgs[0].len=length;
msgs[0].flags=0 | I2C_M_IGNORE_NAK;
msgs[0].buf=buf;
if(ioctl(handle, I2C_RDWR, (unsigned long)msgset)0){
fprintf(stderr, i2c_write_ignore_nack error: %s\n, strerror(errno));
return(-1);
}
return(length);
}
int i2c_close(int handle){
if((close(handle))!=0){
fprintf(stderr, i2c_close error: s\n, strerror(errno));
return(-1);
}return(0);
}
/**
*delay function *
*/
int delay_ms(unsigned int msec){
int ret;
struct timespec a;
if(msec999){
fprintf(stderr, delay_ms error: delay value needs to be less than
999\n);
}
a.tv_nsec=((long)(msec))*1E6d;
a.tv_sec=0;
if((ret=nanosleep(a, NULL))!=0){
fprintf(stderr, delay_ms error: %s\n, strerror(errno));
}
return(0);
}
/*
* ov7670 function *
/
void wr_rst_on(void){
int fd_66=open(/sys/class/gpio/gpio66/value, O_WRONLY);
if(fd_66 0){
write(fd_66, 0, 1);
}else{
printf(Error: wr_rst_on\n);
}
close(fd_66);
}
void wr_rst_off(void){
int fd_66=open(/sys/class/gpio/gpio66/value, O_WRONLY);
if(fd_66 0){
write(fd_66, 1, 1);
}else{
printf(Error: wr_rst_off\n);
}
close(fd_66);
}
void rd_rst_on(void){
int fd_67=open(/sys/class/gpio/gpio67/value, O_WRONLY);
if(fd_67 0){
write(fd_67, 0, 1);
}else{
printf(Error: rd_rst_on\n);
}
close(fd_67);
}
void rd_rst_off(void){
int fd_67=open(/sys/class/gpio/gpio67/value, O_WRONLY);
if(fd_67 0){
write(fd_67, 1, 1);
}else{
printf(Error: rd_rst_off\n);
}
close(fd_67);
}
void rd_en_on(void){
int fd_69=open(/sys/class/gpio/gpio69/value, O_WRONLY);
if(fd_69 0){
write(fd_69, 0, 1);
}else{
printf(Error: rd_en_on\n);
}
close(fd_69);
}
void rd_en_off(void){
int fd_69=open(/sys/class/gpio/gpio69/value, O_WRONLY);
if(fd_69 0){
write(fd_69, 1, 1);
}else{
printf(Error: rd_en_off\n);
}
close(fd_69);
}
void wr_en_on(void){
int fd_68=open(/sys/class/gpio/gpio68/value, O_WRONLY);
if(fd_68 0){
write(fd_68, 1, 1);
}else{
printf(Error: wr_en_on\n);
}
close(fd_68);
}
void wr_en_off(void){
int fd_68=open(/sys/class/gpio/gpio69/value, O_WRONLY);
if(fd_68 0){
write(fd_68, 0, 1);
}else{
printf(Error: wr_en_off\n);
}
close(fd_68);
}
void rd_clk_hi(void){
int fd_22=open(/sys/class/gpio/gpio22/value, O_WRONLY);
if(fd_22 0){
write(fd_22, 1, 1);
}else{
printf(Error: rd_clk_hi\n);
}
close(fd_22);
}
void rd_clk_lo(void){
int fd_22=open(/sys/class/gpio/gpio22/value, O_WRONLY);
if(fd_22 0){
write(fd_22, 0, 1);
}else{
Re: [beagleboard] Beaglebone Black Wifi Managed and Master mode
On 08/12/2015 04:53 PM, Colin Bester wrote: USB WiFi to debian 3.8.13-boneX where they are able to connect to existing access points AND configure the wifi to act as an access point (master mode) using hostapd. Not using debian, but ubuntu 15.04 with hostapd in bridge mode, in the 5GHz wifi band: ~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid ~$ uname -srpo Linux 4.1.3-bone15 armv7l GNU/Linux ~$ lsusb Bus 001 Device 002: ID 148f:5572 Ralink Technology, Corp. RT5572 Wireless Adapter regards, Nuno -- -- 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 Black, ADC, C++, Eclipse, crosscompiling]First steps: is this doable?
Hi terra ÜÝÜ, thanks for your reply! Step 1 already done, I' m able to crosscompile and debug my bbb and the analog inputs are enabled! V. Il giorno mercoledì 12 agosto 2015 06:11:03 UTC+2, terra ÜÝÜ ha scritto: step 1. get the cross compile to work; I personally use http://gnutoolchains.com/beaglebone/ - beaglebone-gcc4.7.3.exe http://sysprogs.com/files/gnutoolchains/beaglebone/beaglebone-gcc4.7.3.exe Once you install it, open eclipse and try to compile the hello world program; once that works step 2 step 2. While I highly recommend the book (id get it make your life much easier); goto http://exploringbeaglebone.com/chapter1/ and read it till your reach the ADC bit; there is a github for the book, which has adc examples.; the book explains how to configure the adc, and so do a lot of website; recommend you search google for uenv.txt+BB-ADC On Tuesday, 11 August 2015 00:25:22 UTC+10, Valeria M. wrote: Hi everybody! I have a Beaglebone Black running the last Debian image and for my current project I need to cross-compile it with Eclipse from my WIndows OS. I'm fairly new both to microcontrollers and C++ (programming in general if I am to be honest) and right now I'm still trying to understand if my assignment is doable! Here it goes: I need to sample with the built-in ADC of the BBB an analog input, count the samples and find a way to 'force' the ADC-clock rollover to synchronize with an external clock Do you think this is feasible? I haven't find, strangely enough, anything online about the last two, I'm googling the wrong way? Regards, Valeria -- 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 Black, ADC, C++, Eclipse, crosscompiling]First steps: is this doable?
Hi TJF, thanks for your reply! I was hoping not to have to resort to use PRUs D: , for now the low accuracy given by the ADC clock will have to do. (btw why 10 kHz accuracy? it's caused by Linux non-real-time-ness? Otherwise ADC clock frequency should be 1,6 MHz max right?) Other random question: I suppose that if I sync the BBB system clock to an external clock the ADC's one won't be affected by it right? I mean they have different time 'domain'. Corss-compiling I'll be able to debug my procject. Valeria Il giorno martedì 11 agosto 2015 21:45:09 UTC+2, TJF ha scritto: Hi Valeria! The FSM module in the TSC_ADC_SS can either get triggered by software or by an external hardware event (TIMER4-7 or PRU_ICSS pr1_host_intr0). See SRM chapter 12 http://www.ti.com/lit/pdf/spruh73 for details. The best way how to synchronize with an external clock depends on the clock frequency and the timming accuracy requirements. For high accuracy or above ~10 KHz you may need customized software. But below that frequency you may be happy with a simple solution: The ADC operates at a fast sampling rate and the host CPU just reads the current value when the external clock fires. This is feasible with libpruio http://beagleboard.org/project/libpruio/. (You may see some latency when the host CPU is busy by any system interrupt.) BR BTW: Cross-compiling adds further problems. Why not compiling on the BBB? -- 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: BeagleBone Black doesn't sometimes start. Only Power LED is on
Here are my instructions how to solve boot issue on eMMC (see one warning
which I get below):
All commands should be run on BBB as root or add sudo.
Checkout and patch u-boot as described
here:
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
Do not build yet.
```
nano configs/am335x_boneblack_defconfig
```
Add these lines to the end of the file:
```
CONFIG_AUTOBOOT_KEYED=y
CONFIG_AUTOBOOT_PROMPT=Autobooting in %d seconds, enter \stop\ to stop\n
CONFIG_AUTOBOOT_STOP_STR=stop
CONFIG_AUTOBOOT_DELAY_STR=delay
```
Then compile u-boot running these commands:
```
make ARCH=arm CROSS_COMPILE=${CC} distclean
make ARCH=arm CROSS_COMPILE=${CC} am335x_boneblack_defconfig
make ARCH=arm CROSS_COMPILE=${CC}
```
Now you should have u-boot.img and MLO files compiled.
Write them to eMMC boot calling these commands:
```
dd if=MLO of=/dev/mmcblk0 count=1 seek=1 conv=notrunc bs=128k
dd if=u-boot.img of=/dev/mmcblk0 count=2 seek=1 conv=notrunc bs=384k
```
Done. Try to restart. If you have serial connection, check if you will see
message when BBB starts Autobooting in 1 seconds, enter stop to stop
Warning: After applying this I see warning when u-boot starts *** Warning
- bad CRC, using default environment. By this warning description here
(http://www.denx.de/wiki/view/DULG/WarningBadCRCUsingDefaultEnvironment)
seems like it's not critical or even important, but still, maybe someone
has an idea how to solve it?
Thanks.
Gedas
--
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: Shift register PRU
Am Montag, 10. August 2015 15:47:47 UTC+2 schrieb christia...@gmail.com: Hi folks, i'm currently working with the PRU of the beagle bone black to read and decode a SSI Protocol. Therefore I want to use the build in 28 bit shift register of the PRU. I found out, that the shift register is configured via the GPCFG0 (pru0) register. Can anyone explain to me, how I can use the shift register? I also haven't found the basic-adress of register GPCFG0, just the offset with 0x08. With best regards Christian Thanks a lot. I think I missed the part with the Local Data Memory Map. I'll try it out and post the code when it works as expected. Christian -- 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 Black, ADC, C++, Eclipse, crosscompiling]First steps: is this doable?
Hi! Host CPU and TSC_ADC_SS have different clock domains. Internal ADC clock rate is 24 MHz. The theoretical maximum sample rate is 1.6 Msamples/s (= 15 cycles@24MHz in single shot mode) or 1.74 Msamples/s (= 14 cycles in continous mode). In praxis it's 200 ksamples/s. The PRUSS are first choise for real time tasks with high timing accuracy. Below 10 ksamples/s the CPU latency (due to Linux non-real-time-ness) is small (less than 10 % on a vanilla system). When you need concrete hints, you'll have to specify your timing requirements: - Is the external clock a regular pulse train? - What frequency? - Which maximum latency is required between clock pulse and ADC sample? BR Am Mittwoch, 12. August 2015 08:34:02 UTC+2 schrieb Valeria M.: Hi TJF, thanks for your reply! I was hoping not to have to resort to use PRUs D: , for now the low accuracy given by the ADC clock will have to do. (btw why 10 kHz accuracy? it's caused by Linux non-real-time-ness? Otherwise ADC clock frequency should be 1,6 MHz max right?) Other random question: I suppose that if I sync the BBB system clock to an external clock the ADC's one won't be affected by it right? I mean they have different time 'domain'. Corss-compiling I'll be able to debug my procject. Valeria Il giorno martedì 11 agosto 2015 21:45:09 UTC+2, TJF ha scritto: Hi Valeria! The FSM module in the TSC_ADC_SS can either get triggered by software or by an external hardware event (TIMER4-7 or PRU_ICSS pr1_host_intr0). See SRM chapter 12 http://www.ti.com/lit/pdf/spruh73 for details. The best way how to synchronize with an external clock depends on the clock frequency and the timming accuracy requirements. For high accuracy or above ~10 KHz you may need customized software. But below that frequency you may be happy with a simple solution: The ADC operates at a fast sampling rate and the host CPU just reads the current value when the external clock fires. This is feasible with libpruio http://beagleboard.org/project/libpruio/. (You may see some latency when the host CPU is busy by any system interrupt.) BR BTW: Cross-compiling adds further problems. Why not compiling on the BBB? -- 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] Image 2015-7-26, kernel 4.1.3-ti-r6
On Wed, Aug 12, 2015 at 10:54 AM, Koellner Guenter dl4...@yahoo.de wrote: Hello Robert, what is the difference between 4.1.4-ti-r9 and 4.1.5-bone15 and which one is the one recommended for future use? Stick with 4.1.4-ti-r9, while i'm planning to push out 4.1.Y-boneX for the life of lts, the ti branch has more am335x enable-ment and testing.. Regards, -- Robert Nelson https://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] 4.1 repo
But i think audio (output) was still not working.. Hi Robert, Did you get a chance to look at the audio out and whether it's working? Kind Regards, Shadi -- 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] Is there a NOP opcode for the PRU?
This seems like a question that ought to be easy to answer but so far my searching has not turned up a clear one. I need a NOP on occasion to balance out timing on things and thus far every iteration I have tried of NOPx results in 'instruction illegal for core version'. I'm having to do dummy register loads now which looks kind of goofy. Is there a NOP instruction that works in PRU assembly? -- 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 learn to use TCP/IP on TI Sitara Starter Kit (Beaglebone)?
What is running on your board exactly? When it is an Linux/Ubuntu, there is nothing special, you can use any TCP/IP/sockets documentation for Linux that is out there. When you are using StarterWare bare metal code, you will find it makes use of lwIP. There is a extensive documentation available from this project and StarterWare comes with some examples about how to use it. In this special case it is not programming with a standard socket-API but access to RAW lwIP functions. Am Freitag, 26. Juni 2015 20:37:34 UTC+2 schrieb Robert Willy: Hi, I have a TI Sitara A8 (3358) Starter Kit board. I want to learn TCP/IP programming. Although I spend some time on TI forums, I do not find anything useful for me to write TCP/IP code. I think this StarterKit board is similar to Beaglebone board, thus, I ask the question in this forum. Can anyone help me on writing TCP/IP code? Please give me links, on this learning. I mean on Ubuntu to write the code here. 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] Error with http://repos.rcn-ee.net/debian/dists/wheezy/Release
I'm trying to update an old[is] BBB debian installation. When I do 'apt-get update' it mostly works but I'm getting the following errors:- Get:6 http://repos.rcn-ee.net wheezy Release [2,169 B] Err http://repos.rcn-ee.net wheezy Release W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repos.rcn-ee.net wheezy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D284E608A4C46402 W: Failed to fetch http://repos.rcn-ee.net/debian/dists/wheezy/Release W: Some index files failed to download. They have been ignored, or old ones used instead. How do I get things to catch up properly? -- Chris Green · -- 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: Do ADC filenames ever change, if so when?
Robert Nelson robertcnel...@gmail.com wrote: On Tue, Aug 11, 2015 at 3:42 PM, c...@isbd.net wrote: Robert Nelson robertcnel...@gmail.com wrote: On Fri, Aug 7, 2015 at 11:36 AM, c...@isbd.net wrote: I have a BBB running Debian GNU/Linux 7, 3.8.13-bone47 kernel. I.e. pretty standard. My raw ADC files are to be found at:- /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage0_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage1_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage2_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage3_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage4_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage5_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage6_raw /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage7_raw Currently I use a find() function written in python which walks the /sys/devices tree to find these files, but it's very slow. If I hard code the file names how often, if at all, will they need changing? ... and/or is there an easier way to find them, i.e. is there a configuration file somewhere that tells me where they are (or at least the non-constant bits of the path)? You should also see them here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/sysfs-bus-iio#n91 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw KernelVersion: 2.6.35 Contact: linux-...@vger.kernel.org Description: Raw (unscaled) differential voltage measurement equivalent to channel Y - channel Z where these channel numbers apply to the physically equivalent inputs when non differential readings are separately available. In differential only parts, then all that is required is a consistent labeling. Units after application of scale and offset are millivolts. That isn't really what I was asking for Robert. Actually it was... Walk: /sys/bus/iio/devices/iio* Well, very nearly! :-) If I 'cd /sys/bus/iio/devices/iio*' I get to '/sys/bus/iio/devices/iio:device0', is there any way of knowing that it's 'iio:device0'? It's still sort of clumsy doing a Python walk to find the files. -- Chris Green · -- 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] Error with http://repos.rcn-ee.net/debian/dists/wheezy/Release
On Wed, Aug 12, 2015 at 9:03 AM, c...@isbd.net wrote: I'm trying to update an old[is] BBB debian installation. When I do 'apt-get update' it mostly works but I'm getting the following errors:- Get:6 http://repos.rcn-ee.net wheezy Release [2,169 B] Err http://repos.rcn-ee.net wheezy Release W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repos.rcn-ee.net wheezy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D284E608A4C46402 W: Failed to fetch http://repos.rcn-ee.net/debian/dists/wheezy/Release W: Some index files failed to download. They have been ignored, or old ones used instead. How do I get things to catch up properly? Grab the newer keyring: wget https://rcn-ee.com/repos/debian/pool/main/r/rcn-ee-archive-keyring/rcn-ee-archive-keyring_2015.07.05~bpo70+20150705+1_all.deb sudo dpkg -i rcn-ee-archive-keyring_2015.07.05~bpo70+20150705+1_all.deb then: sudo apt-get update will be happy.. Regards, -- Robert Nelson https://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] Is there a NOP opcode for the PRU?
On 8/12/2015 11:45 AM, k...@cranehome.info wrote: This seems like a question that ought to be easy to answer but so far my searching has not turned up a clear one. I need a NOP on occasion to balance out timing on things and thus far every iteration I have tried of NOPx results in 'instruction illegal for core version'. I'm having to do dummy register loads now which looks kind of goofy. Is there a NOP instruction that works in PRU assembly? I don't think there's a specific NOP, but since the PRU doesn't have flag bits (except for carry) to worry about, you can alias any of a number of instructions to be a NOP: AND r1, r1, r1 OR r1, r1, r1 XOR r1, r1, 0 MOV r1, r1 ...and so on. -- Charles Steinkuehler char...@steinkuehler.net -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 08:27:05PM -0500, Felipe Balbi wrote: On Mon, Aug 10, 2015 at 03:04:52PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 2:59 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 2:55 PM, Felipe Balbi ba...@ti.com wrote: Hi again, On Mon, Aug 10, 2015 at 02:48:11PM -0500, Felipe Balbi wrote: Hi, I'll leave my BBB running with v4.1.0 vanilla, with Debian unstable userland. are you guys running with or without wkup_m3 firmware ? Is PM enabled at all ? The v4.1.x-ti-rX have pm enabled and wkup_m3 firmware.. m3: 0x191: 277eef8611e260a5d73a9e3773fff8f767fe2b01 head of next-upstream http://git.ti.com/gitweb/?p=ti-cm3-pm-firmware/amx3-cm3.git;a=shortlog;h=refs/heads/next-upstream all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. 2 days and still nothing. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Wed, Aug 12, 2015 at 03:08:33PM -0500, Felipe Balbi wrote: On Mon, Aug 10, 2015 at 08:27:05PM -0500, Felipe Balbi wrote: On Mon, Aug 10, 2015 at 03:04:52PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 2:59 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 2:55 PM, Felipe Balbi ba...@ti.com wrote: Hi again, On Mon, Aug 10, 2015 at 02:48:11PM -0500, Felipe Balbi wrote: Hi, I'll leave my BBB running with v4.1.0 vanilla, with Debian unstable userland. are you guys running with or without wkup_m3 firmware ? Is PM enabled at all ? The v4.1.x-ti-rX have pm enabled and wkup_m3 firmware.. m3: 0x191: 277eef8611e260a5d73a9e3773fff8f767fe2b01 head of next-upstream http://git.ti.com/gitweb/?p=ti-cm3-pm-firmware/amx3-cm3.git;a=shortlog;h=refs/heads/next-upstream all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. 2 days and still nothing. unfortunately gotta reboot though, need to test some other bug on MUSB. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
