[beagleboard] suspend_pad_conf entry missing in mounted debugfs directory
Hello all, I installed Ubuntu with Kernel 3.2 Image on my Beaglebone following Robert's instructions and use it successful for almost a year now (with peripherals such as an IMU, etc.). Now I want to use the power management on the board (suspend/resume) to wake it up from standby mode via a GPIO pin and followed the description given herehttp://processors.wiki.ti.com/index.php/AM335x_Linux_Power_Management_User_Guide#Usage_3, but the mounted debugfs directory “/debugfs/omap_mux/board/” only contains an entry “core”. The entry “suspend_pad_conf” where I can configure the wake-up source is missing. I also got the file “am335x-pm-firmware.bin” and added it to the firmware directory and the kernel config. I also verfified that it gets loaded by checking dmesg: [2.338288] Power Management for AM33XX family [2.343144] Trying to load am335x-pm-firmware.bin (60 secs timeout) [2.349868] Copied the M3 firmware to UMEM But the entry “suspend_pad_conf” does not show up in the directory. Any idea what I need to do in order to have that entry show up to use the functionality to specifiy the wake-up source(s)? Thanks a lot in advance for your help on this! I appreciate your feedback! Best Regards, 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] Measuring CPU(Cortex-A8) clock cycles
Thank you Grissiom On Tuesday, March 11, 2014 10:19:28 AM UTC+9, Grissiom Gu wrote: On Mon, Mar 10, 2014 at 11:00 PM, Paddu pradeep@gmail.comjavascript: wrote: Hi, Thank you for sharing very useful information. With your suggestions currently I am able to read the Cycle count using using this register. Please let me ask more question about CCNT register. Just for the confirmation, I would like to know is this a 32 bit register? or 64 bit? and what would happen if the count value is overflown, will the register reset to 0 ? It is a 32bit register(use mrc to read it instead of mrrc). If you are afraid of overflow and don't want to deal with the interrupt, you could set the D bit in PMCR register(c9, c12, 0). Than PMU will divide the cycle with 64. -- Cheers, Grissiom -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.
Hi, Gerald: Try removing C24. See if that helps. We saw the same problem. After removing C24 and C30 it seems to be solved! Our board is revision B. Robert -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] FBIO_WAITFORVSYNC on BBB
Hi, when I do an ioctl with FBIO_WAITFORVSYNC on my BBblack I got an error (Inappropriate ioctl for device). As far as I remember there was also no FBIO_WAITFORVSYNC on the original beagleboard. One had to use omap_dispc_register_isr. How can I wait for vsync on my BBB? Robert -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Kernel 3.12.x / GPMC
I have done some tests initializing the device tree. The file I have used
does work in kernel 3.8.13 without any issues. However, kernel 3.12.13
causes lots of trouble.
My .dts file is as follows:
/*
* optargs=capemgr.disable_partno=BB-BONE-EMMC-2G
* arch/arm/boot/dts/am335x-boneblack.dts, find the section starting
* with mmc2 { and in section change status = okay into disabled.
* do once : mmc dev 1
* mmc rstn 1
* in uBoot or in uEnv and then delete
*/
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = BB-BONE-MARK1;
version = 00A1;
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
P8.25,/* gpmc: gpmc_ad0 */
P8.24,/* gpmc: gpmc_ad1 */
P8.5,/* gpmc: gpmc_ad2 */
P8.6,/* gpmc: gpmc_ad3 */
P8.23,/* gpmc: gpmc_ad4 */
P8.22,/* gpmc: gpmc_ad5 */
P8.3,/* gpmc: gpmc_ad6 */
P8.4,/* gpmc: gpmc_ad7 */
P8.19,/* gpmc: gpmc_ad8 */
P8.13,/* gpmc: gpmc_ad9 */
P8.14,/* gpmc: gpmc_ad10 */
P8.17,/* gpmc: gpmc_ad11 */
P8.12,/* gpmc: gpmc_ad12 */
P8.11,/* gpmc: gpmc_ad13 */
P8.16,/* gpmc: gpmc_ad14 */
P8.15,/* gpmc: gpmc_ad15 */
P9.13,/* gpmc: gpmc_wpn */
P8.21,/* gpmc: gpmc_csn1 */
P8.18,/* gpmc: gpmc_clk */
P8.7,/* gpmc: gpmc_advn_ale */
P8.8,/* gpmc: gpmc_oen_ren */
P8.10,/* gpmc: gpmc_wen */
P8.9,/* gpmc: gpmc_ben0_cle */
P9.18,
P9.22,
gpmc,
/* the reset pin */
eMMC_RSTn;
#address-cells = 1;
#size-cells = 1;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
gpmc_pins: pinmux_gpmc_pins {
pinctrl-single,pins =
0x000 0x30/* gpmc_ad0.gpmc_ad0 MODE0 | INPUT |
PULLUP */
0x004 0x30/* gpmc_ad1.gpmc_ad1 MODE0 | INPUT |
PULLUP */
0x008 0x30/* gpmc_ad2.gpmc_ad2 MODE0 | INPUT |
PULLUP */
0x00C 0x30/* gpmc_ad3.gpmc_ad3 MODE0 | INPUT |
PULLUP */
0x010 0x30/* gpmc_ad4.gpmc_ad4 MODE0 | INPUT |
PULLUP */
0x014 0x30/* gpmc_ad5.gpmc_ad5 MODE0 | INPUT |
PULLUP */
0x018 0x30/* gpmc_ad6.gpmc_ad6 MODE0 | INPUT |
PULLUP */
0x01C 0x30/* gpmc_ad7.gpmc_ad7 MODE0 | INPUT |
PULLUP */
0x020 0x30/* gpmc_ad8.gpmc_ad8 MODE0 | INPUT |
PULLUP */
0x024 0x30/* gpmc_ad9.gpmc_ad9 MODE0 | INPUT |
PULLUP */
0x028 0x30/* gpmc_ad10.gpmc_ad10 MODE0 | INPUT |
PULLUP */
0x02C 0x30/* gpmc_ad11.gpmc_ad11 MODE0 | INPUT |
PULLUP */
0x030 0x30/* gpmc_ad12.gpmc_ad12 MODE0 | INPUT |
PULLUP */
0x034 0x30/* gpmc_ad13.gpmc_ad13 MODE0 | INPUT |
PULLUP */
0x038 0x30/* gpmc_ad14.gpmc_ad14 MODE0 | INPUT |
PULLUP */
0x03C 0x30/* gpmc_ad15.gpmc_ad15 MODE0 | INPUT |
PULLUP */
0x080 0x08/* gpmc_cscn1.gpmc_cscn1 MODE0 | OUTPUT */
0x08C 0x28/* gpmc_clk.gpmc_clk MODE0 | OUTPUT */
0x090 0x08/* gpmc_advn_ale.gpmc_advn_ale MODE0 |
OUTPUT */
0x094 0x08/* gpmc_oen_ren.gpmc_oen_ren MODE0 |
OUTPUT */
0x098 0x08/* gpmc_wen.gpmc_wen MODE0 | OUTPUT */
0x09C 0x08/* gpmc_ben0_cle.gpmc_ben0_cle MODE0 |
OUTPUT */
0x078 0x08/* gpmc_ben1_cle.gpmc_ben1_cle MODE0 |
OUTPUT */
;
};
fpga_config_pins: pinmux_fpga_config_pins {
pinctrl-single,pins =
/* config clk and data */
0x158 0x17 /* spi1_d1 MODE3 | INPUT | PULLUP ,
serial data config */
0x150 0x17/* spi1_sclk MODE3 | INPUT | PULLUP,
serial clock config */
;
};
};
};
fragment@1 {
target = gpmc;
depth = 1;/* only create devices on depth 1 */
/* stupid warnings */
#address-cells = 1;
#size-cells = 1;
__overlay__ {
status = okay;
#address-cells = 2;
#size-cells = 1;
pinctrl-names = default;
pinctrl-0 = gpmc_pins;
/* chip select ranges */
ranges = 1 0 0x0100 0x100;
camera{
compatible = mark1;
status = okay;
pinctrl-names = default;
pinctrl-0 = fpga_config_pins;
reset = rstctl 0 0;
reset-names =
[beagleboard] Support for the Embest 14pin jtag XDS100v2 USB Emulator in Beaglebone black
Hi, Is there is anyway to use the Embest XDS 100v2 14 pin jtag for the beaglebone black, i referred the difference for the 20pin and 14pin here: http://processors.wiki.ti.com/index.php/JTAG_Connectors But any turnarounds to use this jtag in BBB which have the 20 pin connector. Thanks, Elavarasu. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: BBB + PREEMPT_RT
I have never heard of a PREEMPT_RT capable kernel for the BBB besides that from OSADL. I have recently had a conversation with Robert C. Nelson. He told me, that kernel 3.8 has problems and did never support PREEMPT_RT. The 3.8-rt branch is no longer in development. Officially, the BBB does not even support simple PREEMPT. So I guess your only chance is the OSADL kernel. The current version is 3.12.13-rt21. It seems to work. But there are issues with GPMC. I have created a new thread on this topic here: https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/uac_Zh41LYo. Am Samstag, 8. März 2014 22:15:04 UTC+1 schrieb fj.r...@openmailbox.org: I have lately also unsuccessfully tried to install RT_PREEMPT on BBB. What I have done until now (and failed) is: A. 1. Get the sources from here: https://github.com/beagleboard/kernel/tree/3.8-rt 2. Before make command, enable Full Preemption under kernel features options. 3. Compile. When testing on BBB, the kernel doesn't boot. B. 1. Get the sources from here: https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8 2. ./build_kernel.sh 3. Download the rt patch from here: https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/patch-3.8.13.14-rt27.patch.bz2into KERNEL folder 4. patch p1 patch-3.8.13.14-rt27.patch 5. From here, it turned a little bit weird since approximately 21 HUNKS failed. Reading this post: https://groups.google.com/forum/#!topic/beagleboard/aAufDe13SeQ then I re-edited the .patch file taking away the modifications in cpsw.h and cpsw.c (lines 5825 to 7346 from .patch file). 6. Then repeated steps 1 through 4 again, but using the edited patch. 7. Use menuconfig to activate Full-Preemption. 8. ./tools/rebuild.sh 9. ./tools/install_kernel.sh (with the modifications in the system.sh file) 10. Plug the SD card in the BBB. and it never booted. I have seen the osadl 3.8.12 kernel, but I'm more interested in using the 3.8.13 kernel. If anyone could give away any ideas, I would be really grateful. Thank you for your 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.
[beagleboard] Re: Kernel/device tree road-map for the BBB
@Chris: Hi Chris, what usb-wifi devices are you using? Is this the only reason to move to 3.13? I have two wifi devices(Netgear WNA1100 and Logic Supply UWN200) working very reliably with RCN's debian 3.8.13-bone41. Kernel drivers are built into -bone41 for both. I would recommend devices with these chipsets (Atheros or Ralink/Mediatek). Regards - Eamonn -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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: Error Listening To Socket - MOOS-IvP won't run on Beaglebone Black
Ok so after much debugging I have found that when the Listen thread socket is started it starts as a UDP socket (determined using lsof) when it should be a TCP socket. What would cause this? On Wednesday, 5 March 2014 20:32:54 UTC+10:30, haeusler...@gmail.com wrote: I managed to get it to work in single threaded mode. Has any one had any issues with threads with the BBB? On Wednesday, 5 March 2014 18:58:42 UTC+10:30, haeusler...@gmail.comwrote: I am attempting to run MOOS-IvPhttp://oceanai.mit.edu/moos-ivp/pmwiki/pmwiki.php?n=Main.HomePageon a Beaglebone Black On attempting to run the MOOS database it continuously throws the exception Exception Thrown in listen loop: Error Listening To Socket. Operation not supported This software runs on a Raspberry Pi Any ideas what might be the issue? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] 2014-03-04 Debian flasher doesn't flash the eMMC in BBB
After retry several times, I found I can flash the NAND with the latest Debian. Maybe, there is something wrong over there, but I can use it now... On Tue, Mar 11, 2014 at 11:38 AM, Sam Hon samhonboo...@gmail.com wrote: Hi Gerald, I did hold S2 until after the board powers up. Before I updated Angstrom several times, they were all success. I didn't know where I did wrong. My PCB is version A5C. What information should I give to make it clear and easy to debug. Thanks, On Fri, Mar 7, 2014 at 8:32 PM, Gerald Coley ger...@beagleboard.orgwrote: Are you holding S2 pressed until after the board powers up? Gerald On Fri, Mar 7, 2014 at 6:21 AM, Sam Hon samhonboo...@gmail.com wrote: I tried to update the latest version Debian in http://beagleboard.org/latest-images/ Download BeagleBone Black (eMMC flasher) Debian (BeagleBone Black - 2GB eMMC) 2014-03-04 and use Image Writer to write into SD card. However, when pressing on S2 (boot Switch) and power on,image in SD card isn't flashed into eMMC but BBB boots from it. How do I do to flash the image into BBB eMMC not boot from it. Will be a big different between Angostrom and Debian? because I use Angostrom before to control LED on the board, GPIO, UART0 and so on. Those codes remain the same or I have to modify it. 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. -- 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/5qcEHCsQvyE/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.
Re: [beagleboard] 2014-03-04 Debian flasher doesn't flash the eMMC in BBB
On Tue, Mar 11, 2014 at 8:00 AM, Sam Hon samhonboo...@gmail.com wrote: After retry several times, I found I can flash the NAND with the latest Debian. Maybe, there is something wrong over there, but I can use it now... That's a little odd, as they are the same flashing backend. 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] power adapter question
Yes. They have the same connectors. They have the same polarity. And they are both 5Vr. Now, as there is no official XM power supply, you need to make sure the one you bought has the right amount of current for you application. Gerald On Mon, Mar 10, 2014 at 10:35 PM, madjac...@gmail.com wrote: Can I use the same BB-XM Power supply for the BBBlack? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Problems installing WSPR and RTL-SDR on Beaglebone Debian
Hello, After trying Angstrom, Ubuntu, Debian, Angstrom I decided to install Debian on the emmc. No problem. FLdigi and several other amateur radio programs are running fine. The main reason for the BBB was a WSPR monitor. So I got the sources installed the depending libraries, made configure and everything went well: creating Makefile, ... Installing: ..., but in the directory was no make file. Same problem with RTL-SDR, configuration went without complaints, but no make file. I can't open the py-file due to missing files. I ran this also as root and both sources compile fine on other machines. Debian wheezy 7.4 / 3.8.13-bone40 / Xfce. Any pointers? Thanks in advance for your help. 73 de Hajo -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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.
Correct. You can also solve the issue by using the correct SW as well. The issue is that the processors interferes with the default address settings when the PHY reads the pins. If the SW looks for the other addresses, it works fine. Also, removing these caps will also create issues where the board does not boot at all. Not exactly a good trade. Gerald On Tue, Mar 11, 2014 at 3:25 AM, Robert Kuhn rob...@ku.hn wrote: Hi, Gerald: Try removing C24. See if that helps. We saw the same problem. After removing C24 and C30 it seems to be solved! Our board is revision B. Robert -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Support for the Embest 14pin jtag XDS100v2 USB Emulator in Beaglebone black
You will need an adapter. Gerald On Tue, Mar 11, 2014 at 5:59 AM, Elavarasu elavarasu@gmail.com wrote: Hi, Is there is anyway to use the Embest XDS 100v2 14 pin jtag for the beaglebone black, i referred the difference for the 20pin and 14pin here: http://processors.wiki.ti.com/index.php/JTAG_Connectors But any turnarounds to use this jtag in BBB which have the 20 pin connector. Thanks, Elavarasu. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] suspend_pad_conf entry missing in mounted debugfs directory
Hello all, I installed Ubuntu with Kernel 3.2 Image on my Beaglebone following Robert's instructions and use it succesfully for almost a year now (with peripherals such as IMU, etc.). Now I want to use the power management on the board (suspend/resume) and want to wake-up the board via a GPIO pin. I followed e.g. the instrunction given herehttp://processors.wiki.ti.com/index.php/AM335x_Linux_Power_Management_User_Guide#Usage_3, but the mounted debugfs directory “/debugfs/omap_mux/board/” only contains an entry “core”. The entry “suspend_pad_conf” where I can configure the wake-up source is missing. I also got the file “am335x-pm-firmware.bin” from the web which needs to be loaded on startup for suspend/resume support and added it to the firmware directory and the kernel config. I also verfified that it gets loaded by checking dmesg: [2.338288] Power Management for AM33XX family [2.343144] Trying to load am335x-pm-firmware.bin (60 secs timeout) [2.349868] Copied the M3 firmware to UMEM But the entry “suspend_pad_conf” does not show up in the directory. Do you have an idea what I need to do in order to have that entry show up to be able to define the wakeup source(s)? Thanks a lot in advance for your help on this! Best Regards, 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] good, *current* online tutorial for capemgr for BBB?
Could someone explain to me how to play the uartpatchpatch.gz to a 3.12 kernel. I am kinda new to Linux and need UART1 (ttyO1) working on a non 3.8 kernel for the beaglebone Black. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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.
Gerald: Correct. You can also solve the issue by using the correct SW as well. The issue is that the processors interferes with the default address settings when the PHY reads the pins. If the SW looks for the other addresses, it works fine. Also, removing these caps will also create issues where the board does not boot at all. Not exactly a good trade. I got my Ubuntu 12.04 from here: http://www.armhf.com/index.php/download/ When I searched for beaglebone+ubuntu I got many results. So its hard to find the correct software. So where can I find it? Do you have a link? Thanks - Robert -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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.
My SW guy is currently out. There is a change that needs to be made. I will get with him next week to make sure the change gets done. Gerald On Tue, Mar 11, 2014 at 8:26 AM, Robert Kuhn rob...@ku.hn wrote: Gerald: Correct. You can also solve the issue by using the correct SW as well. The issue is that the processors interferes with the default address settings when the PHY reads the pins. If the SW looks for the other addresses, it works fine. Also, removing these caps will also create issues where the board does not boot at all. Not exactly a good trade. I got my Ubuntu 12.04 from here: http://www.armhf.com/index.php/download/ When I searched for beaglebone+ubuntu I got many results. So its hard to find the correct software. So where can I find it? Do you have a link? Thanks - Robert -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Beaglebone Black Ethernet Phy Not Detected on Boot.
On Tue, Mar 11, 2014 at 8:26 AM, Robert Kuhn rob...@ku.hn wrote: Gerald: Correct. You can also solve the issue by using the correct SW as well. The issue is that the processors interferes with the default address settings when the PHY reads the pins. If the SW looks for the other addresses, it works fine. Also, removing these caps will also create issues where the board does not boot at all. Not exactly a good trade. I got my Ubuntu 12.04 from here: http://www.armhf.com/index.php/download/ When I searched for beaglebone+ubuntu I got many results. So its hard to find the correct software. So where can I find it? Do you have a link? My debian image is now hosted here: http://beagleboard.org/latest-images For ubuntu you can find images from the same script that generates that image ^ here: http://elinux.org/BeagleBoardUbuntu But honestly, due to ubuntu's current short eol cycles (9 months), ubuntu isn't that great anymore for long run embedded applications. So i've been losing interest in support ubuntu. 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] good, *current* online tutorial for capemgr for BBB?
On Tue, Mar 11, 2014 at 5:26 AM, rinzevd...@gmail.com wrote: Could someone explain to me how to play the uartpatchpatch.gz to a 3.12 kernel. I am kinda new to Linux and need UART1 (ttyO1) working on a non 3.8 kernel for the beaglebone Black. Start with the debian image here: http://beagleboard.org/latest-images cd /opt/scripts/ git pull ./tools/update_kernel.sh --beta-kernel reboot edit: /boot/uboot/uEnv.txt changes CAPE= to CAPE=ttyO1 (not eMMC is disabled when you do that^ i need to fix that, so only use the microSD image) 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] Kernel 3.12.x / GPMC
I don't think capemgr/device tree overlays are supported anymore. Robert
Nelson has proposed another solution with 3.13.x kernels that seems to
work for me:
https://github.com/RobertCNelson/linux-dev/commit/685b182ca956dcd8396ca69af5c678c43a102d03
HTH,
Dave.
On 03/11/2014 05:05 AM, quikcj...@gmail.com wrote:
I have done some tests initializing the device tree. The file I have
used does work in kernel 3.8.13 without any issues. However, kernel
3.12.13 causes lots of trouble.
My .dts file is as follows:
/*
* optargs=capemgr.disable_partno=BB-BONE-EMMC-2G
* arch/arm/boot/dts/am335x-boneblack.dts, find the section starting
* with mmc2 { and in section change status = okay into disabled.
* do once : mmc dev 1
* mmc rstn 1
* in uBoot or in uEnv and then delete
*/
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = BB-BONE-MARK1;
version = 00A1;
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
P8.25,/* gpmc: gpmc_ad0 */
P8.24,/* gpmc: gpmc_ad1 */
P8.5,/* gpmc: gpmc_ad2 */
P8.6,/* gpmc: gpmc_ad3 */
P8.23,/* gpmc: gpmc_ad4 */
P8.22,/* gpmc: gpmc_ad5 */
P8.3,/* gpmc: gpmc_ad6 */
P8.4,/* gpmc: gpmc_ad7 */
P8.19,/* gpmc: gpmc_ad8 */
P8.13,/* gpmc: gpmc_ad9 */
P8.14,/* gpmc: gpmc_ad10 */
P8.17,/* gpmc: gpmc_ad11 */
P8.12,/* gpmc: gpmc_ad12 */
P8.11,/* gpmc: gpmc_ad13 */
P8.16,/* gpmc: gpmc_ad14 */
P8.15,/* gpmc: gpmc_ad15 */
P9.13,/* gpmc: gpmc_wpn */
P8.21,/* gpmc: gpmc_csn1 */
P8.18,/* gpmc: gpmc_clk */
P8.7,/* gpmc: gpmc_advn_ale */
P8.8,/* gpmc: gpmc_oen_ren */
P8.10,/* gpmc: gpmc_wen */
P8.9,/* gpmc: gpmc_ben0_cle */
P9.18,
P9.22,
gpmc,
/* the reset pin */
eMMC_RSTn;
#address-cells = 1;
#size-cells = 1;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
gpmc_pins: pinmux_gpmc_pins {
pinctrl-single,pins =
0x000 0x30/* gpmc_ad0.gpmc_ad0 MODE0 | INPUT |
PULLUP */
0x004 0x30/* gpmc_ad1.gpmc_ad1 MODE0 | INPUT |
PULLUP */
0x008 0x30/* gpmc_ad2.gpmc_ad2 MODE0 | INPUT |
PULLUP */
0x00C 0x30/* gpmc_ad3.gpmc_ad3 MODE0 | INPUT |
PULLUP */
0x010 0x30/* gpmc_ad4.gpmc_ad4 MODE0 | INPUT |
PULLUP */
0x014 0x30/* gpmc_ad5.gpmc_ad5 MODE0 | INPUT |
PULLUP */
0x018 0x30/* gpmc_ad6.gpmc_ad6 MODE0 | INPUT |
PULLUP */
0x01C 0x30/* gpmc_ad7.gpmc_ad7 MODE0 | INPUT |
PULLUP */
0x020 0x30/* gpmc_ad8.gpmc_ad8 MODE0 | INPUT |
PULLUP */
0x024 0x30/* gpmc_ad9.gpmc_ad9 MODE0 | INPUT |
PULLUP */
0x028 0x30/* gpmc_ad10.gpmc_ad10 MODE0 | INPUT
| PULLUP */
0x02C 0x30/* gpmc_ad11.gpmc_ad11 MODE0 | INPUT
| PULLUP */
0x030 0x30/* gpmc_ad12.gpmc_ad12 MODE0 | INPUT
| PULLUP */
0x034 0x30/* gpmc_ad13.gpmc_ad13 MODE0 | INPUT
| PULLUP */
0x038 0x30/* gpmc_ad14.gpmc_ad14 MODE0 | INPUT
| PULLUP */
0x03C 0x30/* gpmc_ad15.gpmc_ad15 MODE0 | INPUT
| PULLUP */
0x080 0x08/* gpmc_cscn1.gpmc_cscn1 MODE0 |
OUTPUT */
0x08C 0x28/* gpmc_clk.gpmc_clk MODE0 | OUTPUT */
0x090 0x08/* gpmc_advn_ale.gpmc_advn_ale MODE0
| OUTPUT */
0x094 0x08/* gpmc_oen_ren.gpmc_oen_ren MODE0 |
OUTPUT */
0x098 0x08/* gpmc_wen.gpmc_wen MODE0 | OUTPUT */
0x09C 0x08/* gpmc_ben0_cle.gpmc_ben0_cle MODE0
| OUTPUT */
0x078 0x08/* gpmc_ben1_cle.gpmc_ben1_cle MODE0
| OUTPUT */
;
};
fpga_config_pins: pinmux_fpga_config_pins {
pinctrl-single,pins =
/* config clk and data */
0x158 0x17 /* spi1_d1 MODE3 | INPUT | PULLUP
, serial data config */
0x150 0x17/* spi1_sclk MODE3 | INPUT | PULLUP,
serial clock config */
;
};
};
};
fragment@1 {
target = gpmc;
depth = 1;/* only create devices on depth 1 */
/* stupid warnings */
#address-cells = 1;
#size-cells = 1;
__overlay__ {
status = okay;
#address-cells = 2;
#size-cells = 1;
pinctrl-names = default;
pinctrl-0 = gpmc_pins;
/* chip select
[beagleboard] Re: not able to connect to Beaglebone black
Any link or tutorial will be appreciated. On Monday, March 10, 2014 8:55:56 PM UTC+5:30, Kumar Gaurav wrote: Hi All, I have bought beaglebone black and used tutorials to setup it. I started with start.html (provided with BBB). installed rules(mkudevrule.sh). Tried opening 192.168.7.2 in browser but didn't succeded. I tried finding IP of BBB using arp-scan and again got nothing. I found somewhere that by default ssh doesn't work on angstrom so i flashed debian into an SD card and booted with that ( i refer this tute: http://avedo.net/653/flashing-ubuntu-13-04-or-debian-wheezy-to-the-beaglebone-black-emmc/), again i am not able to connect with BBB. In start.html there's a link for *USB to virtual Ethernet.* I don't know how would i install this (if i need to) My system is detail is kumar@anandlinux:~$ uname -a Linux anandlinux.com 3.2.0-52-generic #78-Ubuntu SMP Fri Jul 26 16:21:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux One of my friend suggested that i should use FTDI to USB cable to connect with BBB USB mini to USB won't work. Is that true? Currently i'm using USB Mini to USB. I tried using screen command too screen /dev/ttyUSB1 115200 but that too doesn't help. Please suggest how can i connect. I've been Googling since 5th march and still clueless. I'm using this forum for first time so if i used wrong topic/specific topic etc then let me know. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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: Kernel/device tree road-map for the BBB
Eamonn, I have this device, which I bought from adafruit... I looked around and saw a lot of people having problems with this guy. Bus 001 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter http://www.adafruit.com/products/814 Yeah if it's cheap, it might be better just to get a new adapter and save myself the hassle. On Tuesday, March 11, 2014 6:19:54 AM UTC-5, Eamonn BotheringElectrons wrote: @Chris: Hi Chris, what usb-wifi devices are you using? Is this the only reason to move to 3.13? I have two wifi devices(Netgear WNA1100 and Logic Supply UWN200) working very reliably with RCN's debian 3.8.13-bone41. Kernel drivers are built into -bone41 for both. I would recommend devices with these chipsets (Atheros or Ralink/Mediatek). Regards - Eamonn -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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: Availability - how come nobody has any BeagleBone Black to sell?
I wanted to know if someone got recently a LCD7 CAP ? Because I'm still waiting since January .. !!! On Mon, Mar 10, 2014 at 3:45 PM, Gerald Coley ger...@beagleboard.orgwrote: Actually most shops do. That is why we can never catch up.; Gerald On Mon, Mar 10, 2014 at 9:40 AM, Satz Klauer satzkla...@googlemail.comwrote: On Mon, Mar 10, 2014 at 2:53 PM, Gerald Coley ger...@beagleboard.org wrote: It is real. But, if you wait until you see it in stock, it may be a while before you will get one. This is not a solution, most shops don't allow to order something when they don't have the hardware in stock. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Re: BBB PRU input test
I read your last email with attention by still I can't understad why my
code is not working. I a few words:
The code works when properly when I comment the line WBS r31.t15 //Wait
til GPIO-15-in is high... P9_24
*PINMUX DTS:*
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = BB-BONE-W;
version = 00A0;
exclusive-use = P9.24;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
mygpio: pinmux_mygpio{
pinctrl-single,pins =
0x184 0x36 /* P9 24 pr1_pru0_pru_r31_16.GPIO0_15: | PULLUP | MODE6
| INPUT */
;
};
};
};
fragment@1 {
target = ocp;
__overlay__ {
test_helper: helper {
compatible = bone-pinmux-helper;
pinctrl-names = default;
pinctrl-0 = mygpio;
status = okay;
};
};
};
fragment@2{
target = pruss;
__overlay__ {
status = okay;
};
};
};
*PIN MUX STATUS:*
# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins | grep pin 97
pin 97 (44e10984) 0036 pinctrl-single
*UNAME +DIST:*
# uname -a
Linux don-t001 3.8.13-bone30 #1 SMP Thu Nov 14 11:19:20 UTC 2013 armv7l
armv7l armv7l GNU/Linux
# cat /etc/issue
Ubuntu 12.04.3 LTS \n \l
*ASM CODE:*
.origin 0
.entrypoint START
#define PRU0_ARM_INTERRUPT 19
#define AM33XX
#define GPIO1 0x4804c000
#define GPIO_CLEARDATAOUT 0x190
#define GPIO_SETDATAOUT 0x194
START:
//Enable OCP master port
LBCO r0, C4, 4, 4
CLR r0, r0, 4 // Clear SYSCFG[STANDBY_INIT] to enable OCP master port
SBCO r0, C4, 4, 4
MOV r1, 1000 //# cycles
INPUTTEST:
WBS r31.t15 //Wait til GPIO-15-in is high... P9_24
SUB r1, r1, 1 //Subtract from counter
QBNE INPUTTEST, r1, 0 //Loop if counter not at zero
// Send notification to Host for program completion
MOV R31.b0, PRU0_ARM_INTERRUPT+16
MOV r1, 0
HALT
*INIT PROGRAM USING PyPRUSS:*
#!/usr/bin/python
''' ddr_write.py - Finds the DDR address and size, passes that info to the
PRU0
data memory, executes a program and reads back data from the first and last
banks'''
import pypruss
import mmap
import struct
pypruss.modprobe()
ddr_addr = pypruss.ddr_addr()
ddr_size = pypruss.ddr_size()
print DDR memory address is 0x%x and the size is 0x%x%(ddr_addr, ddr_size)
ddr_offset = ddr_addr-0x1000
ddr_filelen = ddr_size+0x1000
ddr_start = 0x1000
ddr_end = 0x1000+ddr_size
pypruss.init() # Init the PRU
pypruss.open(0) # Open PRU event 0 which is PRU0_ARM_INTERRUPT
pypruss.pruintc_init() # Init the interrupt controller
pypruss.pru_write_memory(0, 0, [ddr_addr, ddr_addr+ddr_size-4]) # Put the
ddr address in the first region
pypruss.exec_program(0, ./ddr_write.bin) # Load firmware ddr_write.bin
on PRU 0
pypruss.wait_for_event(0) # Wait for event 0 which is connected to
PRU0_ARM_INTERRUPT
pypruss.clear_event(0) # Clear the event
pypruss.exit() # Exit PRU
with open(/dev/mem, r+b) as f: # Open the physical memory device
ddr_mem = mmap.mmap(f.fileno(), ddr_filelen, offset=ddr_offset) # mmap the
right area
read_back = struct.unpack(L, ddr_mem[ddr_start:ddr_start+4])[0] # Parse
the data
print The first 4 bytes of DDR memory reads +hex(read_back)
ddr_mem.close() # Close the memory
f.close() # Close the file
No way to read the P9_24 PIN From BBB using PRUSS
May be the *WBS *does no work as I think . a week working on that and
still nothing.
El martes, 11 de marzo de 2014 00:40:04 UTC-3, Brandon I escribió:
When I do an interruput up or down the ASM keeps waiting and nothing
Read my previous email. Your code will not work as is.
On Mon, Mar 10, 2014 at 8:11 PM, Manu manuelbe...@gmail.com javascript:
wrote:
My DTS is:
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = BB-BONE-W;
version = 00A0;
exclusive-use = P9.24;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
mygpio: pinmux_mygpio{
pinctrl-single,pins =
0x184 0x16 /* P9 24 pr1_pru0_pru_r31_16.GPIO0_15: | PULLUP |
MODE6 | INPUT */
;
};
};
};
fragment@1 {
target = ocp;
__overlay__ {
test_helper: helper {
compatible = bone-pinmux-helper;
pinctrl-names = default;
pinctrl-0 = mygpio;
status = okay;
};
};
};
fragment@2{
target = pruss;
__overlay__ {
status = okay;
pinctrl-names = default;
pinctrl-0 = mygpio;
};
};
};
and the
cat /sys/devices/bone_capemgr.*/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--
[beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support
What are you looking for? A Ubuntu 13.10 image with Chipsee support? On Saturday, March 8, 2014 2:19:27 AM UTC-5, Nicholas Sparks wrote: Do you have this available for download? I was checking your other posts, but I don't see anything. A Google search pointed me to a 12.04 upload you did a 1.5 months ago. On Friday, February 28, 2014 5:00:43 AM UTC-5, Christian Ruocco wrote: Hi, My image is configured to give the ethernet device the static IP address 192.168.0.21 and default gateway 192.168.0.1. If those settings aren’t compatible with your network setup, change them in the /boot/uboot/uEnv.txt file. I had to hard-code them because I wasn’t getting any joy setting up eth0 from ubuntu. I’m still not sure why. So I chose to use uboot to help out. l8r, Xris. On 28 Feb 2014, at 05:28, huynhng...@gmail.com wrote: I have a problem that my ubuntu 12.04 BBB as you said me to set up can not connect to the Internet. How can I solve this problem? //- Vào 17:08:50 UTC+7 Thứ tư, ngày 26 tháng hai năm 2014, knsh...@gmail.comđã viết: In my case, Ubuntu 12.04 BBB image has the random reboot issue! Can the random reboot issue be fixed by updating Ubuntu kernel? On Thursday, January 23, 2014 8:12:25 PM UTC+2, xris@googlemail.comwrote: Hey guys, As promised. Ubuntu 12.04 BBB image for the Chipsee 7” 1024x600 LCD touchscreen. Grab it here: http://www.fileswap.com/dl/sdFGPZoIw6/ You should find yourself downloading bbb-ubuntu-12.04-for-community.xzhttp://www.fileswap.com/dl/sdFGPZoIw6/bbb-ubuntu-12.04-for-community.xz.html Just extract and write that to your SD card (4gb expected) with something like: *cat bbb-ubuntu-12.04-for-community.xz | xz -d /dev/sdX* Note it’s a raw sector dump NOT a tarball, so extract straight to your SD card device. (eg. /dev/sdx, NOT /dev/sdx1) Also note this image doesn’t install or boot from MMC so make sure you’ve got the SD card selected on the boot switch thing. Once the extract is complete, simply slap it into the BBB and boot. It should come up with the Chipsee splash screen but then boot into Ubuntu 12.04 after a while. Hope this helps. l8r, Xris. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Connecting beagle bone black to laptop LAN tthen to 3G USB data card
Hello vinayak, you connected data card to your PC or beagle itself?? because i can access Internet on my PC but when i follow the procedure you mentioned it did not work!! i access internet on Ubuntu using WVDIAl package!! will appriciate any help. On Tuesday, November 5, 2013 1:53:17 AM UTC-5, Vinayak Aghor wrote: Hi I again tried with ubuntu OS on my PC Connected USB 3G.. Verified i can access internet. it is working fine.. as I am posting this on group I tried following on BBB I have attached picture For experts: kindly check that I could do that But somehow same steps did not work with windows vista on PC.. Thanks to ubuntu On Friday, 25 October 2013 12:05:09 UTC+5:30, vinayak aghor wrote: Is there any one... who can help? On Sunday, 13 October 2013 13:51:27 UTC+5:30, vinayak aghor wrote: I did try following but I did nto get break through - /sbin/route add default gw 192.168.7.1 - echo nameserver 8.8.8.8 /etc/resolv.conf Please help On Sunday, 13 October 2013 12:29:39 UTC+5:30, vinayak aghor wrote: Hello, I say share internet connection on 3G modem by following procedure properties -- sharing -- select the LAN connection .. then press ok Sharing is done. But , OS (Vista) assigns that LAN connection a IP : 192.168.0.1 net mask as : 255.255.255.0 This is not in range of 192.168.7.2 of BBB. Because of this my connection between BBB PC breaks. So I can not SSH into BBB. Regards, Vinayak On Sunday, 13 October 2013 11:29:32 UTC+5:30, Wulf Man wrote: enable internet connection sharing on your windows machine On 10/12/2013 10:13 PM, vinayak aghor wrote: Hello, I have BBB, laptop with Vista 3G datacard. I wan to connect beagle bone black to laptop then I wan to access internet connetion of laptop to with BBB. Currently following is status --- root@beaglebone:~# ping www.google.com ping: unknown host www.google.com root@beaglebone:~# ifconfig eth0 Link encap:Ethernet HWaddr 90:59:AF:57:42:18 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:56 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:24 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1768 (1.7 KiB) TX bytes:1768 (1.7 KiB) usb0 Link encap:Ethernet HWaddr 8A:56:DB:0A:72:13 inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:479 errors:0 dropped:0 overruns:0 frame:0 TX packets:182 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:48037 (46.9 KiB) TX bytes:33271 (32.4 KiB) --- root@beaglebone:~# ping -i 0.5 192.168.7.1 PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data. 64 bytes from 192.168.7.1: icmp_req=1 ttl=128 time=0.719 ms 64 bytes from 192.168.7.1: icmp_req=2 ttl=128 time=0.670 ms 64 bytes from 192.168.7.1: icmp_req=3 ttl=128 time=0.577 ms 64 bytes from 192.168.7.1: icmp_req=4 ttl=128 time=0.745 ms ^C --- 192.168.7.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 0.577/0.677/0.745/0.071 ms -- root@beaglebone:~# ping -i 0.5 192.168.7.2 PING 192.168.7.2 (192.168.7.2) 56(84) bytes of data. 64 bytes from 192.168.7.2: icmp_req=1 ttl=64 time=0.235 ms 64 bytes from 192.168.7.2: icmp_req=2 ttl=64 time=0.125 ms 64 bytes from 192.168.7.2: icmp_req=3 ttl=64 time=0.157 ms 64 bytes from 192.168.7.2: icmp_req=4 ttl=64 time=0.117 ms ^C --- 192.168.7.2 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 1503ms rtt min/avg/max/mdev = 0.117/0.158/0.235/0.048 ms root@beaglebone:~# I can SSH into BBB can ping to fro with PC. But as shown on TOP, I can not ping to www.google.com Please help me Regards, Vinayak -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails
Re: [beagleboard] Measuring CPU(Cortex-A8) clock cycles
Ohh I almost forgot that you can check the Overflow Flag Status Register (page 159 section 3.2.45). On Tuesday, 11 March 2014 00:10:48 UTC, Paddu wrote: Hi Luis, Thank you so much. Your information is very useful. Regards Paddu On Tuesday, March 11, 2014 1:36:08 AM UTC+9, Luis wrote: Sorry, in my last reply it is *page 168 section 3.2.52*, not 3.5.52 On Monday, 10 March 2014 16:34:10 UTC, Luis wrote: Hi Paddu, I believe it is a 32-bit register (I found no mention of 64-bit registers in the c9 coprocessor). When it is overflown it resets to 0, in my code I take this into account. It looks like you can generate overflow interrupts (page 168 section 3.5.52) but I haven't used them. Hope this helps. Regards, Luis On Monday, 10 March 2014 15:00:26 UTC, Paddu wrote: Hi, Thank you for sharing very useful information. With your suggestions currently I am able to read the Cycle count using using this register. Please let me ask more question about CCNT register. Just for the confirmation, I would like to know is this a 32 bit register? or 64 bit? and what would happen if the count value is overflown, will the register reset to 0 ? Regards Paddu. On Tuesday, February 25, 2014 11:39:24 PM UTC+9, Luis wrote: Hi Paddu, The Cortex-A8 has a Performance Monitor Control Register (coprocessor c9), you can check the documentation for the registers here (page 154, section 3.2.42): http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344k/DDI0344K_cortex_a8_r3p2_trm.pdf For a simple example of the code check this page: http://stackoverflow.com/questions/3247373/how-to-measure-program-execution-time-in-arm-cortex-a8-processor In there they use assembly to configure and read the registers for the Cortex-A8, so it can be ported to any OS I believe. The Peformance Monitoring Unit is very cool, there's a ton of events you can measure there, you can record up to 5 events (including the Clock Cycles CCNT). If you were using Linux it already has the implementation done for you, you only need some libraries (found in http://perfmon2.sourceforge.net/hw.html ). Hope this helps. Best Regards, Luis On Tuesday, 25 February 2014 03:02:31 UTC, Paddu wrote: Thank all for the kind reply. @liyaoshi- I could find the link you have mentioned. @Grissiom - Currently we are not using Linux, we are using Starterware. I shall see if we could implement this using a ASM code. On Tuesday, February 25, 2014 11:56:11 AM UTC+9, liyaoshi wrote: From this link , you can see readtsc() means this only support on x86 ,tsc register is 64bit register and clock with main clock , on x86/64 this is can very precise On ARM, use generic PIT,(maybe you should write your own driver ) , only limit is almost PIT register is 32bit 2014-02-25 10:49 GMT+08:00 Grissiom chaos@gmail.com: On Mon, Feb 24, 2014 at 10:26 PM, Paddu pradeep@gmail.comwrote: Hi, We need some advice in measuring Beaglebone CPU(Cortex-A8) clock cycles. Is there any way to measure the CPU cycles and use it inside the program? I have heard about ccnt register but don't know how exactly could we use that in the program. Please let me know if there is a reference or pointers on how to implement the code. Do you want to measure cycles in Linux program or baremetal program? If you are on Linux, this link: http://halobates.de/modern-pmus-yokohama.pdf may help you. If not, read the PMU section in the ARM ARM. -- Cheers, Grissiom -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Here is the BeagleBone Debian (beta) image you want to test
Hello all! I have been testing the new official Debian eMMC flasher image for the BBB… *http://beagleboard.org/latest-images/* (…in particular this one Debian (BeagleBone Black - 2GB eMMC) 2014-03-04) root@vBBB5studioS:/var/lib/cloud9# uname -a Linux vBBB5studioS 3.8.13-bone41 #1 SMP Tue Mar 4 22:51:47 UTC 2014 armv7l GNU/Linux Regarding available space on the eMMC, I am seeing this after a fresh flash… root@vBBB5studioS:/var/lib/cloud9# df -h Filesystem Size Used Avail Use% Mounted on rootfs 1.7G 1.3G 284M 83% / udev 10M 0 10M 0% /dev tmpfs 100M 788K 99M 1% /run /dev/disk/by-uuid/57e2c7bb-2b31-488e-b9b4-92e3e4c6af20 1.7G 1.3G 284M 83% / tmpfs 249M 0 249M 0% /dev/shm tmpfs 249M 0 249M 0% /sys/fs/cgroup tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 100M 0 100M 0% /run/user /dev/mmcblk0p1 96M 80M 17M 83% /boot/uboot Does this look right? Is it really supposed to be 83% full from the start with only 284MB remaining? I was trying to build some software from source (*OLA framework*) and during the make process I got some errors about running out of disk space. If I was to start looking for space to free up, where would I start? (I have several BBBs and some of them I was hoping to use a GUI on, but most I just use SSH) Thanks! -frenchy -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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: Here is the BeagleBone Debian (beta) image you want to test
On Tue, Mar 11, 2014 at 10:21 AM, Steve French voltvis...@gmail.com wrote: Hello all! I have been testing the new official Debian eMMC flasher image for the BBB... http://beagleboard.org/latest-images/ (...in particular this one Debian (BeagleBone Black - 2GB eMMC) 2014-03-04) root@vBBB5studioS:/var/lib/cloud9# uname -a Linux vBBB5studioS 3.8.13-bone41 #1 SMP Tue Mar 4 22:51:47 UTC 2014 armv7l GNU/Linux Regarding available space on the eMMC, I am seeing this after a fresh flash... root@vBBB5studioS:/var/lib/cloud9# df -h Filesystem Size Used Avail Use% Mounted on rootfs 1.7G 1.3G 284M 83% / udev 10M 0 10M 0% /dev tmpfs 100M 788K 99M 1% /run /dev/disk/by-uuid/57e2c7bb-2b31-488e-b9b4-92e3e4c6af20 1.7G 1.3G 284M 83% / tmpfs 249M 0 249M 0% /dev/shm tmpfs 249M 0 249M 0% /sys/fs/cgroup tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 100M 0 100M 0% /run/user /dev/mmcblk0p1 96M 80M 17M 83% /boot/uboot Does this look right? Is it really supposed to be 83% full from the start with only 284MB remaining? Correct, to meet everyone's out of box pkg requirements, the eMMC is mostly full. If you drop opencv/python/chromium you'll gain a lot of space back. Otherwise, it's just easier to just use the non-flasher image on a 4GB/8GB microSD card. (making sure to use the grow_partition.sh script under /opt/scripts/tools/ to fully resize the drive) 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] Restart SSH service (or even reboot board) from Cloud9 IDE?
Twice in 6 months, my BBB has locked me out of an SSH connection (standard Angstrom distribution, the only additions are lighttpd and PHP, using a static IP). The standard webserver on port 80 and a lighttpd server on port 6980 still work as does the Cloud9 IDE. The only way to get it back is a hard reset. This normally wouldn't be an issue but I'm about to put a couple of these in a not-easily-accessible place. Is there a way to restart SSH or even reboot the board from within the Cloud9 IDE? I could connect a kill circuit to one of the I/O and power cycle the board from Cloud9 but that's a bit messy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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 HDMI/VGA converter problems
My hopes of using a cheap vga monitor drifted away when my HDMI to VGA converter shut down within a few seconds. A peek at the BeagleBoneBlack schematic shows a 100 ma resettable fuse guarding the mini hdmi power pin. It's the yellow thing that looks like a ceramic capacitor. Luckily it's not surface mounted, so is relatively easy to replace with a 200 ma fuse -- digikey#RXEF020-ND. Now 35 cents and ten minutes work later, all is well. I do use a powered USB hub so as not to overload the BB power regulator -- the reason, is suppose, why the designers used the fuse. On Friday, June 14, 2013 1:52:12 PM UTC-4, lee jones wrote: Hello all :) (newbie alert btw!) I've just recently (only in the last few days) bought a beaglebone black and also a mini hdmi to normal sized hdmi cable to go with it. Unfortunatly I'm not managing to get any display with an HDMI to VGA converter however. I can confirm the beaglebone is doing something as I was able to connect it to a TV with HDMI input, and it displayed a picture ok. After looking into all of this I noticed this page regarding HDMI to VGA converters - http://circuitco.com/support/index.php?title=BeagleBone_Black_Accessories#HDMI-VGA_Adapters. My HDMI to VGA looks very similar but not quite the same to that converter, in fact it looks rather like this - http://www.amazon.co.uk/Adapter-Laptop-Power-Free-Raspberry-support/dp/B0088K7QUQ/ref=sr_1_2?ie=UTF8qid=1371231750sr=8-2keywords=HDMI+to+vga One difference I noticed is that the one linked to in the circuitco webpage appears to be powered (presumably by the micro usb port on the converter?). Mine dosen't have that at all; btw originally my converter was bought to be used with the rasberry pi. Since one converter is powered and the other isn't am I right in assuming that the beaglebone dosen't supply the neccecary +5V to power a device connected to the HDMI port at all, hence the failure? This is only speculation but prehaps most of the HDMI to VGA converters originally bought for rasberry pi's and then subsequently used to try to work on the beaglebone black won't work at all? ljones -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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 HDMI/VGA converter problems
It is not a fuse. It is a PTC. That is why on the Wiki we recommend an externally powered converter. The 5V comes from the power supply in the wall, so there is no regulator on the board to overload. We decided to meet the HDMI specification, so that is the reason for the current limit. Gerald On Tue, Mar 11, 2014 at 11:04 AM, vermonttaxpa...@gmail.com fridayfoodaff...@gmail.com wrote: My hopes of using a cheap vga monitor drifted away when my HDMI to VGA converter shut down within a few seconds. A peek at the BeagleBoneBlack schematic shows a 100 ma resettable fuse guarding the mini hdmi power pin. It's the yellow thing that looks like a ceramic capacitor. Luckily it's not surface mounted, so is relatively easy to replace with a 200 ma fuse -- digikey#RXEF020-ND. Now 35 cents and ten minutes work later, all is well. I do use a powered USB hub so as not to overload the BB power regulator -- the reason, is suppose, why the designers used the fuse. On Friday, June 14, 2013 1:52:12 PM UTC-4, lee jones wrote: Hello all :) (newbie alert btw!) I've just recently (only in the last few days) bought a beaglebone black and also a mini hdmi to normal sized hdmi cable to go with it. Unfortunatly I'm not managing to get any display with an HDMI to VGA converter however. I can confirm the beaglebone is doing something as I was able to connect it to a TV with HDMI input, and it displayed a picture ok. After looking into all of this I noticed this page regarding HDMI to VGA converters - http://circuitco.com/support/index.php?title=BeagleBone_ Black_Accessories#HDMI-VGA_Adapters . My HDMI to VGA looks very similar but not quite the same to that converter, in fact it looks rather like this - http://www.amazon.co.uk/Adapter-Laptop-Power-Free-Raspberry-support/dp/ B0088K7QUQ/ref=sr_1_2?ie=UTF8qid=1371231750sr=8-2keywords=HDMI+to+vga One difference I noticed is that the one linked to in the circuitco webpage appears to be powered (presumably by the micro usb port on the converter?). Mine dosen't have that at all; btw originally my converter was bought to be used with the rasberry pi. Since one converter is powered and the other isn't am I right in assuming that the beaglebone dosen't supply the neccecary +5V to power a device connected to the HDMI port at all, hence the failure? This is only speculation but prehaps most of the HDMI to VGA converters originally bought for rasberry pi's and then subsequently used to try to work on the beaglebone black won't work at all? ljones -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Re: Problems installing WSPR and RTL-SDR on Beaglebone Debian
Oh Dear, problem solved. make was not part of the Debian distribution. I had to install it by hand.I think nobody seems to compile programs anymore. Hajo -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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: Problems installing WSPR and RTL-SDR on Beaglebone Debian
On Tue, Mar 11, 2014 at 11:40 AM, Hajo Dezelski dl1...@gmail.com wrote: Oh Dear, problem solved. make was not part of the Debian distribution. I had to install it by hand.I think nobody seems to compile programs anymore. The official debian image have gcc/make installed by default. http://beagleboard.org/latest-images With my other traditional images on http://elinux.org/BeagleBoardDebian the only goal was enough packages to get online to use apt-get... Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: BBB + PREEMPT_RT
I tried PREEMPT yesterday on 3.12.9 and the ethernet seemed to work. The only thing I had a problem with was USB host. It failed the probe(). So I reverted. Years ago I filed a bug report with TI regarding the ethernet driver not working with PREEMPT in kernel 3.2. Some progress has been made, ethernet seemed to work now on 3.12.9. Dick -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: BBB PRU input test
I think I see the problem. You have the pin muxed for pru gpio in the
device tree overlay, but you're trying to read the arm gpio block. PRU gpio
is accessed directly with register r30 for output and r31 for input
(section 5.2.2.3 in the somewhat terrible pru reference
guidehttps://github.com/beagleboard/am335x_pru_package/blob/master/am335xPruReferenceGuide.pdf
).
On Tuesday, March 11, 2014 7:49:47 AM UTC-7, Manu wrote:
I read your last email with attention by still I can't understad why my
code is not working. I a few words:
The code works when properly when I comment the line WBS r31.t15 //Wait
til GPIO-15-in is high... P9_24
*PINMUX DTS:*
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = BB-BONE-W;
version = 00A0;
exclusive-use = P9.24;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
mygpio: pinmux_mygpio{
pinctrl-single,pins =
0x184 0x36 /* P9 24 pr1_pru0_pru_r31_16.GPIO0_15: | PULLUP |
MODE6 | INPUT */
;
};
};
};
fragment@1 {
target = ocp;
__overlay__ {
test_helper: helper {
compatible = bone-pinmux-helper;
pinctrl-names = default;
pinctrl-0 = mygpio;
status = okay;
};
};
};
fragment@2{
target = pruss;
__overlay__ {
status = okay;
};
};
};
*PIN MUX STATUS:*
# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins | grep pin 97
pin 97 (44e10984) 0036 pinctrl-single
*UNAME +DIST:*
# uname -a
Linux don-t001 3.8.13-bone30 #1 SMP Thu Nov 14 11:19:20 UTC 2013 armv7l
armv7l armv7l GNU/Linux
# cat /etc/issue
Ubuntu 12.04.3 LTS \n \l
*ASM CODE:*
.origin 0
.entrypoint START
#define PRU0_ARM_INTERRUPT 19
#define AM33XX
#define GPIO1 0x4804c000
#define GPIO_CLEARDATAOUT 0x190
#define GPIO_SETDATAOUT 0x194
START:
//Enable OCP master port
LBCO r0, C4, 4, 4
CLR r0, r0, 4 // Clear SYSCFG[STANDBY_INIT] to enable OCP master port
SBCO r0, C4, 4, 4
MOV r1, 1000 //# cycles
INPUTTEST:
WBS r31.t15 //Wait til GPIO-15-in is high... P9_24
SUB r1, r1, 1 //Subtract from counter
QBNE INPUTTEST, r1, 0 //Loop if counter not at zero
// Send notification to Host for program completion
MOV R31.b0, PRU0_ARM_INTERRUPT+16
MOV r1, 0
HALT
*INIT PROGRAM USING PyPRUSS:*
#!/usr/bin/python
''' ddr_write.py - Finds the DDR address and size, passes that info to the
PRU0
data memory, executes a program and reads back data from the first and
last banks'''
import pypruss
import mmap
import struct
pypruss.modprobe()
ddr_addr = pypruss.ddr_addr()
ddr_size = pypruss.ddr_size()
print DDR memory address is 0x%x and the size is 0x%x%(ddr_addr,
ddr_size)
ddr_offset = ddr_addr-0x1000
ddr_filelen = ddr_size+0x1000
ddr_start = 0x1000
ddr_end = 0x1000+ddr_size
pypruss.init() # Init the PRU
pypruss.open(0) # Open PRU event 0 which is PRU0_ARM_INTERRUPT
pypruss.pruintc_init() # Init the interrupt controller
pypruss.pru_write_memory(0, 0, [ddr_addr, ddr_addr+ddr_size-4]) # Put the
ddr address in the first region
pypruss.exec_program(0, ./ddr_write.bin) # Load firmware
ddr_write.bin on PRU 0
pypruss.wait_for_event(0) # Wait for event 0 which is connected to
PRU0_ARM_INTERRUPT
pypruss.clear_event(0) # Clear the event
pypruss.exit() # Exit PRU
with open(/dev/mem, r+b) as f: # Open the physical memory device
ddr_mem = mmap.mmap(f.fileno(), ddr_filelen, offset=ddr_offset) # mmap the
right area
read_back = struct.unpack(L, ddr_mem[ddr_start:ddr_start+4])[0] # Parse
the data
print The first 4 bytes of DDR memory reads +hex(read_back)
ddr_mem.close() # Close the memory
f.close() # Close the file
No way to read the P9_24 PIN From BBB using PRUSS
May be the *WBS *does no work as I think . a week working on that and
still nothing.
El martes, 11 de marzo de 2014 00:40:04 UTC-3, Brandon I escribió:
When I do an interruput up or down the ASM keeps waiting and nothing
Read my previous email. Your code will not work as is.
On Mon, Mar 10, 2014 at 8:11 PM, Manu manuelbe...@gmail.com wrote:
My DTS is:
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = BB-BONE-W;
version = 00A0;
exclusive-use = P9.24;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
mygpio: pinmux_mygpio{
pinctrl-single,pins =
0x184 0x16 /* P9 24 pr1_pru0_pru_r31_16.GPIO0_15: | PULLUP |
MODE6 | INPUT */
;
};
};
};
fragment@1 {
target = ocp;
__overlay__ {
test_helper: helper {
compatible = bone-pinmux-helper;
pinctrl-names =
Re: [beagleboard] Re: Problems installing WSPR and RTL-SDR on Beaglebone Debian
Hello Robert, I was using the official image BBB-eMMc-flasher-debian-7.4-2014-02-16-2gb.img. While installing make with apt-get it was installed new. I couldn't recall the message... too many lines gone by. Program still doesn't work but that's another problem ;-) Anyway thanks for the answer. Hajo On Tuesday, March 11, 2014 5:44:31 PM UTC+1, RobertCNelson wrote: On Tue, Mar 11, 2014 at 11:40 AM, Hajo Dezelski dl1...@gmail.comjavascript: wrote: Oh Dear, problem solved. make was not part of the Debian distribution. I had to install it by hand.I think nobody seems to compile programs anymore. The official debian image have gcc/make installed by default. http://beagleboard.org/latest-images With my other traditional images on http://elinux.org/BeagleBoardDebian the only goal was enough packages to get online to use apt-get... 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: FBIO_WAITFORVSYNC on BBB
On Tue, Mar 11, 2014 at 12:13 PM, Robert Kuhn rob...@ku.hn wrote: Hi, So now I try to enable omapfb und omapdss. I use the kernel source from linux-dev-3.13.6-bone7 and the instructions from http://processors.wiki.ti.com/index.php/Linux_Core_DSS_User%27s_Guide#omapdrm I think I enabled omapdss (see my config), but there is no /sys/devices/platform/omapdss Where is my error? Well the Sitara am335x use on the bone's doesn't have the omapfb display ip block. On mainline it uses the tilcd driver, based loosely of the same ip as the davanci da8x-fb driver. 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: FBIO_WAITFORVSYNC on BBB
RobertCNelson: Well the Sitara am335x use on the bone's doesn't have the omapfb display ip block. On mainline it uses the tilcd driver, based loosely of the same ip as the davanci da8x-fb driver. Oh, I see. Any chance to get the vsync signal with that in userspace or i a kernel module? Thanks - Robert -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Production tooling (MSPGCC)
I am experimenting with using a beaglebone for some production tooling. I would like to use desktop for a nice fancy GUI to show screening results and I also need to have the beaglebone program an MSP430 processor using a TI FET tool. Well that's what I want, getting it is another thing. I have a beaglebone and a 7 ldc from circuitco (got it awhile ago) and I'm trying to get a desktop installed. I could go with the Angstrom distribution that comes stock but I've tried installing a ubuntu image then LXDE but LXDE hangs on the login screen. I then tried installing ubuntu desktop and got the same results so the stock Angstrom is looking much better now. I can work with the angstrom distribution but I need a little help in getting the MSPGCC tool chain running on it. I'm strating from near zero, it's been a long time since I've done any linux stuff. Can someone give me a roadmap on what I have to do? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Production tooling (MSPGCC)
On Tue, Mar 11, 2014 at 11:40 AM, and...@gmail.com wrote: I am experimenting with using a beaglebone for some production tooling. I would like to use desktop for a nice fancy GUI to show screening results and I also need to have the beaglebone program an MSP430 processor using a TI FET tool. Well that's what I want, getting it is another thing. I have a beaglebone and a 7 ldc from circuitco (got it awhile ago) and I'm trying to get a desktop installed. I could go with the Angstrom distribution that comes stock but I've tried installing a ubuntu image then LXDE but LXDE hangs on the login screen. I then tried installing ubuntu desktop and got the same results so the stock Angstrom is looking much better now. I can work with the angstrom distribution but I need a little help in getting the MSPGCC tool chain running on it. I'm strating from near zero, it's been a long time since I've done any linux stuff. Can someone give me a roadmap on what I have to do? The official debian image posted here: http://beagleboard.org/latest-images should not lock up at the login screen with your lcd. Then just sudo apt-get install gcc-msp430 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: BBB PRU input test
This is what I don't know how to do, access to the r31
(pr1_pru0_pru_r31_16) | PIN =97 | GPIO0_15
could you help me?
Thank you.
On 03/11/2014 02:17 PM, Brandon I wrote:
I think I see the problem. You have the pin muxed for pru gpio in the
device tree overlay, but you're trying to read the arm gpio block. PRU
gpio is accessed directly with register r30 for output and r31 for
input (section 5.2.2.3 in the somewhat terrible pru reference guide
https://github.com/beagleboard/am335x_pru_package/blob/master/am335xPruReferenceGuide.pdf).
On Tuesday, March 11, 2014 7:49:47 AM UTC-7, Manu wrote:
I read your last email with attention by still I can't understad
why my code is not working. I a few words:
The code works when properly when I comment the line WBS r31.t15
//Wait til GPIO-15-in is high... P9_24
*PINMUX DTS:*
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = BB-BONE-W;
version = 00A0;
exclusive-use = P9.24;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
mygpio: pinmux_mygpio{
pinctrl-single,pins =
0x184 0x36 /* P9 24 pr1_pru0_pru_r31_16.GPIO0_15: | PULLUP |
MODE6 | INPUT */
;
};
};
};
fragment@1 {
target = ocp;
__overlay__ {
test_helper: helper {
compatible = bone-pinmux-helper;
pinctrl-names = default;
pinctrl-0 = mygpio;
status = okay;
};
};
};
fragment@2{
target = pruss;
__overlay__ {
status = okay;
};
};
};
*PIN MUX STATUS:*
# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins | grep pin 97
pin 97 (44e10984) 0036 pinctrl-single
*UNAME +DIST:*
# uname -a
Linux don-t001 3.8.13-bone30 #1 SMP Thu Nov 14 11:19:20 UTC 2013
armv7l armv7l armv7l GNU/Linux
# cat /etc/issue
Ubuntu 12.04.3 LTS \n \l
*ASM CODE:*
*
*
.origin 0
.entrypoint START
#define PRU0_ARM_INTERRUPT 19
#define AM33XX
#define GPIO1 0x4804c000
#define GPIO_CLEARDATAOUT 0x190
#define GPIO_SETDATAOUT 0x194
START:
** //Enable OCP master port
LBCO r0, C4, 4, 4
CLR r0, r0, 4// Clear SYSCFG[STANDBY_INIT] to enable OCP
master port
SBCO r0, C4, 4, 4
MOV r1, 1000 //# cycles
INPUTTEST:
WBS r31.t15 //Wait til GPIO-15-in is high... P9_24
SUB r1, r1, 1 //Subtract from counter
QBNE INPUTTEST, r1, 0 //Loop if counter not at zero
// Send notification to Host for program completion
MOV R31.b0, PRU0_ARM_INTERRUPT+16
MOV r1, 0
HALT
*INIT PROGRAM USING PyPRUSS:*
#!/usr/bin/python
''' ddr_write.py - Finds the DDR address and size, passes that
info to the PRU0
data memory, executes a program and reads back data from the first
and last banks'''
import pypruss
import mmap
import struct
pypruss.modprobe()
ddr_addr = pypruss.ddr_addr()
ddr_size = pypruss.ddr_size()
print DDR memory address is 0x%x and the size is 0x%x%(ddr_addr,
ddr_size)
ddr_offset = ddr_addr-0x1000
ddr_filelen = ddr_size+0x1000
ddr_start = 0x1000
ddr_end = 0x1000+ddr_size
pypruss.init()# Init the PRU
pypruss.open(0)# Open PRU event 0 which is PRU0_ARM_INTERRUPT
pypruss.pruintc_init()# Init the interrupt controller
pypruss.pru_write_memory(0, 0, [ddr_addr, ddr_addr+ddr_size-4])#
Put the ddr address in the first region
pypruss.exec_program(0, ./ddr_write.bin)# Load firmware
ddr_write.bin on PRU 0
pypruss.wait_for_event(0)# Wait for event 0 which is connected to
PRU0_ARM_INTERRUPT
pypruss.clear_event(0)# Clear the event
pypruss.exit()# Exit PRU
with open(/dev/mem, r+b) as f:# Open the physical memory device
ddr_mem = mmap.mmap(f.fileno(), ddr_filelen, offset=ddr_offset) #
mmap the right area
read_back = struct.unpack(L, ddr_mem[ddr_start:ddr_start+4])[0]#
Parse the data
print The first 4 bytes of DDR memory reads +hex(read_back)
ddr_mem.close()# Close the memory
f.close()# Close the file
No way to read the P9_24 PIN From BBB using PRUSS
May be the *WBS *does no work as I think . a week working on
that and still nothing.
El martes, 11 de marzo de 2014 00:40:04 UTC-3, Brandon I escribió:
When I do an interruput up or down the ASM keeps waiting and
nothing
Read my previous email. Your code will not work as is.
On Mon, Mar 10, 2014 at 8:11 PM, Manu manuelbe...@gmail.com
wrote:
My DTS is:
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = BB-BONE-W;
[beagleboard] New to Beaglebaord and single board computers
Hi Everyone, I am very new to this single board computers and Beaglebaord .But i am very much interested doing project in electronics .Though i am having bachelors degree in electronics and communication engineering , i don't have much hardware experience. currently i am working as software engineers. This field seems to be very interesting and innovative. Since i am a newbie i need your guidance and support to start with. I don't know what to buy, means what are all the others parts needed to setup a project . I am very much interested in robotics ,image processing , sensing and media etc. Please all of you give suggestions ,ideas and list of products to buy to start with beagleboard.. note : i am planning to buy beaglebone black. Thanks Regards, iJegan -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] New to Beaglebaord and single board computers
The BBB is linux based and is a bit sensitive to current draw and applied voltage. You might want to start with a more forgiving platform like an arduino uno. that said there are lots of resources on line and places to get kits of parts and parts Videos and Web Sites Sparkfun.com adafruit.com learing.adafruit.com derekmolloy.ie digikey.com mouser.com I could keep going youtube channels = sparkfun derek molloy adafruit general search arduino, beaglevome black You will need a good solidering iron power supply(s) multimeters and probes prototype boards jumpers components like led, servos, motor controllers and whatever on and on this is a hobby that you can spend much $$ but don't have to to get started. So go to adafruit or sparkfun and pick a project, buy parts for the project and get building and prrogramming. Don't try to buy everything you need/want at first. Get experience with simple and build from there Eric PS I'm, building a robot with BBB one subsysem at a time. I am playing with arduino for concepts I don't fully undersandd first and then coding and redesigning for the BBB. I have little time with my job so I plan on spending a year or two building the robot. good luck On Tue, Mar 11, 2014 at 2:29 PM, jeganath.perial...@gmail.com wrote: Hi Everyone, I am very new to this single board computers and Beaglebaord .But i am very much interested doing project in electronics .Though i am having bachelors degree in electronics and communication engineering , i don't have much hardware experience. currently i am working as software engineers. This field seems to be very interesting and innovative. Since i am a newbie i need your guidance and support to start with. I don't know what to buy, means what are all the others parts needed to setup a project . I am very much interested in robotics ,image processing , sensing and media etc. Please all of you give suggestions ,ideas and list of products to buy to start with beagleboard.. note : i am planning to buy beaglebone black. Thanks Regards, iJegan -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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. -- Eric Palmer -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes
Hi Micka, Would you be able to send me the driver you compiled with these changes? RobertCNelson's latest builds (-40) have ti_am335x_tsc.ko from last year. I tried the steps you provided last night, I got as far as compiling the kernel but the driver I made had invalid ELF data so I did not try loading it. Alternatively, the patch you have, which version of the ti_am335x_tsc.c driver is it meant to patch? there's been a lot of activity on ti_am335x_tsc.c. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes
Hi Micka, Any chance you can post the ti_am335x_tsc.ko that you compiled for debian? RobertCNelson's recent releases contain an old ti_am335x_tsc.ko (from last year). On Tuesday, 28 January 2014 01:05:15 UTC-8, Mickae1 wrote: Well, It's good that it works in other device :) Micka, On Mon, Jan 27, 2014 at 9:32 PM, Terry Storm terrys...@gmail.comjavascript: wrote: Brilliant Thank you Robert, and thank you Micka for the patch. Just ran it up, booted from SD card and I cant fault the touch in the few minutes I have played with it. Great news, thank you both. Will continue to test. Terry On Tuesday, 28 January 2014 02:45:40 UTC+13, RobertCNelson wrote: On Mon, Jan 27, 2014 at 4:36 AM, Terry Storm terrys...@gmail.com wrote: Great news Can someone please link me to the l ... -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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: Here is the BeagleBone Debian (beta) image you want to test
Hello, this was one of the problems with BBB. I managed to install Debian with BBB-eMMc-flasher-debian-7.4-2014-02-16-2gb.img installed only Xfce (needed an graphical output) and had about 450 MB left. Beside that I had to install a swap file 128 MB I'm down to 211156. That's not a lot. Under Angstrom I managed to use the sd card with the uEnv.txt as additional storage, but I forgot to withdraw the card when finished and waited while booting up until I noticed that the BBB got stuck. My question to Robert: Is there a clean way under Debian to format or mount the sd card as additional storage or even better: Is it possible to mount e.g. homedirectories to that card, so that we are not stuck to that damned 2 GB. I know, I could use the card to boot from, but ... Regards Hajo DL1SDZ On Tuesday, March 11, 2014 4:26:11 PM UTC+1, RobertCNelson wrote: On Tue, Mar 11, 2014 at 10:21 AM, Steve French voltv...@gmail.comjavascript: wrote: Hello all! I have been testing the new official Debian eMMC flasher image for the BBB... http://beagleboard.org/latest-images/ (...in particular this one Debian (BeagleBone Black - 2GB eMMC) 2014-03-04) root@vBBB5studioS:/var/lib/cloud9# uname -a Linux vBBB5studioS 3.8.13-bone41 #1 SMP Tue Mar 4 22:51:47 UTC 2014 armv7l GNU/Linux Regarding available space on the eMMC, I am seeing this after a fresh flash... root@vBBB5studioS:/var/lib/cloud9# df -h Filesystem Size Used Avail Use% Mounted on rootfs 1.7G 1.3G 284M 83% / udev 10M 0 10M 0% /dev tmpfs 100M 788K 99M 1% /run /dev/disk/by-uuid/57e2c7bb-2b31-488e-b9b4-92e3e4c6af20 1.7G 1.3G 284M 83% / tmpfs 249M 0 249M 0% /dev/shm tmpfs 249M 0 249M 0% /sys/fs/cgroup tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 100M 0 100M 0% /run/user /dev/mmcblk0p1 96M 80M 17M 83% /boot/uboot Does this look right? Is it really supposed to be 83% full from the start with only 284MB remaining? Correct, to meet everyone's out of box pkg requirements, the eMMC is mostly full. If you drop opencv/python/chromium you'll gain a lot of space back. Otherwise, it's just easier to just use the non-flasher image on a 4GB/8GB microSD card. (making sure to use the grow_partition.sh script under /opt/scripts/tools/ to fully resize the drive) 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] Support for the Embest 14pin jtag XDS100v2 USB Emulator in Beaglebone black
From: Elavarasu elavarasu@gmail.com Reply-To: beagleboard@googlegroups.com Date: Tuesday, March 11, 2014 at 2:59 AM To: beagleboard@googlegroups.com Subject: [beagleboard] Support for the Embest 14pin jtag XDS100v2 USB Emulator in Beaglebone black Hi, Is there is anyway to use the Embest XDS 100v2 14 pin jtag for the beaglebone black, i referred the difference for the 20pin and 14pin here: http://processors.wiki.ti.com/index.php/JTAG_Connectors But any turnarounds to use this jtag in BBB which have the 20 pin connector. My Blackhawk USB100V2 came with a 14 pin to 20 pin CTI adapter. You can buy this separately, but it is expensive ($69), or you can make your own adapter. Regards, John Thanks, Elavarasu. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Beaglebone Black Ethernet Phy Not Detected on Boot.
Gerald said: The issue is that the processors interferes with the default address settings when the PHY reads the pins. If the SW looks for the other addresses, it works fine. Could we get a clue about which addresses are the problem? Maybe the addresses 4a10 vs. 4a101000? davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00 --- cpsw 4a10.ethernet: Or maybe the mask that seems to select the particular phy? davinci_mdio 4a101000.mdio: detected phy mask fffb --- davinci_mdio 4a101000.mdio: detected phy mask fffe Or the phy id which I haven't a clue about? net eth0: phy found : id is : 0x7c0f1 Or maybe the default MAC addresses, two in the onboard hardware memory and more in the boot environment? I still see lots of phy not found dmessages, even though all of my interfaces work properly when connected. Would be nice to understand this better... -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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.
The base address of the PHY. Only one address per PHY. I believe it is 0 to 7. It is my understanding that the fix was pushed up a week ago. Robert's image should handle this. It is not the MAC address. PHY NOT FOUND means that at the one address of 00 the PHY did not respond because the PHY has a different address. Gerald On Tue, Mar 11, 2014 at 2:48 PM, Loren Amelang lorenamel...@gmail.comwrote: Gerald said: The issue is that the processors interferes with the default address settings when the PHY reads the pins. If the SW looks for the other addresses, it works fine. Could we get a clue about which addresses are the problem? Maybe the addresses 4a10 vs. 4a101000? davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00 --- cpsw 4a10.ethernet: Or maybe the mask that seems to select the particular phy? davinci_mdio 4a101000.mdio: detected phy mask fffb --- davinci_mdio 4a101000.mdio: detected phy mask fffe Or the phy id which I haven't a clue about? net eth0: phy found : id is : 0x7c0f1 Or maybe the default MAC addresses, two in the onboard hardware memory and more in the boot environment? I still see lots of phy not found dmessages, even though all of my interfaces work properly when connected. Would be nice to understand this better... -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] dtb file causes boot failure
I am having trouble getting my Beagleboard-xm to boot when the omap3-beagle-xm.dtb is loaded by u-boot Best I can tell, u-boot loads the kernel and the dtb file successfully but boot locks up with Waiting for root device /dev/mmcblk0p2... There are a number of things in the boot log that look unhealthy however directly relating to the SD card I found the following: [1.565521] omap_hsmmc mmc.20: unable to select pin group [1.571563] omap_hsmmc mmc.20: Failed to get debounce clk [1.577270] /ocp/mmc@4809c000: can't find DMA channel [1.582611] omap_hsmmc mmc.20: unable to obtain RX DMA engine channel 62 If I modify my uEnv.txt to skip loading the dtb file everything appears to load up properly. What can I do to troubleshoot the dtb? I need SGX drivers so I am stuck with the following versions: I am using the 3.7.x kernel from https://github.com/RobertCNelson/stable-kernel Ubuntu 11.10 (no longer available to download from RCN's file server) u-boot 2014.1 from http://eewiki.net/display/linuxonarm/BeagleBoard#BeagleBoard-Bootloader:U-Boot About the bootloader: Ubuntu 11.10 comes with 2013.7 but there is something wrong with the uEnv.txt and the dtb cannot be loaded and falls back on loading the kernel without it. I need to rebuild u-boot to remove the 2 second boot delay and kernel validation(boot speed is requirement of the project). The patches from RCN for version 2013.7 fail to apply properly so I am using version 2014.1 which appears to be functioning properly. full boot log: http://pastebin.com/NbsM8gq0 uEnv.txt(dtb load disabled): http://pastebin.com/NWuYSYd8 I've been banging my head against the wall for about a week now on this. Any ideas as to what I could try would be awesome! 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] Beaglebone Black Ethernet Phy Not Detected on Boot.
Got it! (Chrome print to PDF, copy from the print...) - 3.7.1 PHYAD[2:0]: PHY Address Configuration The PHYAD[2:0] configuration straps are driven high or low to give each PHY a unique address. This address is latched into an internal register at the end of a hardware reset (default = 000b). In a multitransceiver application (such as a repeater), the controller is able to manage each transceiver via the unique address. Each transceiver checks each management data frame for a matching address in the relevant bits. When a match is recognized, the transceiver responds to that particular frame. The PHY address is also used to seed the scrambler. In a multi-transceiver application, this ensures that the scramblers are out of synchronization and disperses the electromagnetic radiation across the frequency spectrum. The device’s SMI address may be configured using hardware configuration to any value between 0 and 7. The user can configure the PHY address using Software Configuration if an address greater than 7 is required. The PHY address can be written (after SMI communication at some address is established) using the PHYAD bits of the Special Modes Register. The PHYAD[2:0] configuration straps are multiplexed with other signals as shown in Table 3.5. - From my A5C Schematic, showing processor names = LAN8710A names = Microchip names: GMII1_RXERR/RMII1_RXERR/SPI1_D1/I2C1_SCL/MCASP1_FSX/UART5_RTSN/UART2_TXD/GPIO3_2 = RXER/PHYAD0 = RXER/RXD4/PHYAD0 GMII1_RXCLK/UART2_TXD/RGMII1_RCLK/MMC0_DAT6/MMC1_DAT1/UART1_DSRN/MCASP0_FSX/GPIO3_10 = REFCLKO = RXCLK/PHYAD1 GMII1_RXCLK/UART2_TXD/RGMII1_RCLK/MMC0_DAT6/MMC1_DAT1/UART1_DSRN/MCASP0_FSX/GPIO3_10 = RXD3/PHYAD2 = RXD3/PHYAD2 Obviously a lot of multiplexed uses there! Microchip says, This address is latched into an internal register at the end of a hardware reset (default = 000b). But their reset is SYS_RESETn, right? The same reset caused by the user reset button? How is the processor supposed to control those three signals while it is reset? So how do three bits default to 000b? I guess they are counting the address bits you can only program in software? But if those default to 000b, how does my chip end up as phy[0]? Maybe that's where the mask comes in? Mine works with mask fffe: [2.482812] davinci_mdio 4a101000.mdio: detected phy mask fffe [2.490309] libphy: 4a101000.mdio: probed [2.494577] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [2.504409] Detected MACID = 90:59:af:4d:71:eb ... [5.854282] libphy: PHY 4a101000.mdio:01 not found [5.859335] net eth0: phy 4a101000.mdio:01 not found on slave 1 While I see reports above in this thread that On Tuesday, November 26, 2013 2:22:42 PM UTC-8, AndrewTaneGlen wrote: On a good phy boot I see the following: [2.810749] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [2.817206] davinci_mdio 4a101000.mdio: detected phy mask fffe ... On a 'bad phy' boot I see the following (differences highlighted): [2.806763] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [2.813213] davinci_mdio 4a101000.mdio: detected phy mask fffb I'm betting the fe mask eliminates the default 000b bits that are not set by hardware, allowing the good boot. Of the hardware set bits, it seems my chip must get address zero, so all three signals must be zero when reset ends. With mask fe, only the hardware lines are checked. But... Where does the mask come from? I'm not finding it in the boot environment settings. It looks like it is read from the chip: [2.817206] davinci_mdio 4a101000.mdio: detected phy mask fffe But it is not mentioned that I see in the Microchip doc. Always another mystery... On Tuesday, March 11, 2014 12:56:43 PM UTC-7, Gerald wrote: Look in the LAN 8710A data sheet from SMSC. I would cut an paste it, but Microchip has cut and paste blocked. http://www.microchip.com/wwwproducts/Devices.aspx?product=LAN8710ASection 3.7.1 Gerald -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] dtb file causes boot failure
Makes sense, thanks very much for commenting on this. I will keep my uEnv.txt the way it is and ignore the dtb files. On Tuesday, March 11, 2014 4:14:46 PM UTC-6, RobertCNelson wrote: On Tue, Mar 11, 2014 at 4:33 PM, Brett brett@fltsimeng.comjavascript: wrote: I am having trouble getting my Beagleboard-xm to boot when the omap3-beagle-xm.dtb is loaded by u-boot Best I can tell, u-boot loads the kernel and the dtb file successfully but boot locks up with Waiting for root device /dev/mmcblk0p2... There are a number of things in the boot log that look unhealthy however directly relating to the SD card I found the following: [1.565521] omap_hsmmc mmc.20: unable to select pin group [1.571563] omap_hsmmc mmc.20: Failed to get debounce clk [1.577270] /ocp/mmc@4809c000: can't find DMA channel [1.582611] omap_hsmmc mmc.20: unable to obtain RX DMA engine channel 62 If I modify my uEnv.txt to skip loading the dtb file everything appears to load up properly. What can I do to troubleshoot the dtb? Well there's nothing to troubleshoot in v3.7.x for dtb booting, device tree support sucked on omap3 back then and almost nothing worked. It wasn't till v3.11.x that device tree booting on the omap3 (beagle-xm) became end user usable. So with v3.7.x use the old board file, like you did in the modified uEnv.txt. I need SGX drivers so I am stuck with the following versions: I am using the 3.7.x kernel from https://github.com/RobertCNelson/stable-kernel Ubuntu 11.10 (no longer available to download from RCN's file server) u-boot 2014.1 from http://eewiki.net/display/linuxonarm/BeagleBoard#BeagleBoard-Bootloader:U-Boot About the bootloader: Ubuntu 11.10 comes with 2013.7 but there is something wrong with the uEnv.txt and the dtb cannot be loaded and falls back on loading the kernel without it. I need to rebuild u-boot to remove the 2 second boot delay and kernel validation(boot speed is requirement of the project). The patches from RCN for version 2013.7 fail to apply properly so I am using version 2014.1 which appears to be functioning properly. All the u-boot patches can be found in the history of: https://github.com/RobertCNelson/Bootloader-Builder https://github.com/RobertCNelson/Bootloader-Builder; https://github.com/eewiki/u-boot-patches full boot log: http://pastebin.com/NbsM8gq0 uEnv.txt(dtb load disabled): http://pastebin.com/NWuYSYd8 I've been banging my head against the wall for about a week now on this. Any ideas as to what I could try would be awesome! 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] BBXM and SGX libs
I was able to get Ubuntu 13.10 to boot with this kernel. By changing my uEnv.txt to http://pastebin.com/NWuYSYd8 there appear to be no issues. I've not tried to install the SGX libraries but I suspect they will work, that will be my next task if I decide to abandon the 11.10 version. The dtb file was causing the boot issue. See RCN's comment in https://groups.google.com/forum/#!category-topic/beagleboard/beagleboard-xm/V2WeJrX4zXY On Wednesday, March 5, 2014 4:15:49 PM UTC-7, Brett wrote: I had some success with the 3.7.x kernel and the SGX libraries! However I could not get the kernel to boot fully with Ubuntu 13.10 (ubuntu-13.10-console-armhf-2014-02-16.tar.xz). I ended up using an old Ubuntu 11.10 I found on our file server (ubuntu-11.10-r14-minimal-armel-2012-09-27.tar.xz). I might be able to continue using 11.10 but if at all possible we would like update. Can you suggest a version that is more likely to work? Thanks for your help. On Wednesday, March 5, 2014 12:06:29 PM UTC-7, RobertCNelson wrote: On Wed, Mar 5, 2014 at 1:00 PM, Brett brett@fltsimeng.com wrote: Hello, I am trying to get a BBXM running with the SGX libraries. The requirements of my project are to run an EGL2 application without an X11 server. I've followed the steps on http://elinux.org/BeagleBoardUbuntu without success. Using Ubuntu 13.10 built kernel version 3.13.5-armv7-x11 but I get no video on my Samsung SyncMaster 931c. Only the orange screen from u-boot then no signal. I've tried installing the Graphics SDK release 5.01.00.01 from TI's website. Installation appears to go smoothly but the pvr service fails to load. Do we know what version of Linux the SGX libraries will work with? Does anyone have an idea of what direction I need to go in to achieve this? Use the old directions, with the old kernel. http://elinux.org/index.php?title=BeagleBoardUbuntuoldid=314498#SGX_Video_Acceleration I ripped out of a wiki for a reason.. Good Luck! 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] Beaglebone Black Ethernet Phy Not Detected on Boot.
I know what I have seen. I know what I have replicated. And I know the SW fix takes care of it. I also know it does not happen on every board and doe snot happen every time. Do keep in mind that the board reset is not a HW reset. It is a SW reset. The fix is in the latest image from Robert. http://beagleboard.org/latest- images/ Gerald On Tue, Mar 11, 2014 at 6:16 PM, Andrew Glen andrewtaneg...@gmail.comwrote: If anyone has any further information on the software fix/patch for this issue I would be very interested in hearing about it (and backporting into the kernel from late last year I am using) - or even the best way to search for patches to particular files. Regards, Andrew. On 12 March 2014 11:41, Loren Amelang lorenamel...@gmail.com wrote: Got it! (Chrome print to PDF, copy from the print...) - 3.7.1 PHYAD[2:0]: PHY Address Configuration The PHYAD[2:0] configuration straps are driven high or low to give each PHY a unique address. This address is latched into an internal register at the end of a hardware reset (default = 000b). In a multitransceiver application (such as a repeater), the controller is able to manage each transceiver via the unique address. Each transceiver checks each management data frame for a matching address in the relevant bits. When a match is recognized, the transceiver responds to that particular frame. The PHY address is also used to seed the scrambler. In a multi-transceiver application, this ensures that the scramblers are out of synchronization and disperses the electromagnetic radiation across the frequency spectrum. The device's SMI address may be configured using hardware configuration to any value between 0 and 7. The user can configure the PHY address using Software Configuration if an address greater than 7 is required. The PHY address can be written (after SMI communication at some address is established) using the PHYAD bits of the Special Modes Register. The PHYAD[2:0] configuration straps are multiplexed with other signals as shown in Table 3.5. - From my A5C Schematic, showing processor names = LAN8710A names = Microchip names: GMII1_RXERR/RMII1_RXERR/SPI1_D1/I2C1_SCL/MCASP1_FSX/UART5_RTSN/UART2_TXD/GPIO3_2 = RXER/PHYAD0 = RXER/RXD4/PHYAD0 GMII1_RXCLK/UART2_TXD/RGMII1_RCLK/MMC0_DAT6/MMC1_DAT1/UART1_DSRN/MCASP0_FSX/GPIO3_10 = REFCLKO = RXCLK/PHYAD1 GMII1_RXCLK/UART2_TXD/RGMII1_RCLK/MMC0_DAT6/MMC1_DAT1/UART1_DSRN/MCASP0_FSX/GPIO3_10 = RXD3/PHYAD2 = RXD3/PHYAD2 Obviously a lot of multiplexed uses there! Microchip says, This address is latched into an internal register at the end of a hardware reset (default = 000b). But their reset is SYS_RESETn, right? The same reset caused by the user reset button? How is the processor supposed to control those three signals while it is reset? So how do three bits default to 000b? I guess they are counting the address bits you can only program in software? But if those default to 000b, how does my chip end up as phy[0]? Maybe that's where the mask comes in? Mine works with mask fffe: [2.482812] davinci_mdio 4a101000.mdio: detected phy mask fffe [2.490309] libphy: 4a101000.mdio: probed [2.494577] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [2.504409] Detected MACID = 90:59:af:4d:71:eb ... [5.854282] libphy: PHY 4a101000.mdio:01 not found [5.859335] net eth0: phy 4a101000.mdio:01 not found on slave 1 While I see reports above in this thread that On Tuesday, November 26, 2013 2:22:42 PM UTC-8, AndrewTaneGlen wrote: On a good phy boot I see the following: [2.810749] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [2.817206] davinci_mdio 4a101000.mdio: detected phy mask fffe ... On a 'bad phy' boot I see the following (differences highlighted): [2.806763] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [2.813213] davinci_mdio 4a101000.mdio: detected phy mask fffb I'm betting the fe mask eliminates the default 000b bits that are not set by hardware, allowing the good boot. Of the hardware set bits, it seems my chip must get address zero, so all three signals must be zero when reset ends. With mask fe, only the hardware lines are checked. But... Where does the mask come from? I'm not finding it in the boot environment settings. It looks like it is read from the chip: [2.817206] davinci_mdio 4a101000.mdio: detected phy mask fffe But it is not mentioned that I see in the Microchip doc. Always another mystery... On Tuesday, March 11, 2014 12:56:43 PM UTC-7, Gerald wrote: Look in the LAN 8710A data sheet from SMSC. I would cut an paste it, but Microchip has cut and paste blocked. http://www.microchip.com/wwwproducts/Devices.aspx?product=LAN8710ASection 3.7.1 Gerald -- For more
[beagleboard] Re: BeagleBone Black and resistive touchscreen.
On Wednesday, March 5, 2014 1:53:27 AM UTC-5, deniss...@gmail.com wrote: Hello all! Could you help me? And sorry for my bad English :) I'm trying to connect BeagleBoard Black and 7'' resistive touch screen i.q. in the Cape Board http://dlnmh9ip6v2uc.cloudfront.net/datasheets/Dev/Beagle/4DCAPE-43(T)_datasheet_R_1_8.pdf . I used Angstrom OS and Android JB -4.2 , and connected touchscreen to AIN0, ..., AIN3. But it's not working. When you say and, I believe you mean that you tried each Angstrom and Android. Regarding Angstrom, did you try the 2013-06-20 image or the 2013-09-04 image? The latest production version (2013-09-04) is at http://beagleboard.org/latest-images. Can you be more complete in describing how it didn't work? Did the backlight come on? Did you get a bad image? Please include a pastebin.com of the dmesg log. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you 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] Connecting beagle bone black to laptop LAN tthen to 3G USB data card
Hi, I had connected dongle to pc. BBB to PC. Yes, for me it, it worked for 2 times. May be after resetting board, we need to do setting again. There is different procedure to make this permanent change. Pls check derek molly site. On 11 Mar 2014 20:33, moni16...@gmail.com wrote: Hello vinayak, you connected data card to your PC or beagle itself?? because i can access Internet on my PC but when i follow the procedure you mentioned it did not work!! i access internet on Ubuntu using WVDIAl package!! will appriciate any help. On Tuesday, November 5, 2013 1:53:17 AM UTC-5, Vinayak Aghor wrote: Hi I again tried with... -- For more options, visit http://beagleboard.org/discuss --- You received this message because yo... 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: Error Listening To Socket - MOOS-IvP won't run on Beaglebone Black
I have found the problem and fixed it. When the socket is created it needs to be TCP. However when getprotobyname(_sName) is called in the XPCGetProtocol class to lookup the correct protocol number in /etc/protocols it returns the value of the previous time it was called, which was when a UDP socket was setup. To fix it I simply called the function twice, the second time it returns the correct value. I am not sure why it would return incorrect the first time but this works! On Tuesday, 11 March 2014 23:21:08 UTC+10:30, haeusler...@gmail.com wrote: Ok so after much debugging I have found that when the Listen thread socket is started it starts as a UDP socket (determined using lsof) when it should be a TCP socket. What would cause this? On Wednesday, 5 March 2014 20:32:54 UTC+10:30, haeusler...@gmail.comwrote: I managed to get it to work in single threaded mode. Has any one had any issues with threads with the BBB? On Wednesday, 5 March 2014 18:58:42 UTC+10:30, haeusler...@gmail.comwrote: I am attempting to run MOOS-IvPhttp://oceanai.mit.edu/moos-ivp/pmwiki/pmwiki.php?n=Main.HomePageon a Beaglebone Black On attempting to run the MOOS database it continuously throws the exception Exception Thrown in listen loop: Error Listening To Socket. Operation not supported This software runs on a Raspberry Pi Any ideas what might be the issue? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
