[beagleboard] Re: Why do only these 3 PWM pins work but none others?
Actually, I even tried to manually pass my P8_34 device tree overlay to the cape manager: /lib/firmware$ sudo sh -c echo bone_pwm_P8_34 $ SLOTS Then it looked good, like: root@beaglebone:~# cat $SLOTS 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN 7: ff:P-O-L Override Board Name,00A0,Override Manuf,am33xx_pwm 8: ff:P-O-L Override Board Name,00A0,Override Manuf,bspwm_P9_14_6 9: ff:P-O-L Override Board Name,00A0,Override Manuf,bspwm_P9_22_13 10: ff:P-O-L Override Board Name,00A0,Override Manuf,bspwm_P8_19_4 11: ff:P-O-L Override Board Name,00A0,Override Manuf,bspwm_P8_46_b 12: ff:P-O-L Override Board Name,00A0,Override Manuf,bone_pwm_P8_34 But when I went to run the PWM channel, I got this error: error: Failed to find devicetree fragment: bspwm_P8_34_2 Please help! Thanks!!! Donovan On Sunday, February 8, 2015 at 6:33:59 PM UTC-8, donov...@gmail.com wrote: Thanks for the advice, Graham. After disabling HDMI by editing uEnv.txt, I was able to gain functionality of these pins: 8_36 (works but requires EHRPWM1A but that is already in use by 9_14) 8_45 (works but requires EHRPWM2A but that is already in use by 8_19) 8_46 (this one seems to work well) *Can you please explain to me why disabling HDMI didn't help 8_34 work?* By the way, I'm on Debian GNU/Linux 7 and my BBB was Rev. C. Thanks!!! On Sunday, February 8, 2015 at 6:04:50 PM UTC-8, Graham wrote: Donovan: In your Molloy book, read about device trees, which set the default assignment of the I/O pins. Also read about the pin-mux. And related topics like pin-mux helper and device tree overlays. Then find the reference in the book to the BBBP8 and BBBP9 header file spread sheets on the web site for the book and down-load them. There are up to eight different things that each pin can assigned to do. The ones that are giving you errors have been assigned to do things other than PWM. For instance, some are audio (mcasp0) pins, or some are LCD driver pins. There are multiple ways to reroute the functions, and change them from the default assignments, to the functions you want. But make sure that what they are doing is not important to the operation of the BBB. Enough of it is in the book, that you can figure it out. And the next time you ask for help, be sure to say what version of BBB you have, and what kind and version of OS you are running, because the answers/methods/rules are different on different versions of OS and hardware. --- Graham == On Sunday, February 8, 2015 at 7:28:16 PM UTC-6, donov...@gmail.com wrote: Also, I chose to explore these pins by doing: /lib/firmware$ *ls bone_pwm** as stated on p.231 of Derek Molloy's BBB book.. Thank you!!! Donovan On Sunday, February 8, 2015 at 5:25:10 PM UTC-8, donov...@gmail.com wrote: Hello folks, I'm so frustrated. I can't find any pattern to why I can only get 3 PWM pins to work. Particularly, when I try to send a PWM command to some pins using bb.analogWrite it crashes my BBB. Error Details: Failed to find device tree fragment. My Findings: Through some experimentation I've found this: 8_13 - Error 8_19 - WORKS 8_34 - Error 8_36 - Error 8_45 - Error 8_46 - Error 9_14 - WORKS 9_16 - Error 9_21 - Error 9_22 - WORKS 9_28 - Error 9_29 - Error 9_31 - Error 9_42 - Error Can someone tell me exactly WHY each of these pins works or doesn't work? I can't really find a pattern to this so I'm stumped. Thank you, Donovan -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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: tencent USB wifi (MT7601) cannot be found in ubuntu14.04.1
My board is beaglebone black rev C 在 2015年2月9日星期一 UTC+8下午5:14:28，dawei wang写道： I use tencent USB wifi (MT7601), and follow the driver install instructions: sudo apt-get install git git clone https://github.com/porjo/mt7601.git cd mt7601/src make sudo make install sudo mkdir -p /etc/Wireless/RT2870STA/ sudo cp RT2870STA.dat /etc/Wireless/RT2870STA/ sudo modprobe mt7601Usta On my atom ubuntu 14.04.1 LTS, it works fine. On my BBB board, my OS version: Ubuntu 14.04.1 LTS \n \l rcn-ee.net console Ubuntu Image 2015-01-06 Support/FAQ: http://elinux.org/BeagleBoardUbuntu got from wget https://rcn-ee.net/rootfs/2015-01-06/flasher/BBB-eMMC-flasher-ubuntu-14.04.1-console-armhf-2015-01-06-2gb.img.xz I followed the same instruction and can find mt7601Usta using lsmod With lsusb, I can find the USB wifi Bus 001 Device 003: ID 2a5f:1000 no device name followed (same as my PC). When I use ifconfig -a, I cannot find wlan or other relative network adapter. I don't know how to debug this issue, can someone help me? Thanks. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] tencent USB wifi (MT7601) cannot be found in ubuntu14.04.1
I use tencent USB wifi (MT7601), and follow the driver install instructions: sudo apt-get install git git clone https://github.com/porjo/mt7601.git cd mt7601/src make sudo make install sudo mkdir -p /etc/Wireless/RT2870STA/ sudo cp RT2870STA.dat /etc/Wireless/RT2870STA/ sudo modprobe mt7601Usta On my atom ubuntu 14.04.1 LTS, it works fine. On my BBB board, my OS version: Ubuntu 14.04.1 LTS \n \l rcn-ee.net console Ubuntu Image 2015-01-06 Support/FAQ: http://elinux.org/BeagleBoardUbuntu got from wget https://rcn-ee.net/rootfs/2015-01-06/flasher/BBB-eMMC-flasher-ubuntu-14.04.1-console-armhf-2015-01-06-2gb.img.xz I followed the same instruction and can find mt7601Usta using lsmod With lsusb, I can find the USB wifi Bus 001 Device 003: ID 2a5f:1000 no device name followed (same as my PC). When I use ifconfig -a, I cannot find wlan or other relative network adapter. I don't know how to debug this issue, can someone help me? 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] kernel question
I guess the kernel from beagleboard is much different because it contains a lot of patches from the community. The mainline kernel does not have them 2015-02-07 23:02 GMT+03:00 patrick...@gmail.com: Hello, I would like to ask what is the diffewrent between the two kernel 1) kernel 3.8 from git://github.com/beagleboard/kernel.git 2) kernel 3.8 from https://www.kernel.org/ Patrick -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- LinkedIn - http://www.linkedin.com/in/maximpodbereznyy Company - http://www.linkedin.com/company/mentorel Facebook - https://www.facebook.com/mentorel.company -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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 Thursday, February 5, 2015 at 11:16:55 AM UTC-7, alexschn...@gmail.com wrote: After I and my colleagues had fruitlessly tried many things, our hardware developer came up with a working solution: delaying the PHY initialization performed by the U-Boot we use (v2014.10, git checksum c43fd23cf619856b0763a64a6a3bcf3663058c49). This ensured that U-Boot code tried to access LAN8710A only after this chip had come out of reset. So, inserting udelay(100); at the beginning of board_eth_init() function in board/ti/am335x/board.c and recompiling U-Boot worked in our experiments. Alex, I've compiled a boot-loader with the delay in the Ethernet initialization and have done some quick testing on it. I haven't seen any issues yet (where I normally would) but have only tested one board so far. To be exact, I've power cycled a BBB 20 times and confirmed that the Ethernet was working after each boot. Normally I would have seen at least a few Ethernet lockups after 20 resets on this board. There may be something to this. Regards, Bill -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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] Debian emmc flash image with kernel version 3.14
Hi, I'm trying to find a Debian image to flash via emmc onto my beaglebone black rev-c. The problem is I am trying to use a 4D LCD-70T cape, which apperently does not support kernel version 3.14. I have tried with the most recent image available here: http://beagleboard.org/latest-images, and have run into a few issues. It seems that the OS refuses to boot. I would really like to try with an older kernel version, but cant seem to find a flashing image with an older version available. Any help would be appreciated. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: BBB with chrony and RTC
Hi Colin, Same problem here. I'm trying to successfully used chronyd , gpsd with debian to setup the hwclock and sysclock upon each powerup since my BBB will never be connected to a LAN and access NTP servers. So far, setting up gpsd with a Garmin GPS is fine. But chrony never updates the rtc or the sysclock. Would be glad to figure out a way to do this :-) JF Le jeudi 5 février 2015 12:01:01 UTC-5, Colin Bester a écrit : I am running debian 3.8.13-bone47 on Beaglebone black and have a RTC cape up and running (/dev/rtc1) together with chrony 1.24 If I manually run chronyd -s then it does load time from /dev/rtc1 I am wanting to be able to call trimrtc using chronyc and have inserted rtcfile and rtcdevice into /etc/chrony/chrony.conf rtcfile /var/lib/chrony/chrony.rtc rtcdevice /dev/rtc1 If I don't insert rtcfile then when running *trimrtc* in *chronyc* I get error of no RTC driver found. If I include the rtcfile, then I get message of *OK* when running trimrtc but rtcfile is not read. Looking at syslog, if I include *rtcfile* in *chrony.conf* then I get an error Could not start measurement : Invalid argument but doesn't say due to what. I I comment out declaration of rtcfile then I get no errors when starting chronyd but trimrtc fails with error message of RTC driver not found. Has anyone gotten chrony to work on BBB running debian and able to access/trim RTC? Thanks Colin -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Control 5V relay with my BeagleBone Black GPIO
Hi, I have a 5V Relay shield to control with my BBB, i know the GPIO work with 3.3V, i see an instructable that i can shunt the leds in my relay shield and it will work, it is safe for my bbb to do that? Modifications for Driving a 5V relay module from a 3.3V Arduino board http://www.instructables.com/id/Home-Automation-How-to-Add-Relays-to-Arduino/step6/Modifications-for-Driving-a-5V-relay-module-from-a/ My relay board: Relay Board http://wiki.iteadstudio.com/4_Channels_5V_Relay_Module Thanks, -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Can't run bonescript while using VNC
Hi All, I am having some problems running bonescript without cloud IDE 9. The weird thing is when I run the javascript file that requires bonescript while SSH'd as root it works perfectly, the problem is when I VNC into the beaglebone and try to run the exact same script. Here is some information that may help: OS: Debian 7.8 (Wheezy) Board version: Beaglebone black rev. B6 (as printed on the underside of the board) Kernel: 3.8.13-bone50 When I try to run the javascript file that requires bonescript while VNC'd I get the following output: module.js:340 throw err; ^ Error: Cannot find module 'bonescript' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.anonymous (/home/debian/testBBB.js:1:71) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) I am trying to run bonescript without using cloudIDE9 since I do not have internet connectivity where the BBB will be installed. I really appreciate any help. Please let me know if something I said above is unclear. -Gabe -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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] PWM output on Beaglebne Black 3.8.13 - bone_pwm errors
Hi, I have tried to get PWM signals to work on my Beaglebone Black, to use it with the DRV8833 Servo Controller (Which needs 4 PWM inputs). I actually got a tricky Problem, controlling two PWMs of the same Controller. The Problem is, setting run in the pwm_test_PX_XX for multiple times leads to a wrong output. I did: # export SLOTS=/sys/devices/bone_capemgr.9/slots # echo am33xx_pwm $SLOTS # echo bone_pwm_P9_14 $SLOTS # echo bone_pwm_P9_16 $SLOTS to setup the Pins. Then I controlled them by: # cd /sys/devices/ocp.3/ # echo 0 pwm_test_P9_14.15/run # echo 0 pwm_test_P9_16.16/run because they initially are turned on. Now, if I try to set them on and off again, it often happens, that the output does not match the run values (setting both off and one is still sending). I encountered that Problem with both 3.8.13 bone50 and 3.8.13 bone70 kernels. Is there any info about the PWMss I am missing? I havent found very much about that Problem on google... -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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] The time for Google Summer of Code is now!
See http://beagleboard.org/blog/2015-02-09-time-for-gsoc/ We'll be meeting up on http://bit.ly/bbgsocchat (#beagle-gsoc) every Wednesday at noon US Eastern time (http://bit.ly/bbgsocmeet), which is 5PM GMT until March 8th when it switches to 4PM GMT. Google starts accepting applications for potential mentoring organizations on today, February 9th. BeagleBoard.org is going to send in an application. Your help is needed to make that application as strong as it can be! 1) Sign up on the mailing list: http://bit.ly/bbgsocml 2) Join the eLinux wiki and review/update the ideas page: http://bit.ly/bbgsocideas 3) Prospective mentors: update your info on the ideas page (change something so I know you are alive or I'll remove you) 4) Prospective students: contact prospective mentors NOW and start looking for simple tasks to prove your ability to handle a project Need some motivation and inspiration? Check out some of the cool projects that have been executed under BeagleBoard.org's mentorship under the Google Summer of Code in previous years. I've grouped them by some of the typical focus areas where BeagleBoard.org seeks to improve the status of open source software. * Improving initial experience for novice developers * Linux kernel support for embedded devices and interfaces * ARM processor support in open source operating systems and libraries * Heterogeneous co-processor support in open source operating systems and libraries * Linux userspace support of embedded devices and interfaces in high-level languages . -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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: plans for next beaglebone with am437x?
A new one. Dual core A15 1.5GHZ. Gerald On Fri, Feb 6, 2015 at 7:20 PM, rh_ richard_hubb...@lavabit.com wrote: On Fri, 6 Feb 2015 14:14:06 -0800 Rick Mann rm...@latencyzero.com wrote: Actually, I'd love to hear your thoughts on that processor, good or bad. Actions speak louder than words. Which chip did he choose? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: GPIO_40 vs PWM
Why does the device tree list get updated automatically SOMETIMES when I run an AnalogWrite command in BeagleScript? And sometimes it doesn't. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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] I2c not detecting
i2c is not detecting when i give command i2cdetect -r 1 its shows error only it shows i2cdetect -r 0 kindly help me to detect i2c -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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] 5V Relay Board for BeagleBone Black RevC
Hi, I have a BeagleBone Black and Shield Relay board 5V, i want to use this shield to control a contactor but the GPIO in BBB are 3.3V, i see an instructable that i can modify with a shunt in the Leds control this relays with 3.3V, do you think it´s enough to do that and safe for my bbb? Thanks, -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] i2c detect problem
when i am enabling temporally its showing both i2c0 and i2c1 but when i am enabling it permsmently by pasting capemgr.enable_patno=BB-I2C1 in uEnv.txt file its noe detecting -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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 Cape EEPROM format update
I remember populating this info for my XBee Cape, only to find that it is not used at all. I think it is still a good idea to have the info in there in case it is really used in the future. In theory it should be possible to have the cape configured without the need for a DTB file for each cape. On Mon, Feb 9, 2015 at 6:45 PM, Joshua Datko jbda...@gmail.com wrote: The SRM defines a very specific format for BeagleBone Black cape EEPROMs[1]. AFAIK, the only fields that are actually required are the Board Name and Version, which is used on boot to load the appropriate DTS file. If this is the case can we change the other fields to optional? There's a lot of great meta information in there, but if it's not required can the documentation be changed to make it explicitly not required? Josh [1] Table 17, section 8.2.4, page 101 of https://github.com/CircuitCo/BeagleBone-Black/blob/master/BBB_SRM.pdf?raw=true -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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 Cape EEPROM format update
On Mon, 2015-02-09 at 20:08 -0500, Philip Polstra wrote: I remember populating this info for my XBee Cape, only to find that it is not used at all. I think it is still a good idea to have the info in there in case it is really used in the future. In theory it should be possible to have the cape configured without the need for a DTB file for each cape. The data in there is useful and I can think of some other useful data, like a link to the elinux site. But if I put my manufacturer hat on, I want to know what's required and what's recommended. For example, the CryptoCape doesn't populate the week the board was made [1]. SparkFun uses it's own system AFIAK. I think that the EEPROM Spec, as written, doesn't match current practice. Nice-to-haves are nice-to-have, but it would be nice if that was indicated in the spec. ;) Josh [1] This is a result of my recommendation, so feel free to blame me, not SparkFun on this one. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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 not booting due to modification of uEnv.txt
Thanks Graham, that helped me too. Somehow the uEnv.txt file seemed to have disappeared completely from the EMCC. I can still see other stuff I put there but not that file. On Monday, February 9, 2015 at 6:17:12 AM UTC+11, cooolf...@gmail.com wrote: I accidently modified uEnv.txt file located in eMMC of my Beaglebone black. Now the board is not booting. I can not even see BBB for serial connection from terra term (Windows 7 after drivers are installed). How can I get access to the board? If I can just access to uboot I could reflash or run it using nfs. Any ideas? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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] Control 5V relay with my BeagleBone Black GPIO
Hi; I took a look at both circuits. There’s uses an opto-isolator, so shorting the LED should work. In your case, the 1K resistor on the base will load the GPIO too much. I used a 10K base resistor with a 100K pull down. Basically multiply both of your values by 10 and you8 should be fine. I would hook the LED in parallel with the relay coil. Good Luck Bill From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On Behalf Of cmct...@gmail.com Sent: Monday, February 09, 2015 8:57 AM To: beagleboard@googlegroups.com Subject: [beagleboard] Control 5V relay with my BeagleBone Black GPIO Hi, I have a 5V Relay shield to control with my BBB, i know the GPIO work with 3.3V, i see an instructable that i can shunt the leds in my relay shield and it will work, it is safe for my bbb to do that? Modifications for Driving a 5V relay module from a 3.3V Arduino board http://www.instructables.com/id/Home-Automation-How-to-Add-Relays-to-Arduino/step6/Modifications-for-Driving-a-5V-relay-module-from-a/ My relay board: Relay Board http://wiki.iteadstudio.com/4_Channels_5V_Relay_Module 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 the Google Groups BeagleBoard group. To unsubscribe from this group 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 Pulse Width Modulation Linux 3.181-bone1
Hi, I am having some trouble trying to follow this, please will you elaborate on the XXX.dtb, I am not sure how to create this file. please also share your method for compiling pwm_test.c as I tried multiple time with no success? Thank you, Graham -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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 not booting due to modification of uEnv.txt
Well these instructions are for the later single partition Debian distributions. The 7.5, distribution has the uEnv.txt file in a separate FAT partition, so the mounting instructions are slightly different, if you need to get at the file in a different partition. --- Graham == On Mon, Feb 9, 2015 at 2:58 PM, JS-BBB jsamperi2...@gmail.com wrote: Thanks Graham, that helped me too. Somehow the uEnv.txt file seemed to have disappeared completely from the EMCC. I can still see other stuff I put there but not that file. On Monday, February 9, 2015 at 6:17:12 AM UTC+11, cooolf...@gmail.com wrote: I accidently modified uEnv.txt file located in eMMC of my Beaglebone black. Now the board is not booting. I can not even see BBB for serial connection from terra term (Windows 7 after drivers are installed). How can I get access to the board? If I can just access to uboot I could reflash or run it using nfs. Any ideas? -- 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/l0oh8Amfmbw/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] Beaglebone Black Ethernet Phy Not Detected on Boot.
If this ends up being the solution, can you please post a guide for those not as up to speed as you on precisely how to implement this fix? Thanks On Thursday, February 5, 2015 at 1:16:55 PM UTC-5, alexschn...@gmail.com wrote: Hello everybody, After I and my colleagues had fruitlessly tried many things, our hardware developer came up with a working solution: delaying the PHY initialization performed by the U-Boot we use (v2014.10, git checksum c43fd23cf619856b0763a64a6a3bcf3663058c49). This ensured that U-Boot code tried to access LAN8710A only after this chip had come out of reset. So, inserting udelay(100); at the beginning of board_eth_init() function in board/ti/am335x/board.c and recompiling U-Boot worked in our experiments. We haven't yet done many experiments, but at least the board, whose PHY failed almost every time before, always starts successfully now. I would appreciate if you repeat this experiment with the delayed PHY initialization and report the results here. I guess the problem was, as described in the reply from Texas Instruments mentioned by Micka https://groups.google.com/d/msg/beagleboard/9mctrG26Mc8/2aova_Jd__EJ (I misunderstood that earlier), that LAN8710A starts to function correctly at a slightly higher voltage level than the microprocessor, and may come out of reset too late with respect to the microprocessor. This agrees with the observation that a higher capacity on nRESET_INOUT only worsens things, because it makes the slope of the reset pulse more flat, thus increasing the time lag between the starts of the two chips. @ c2h2: Thank you for your reply. As far as I understand, you delayed the reset of the microprocessor with respect to the reset of LAN8710A by means of some RC circuit, right? If this is correct, could you please provide more details about that circuit? @ Vince Caldeira: Could you please explain, why you marked the topic as complete? If you know any better solution of the problem, please share that with us. Regards, Alex On Tuesday, December 30, 2014 at 2:37:25 PM UTC+1, Christopher and Christina Myers wrote: Based on all the comments and discussions I've seen before and after purchasing my BBB, I'm sure someone will figure out how to fix the issue. However, unfortunately my knowledge isn't that advanced yet, so while I can understand what folks are saying (usually,) I'm not at the level to be able to figure this out :/ It does sound like folks have fixes in the works though. OOC, have you tried any other OSes to see if the problems with your board persist? I know openSuSE has one as well, but not necessarily support for all the GPIO built-in. On Friday, December 26, 2014, John Tucker ars_...@windstream.net wrote: As I continue to struggle with this problem and asking myself if I wasted my money on a product that is not working as advertised, I was wondering if it is possible to reset the ethernet interface on the board after the OS has booted, either via a script or some other means. Anyone try this at all? I'm not ready to give up but this board should work with an ethernet cable. For what it is worth, my pcDuino3 works flawlessly compared to the BeagleBone Black. So I hope the people who make the BBB make this right for all of us who have purchased this product and have been dissappointed. John On Wednesday, December 24, 2014 3:18:11 PM UTC-5, John Tucker wrote: Thanks for the suggestions. I reflashed the eMMC today with a very recent version of Debian (12/19). This version appears to be reasonably stable. But after rebooting and trying your suggestion, Ethernet was still not available. I even tried booting without an Ethernet cable installed and then plugged it in. Nothing. But what I do see now is the green LED flashing quite a bit. So there is something going on but I never seen any flashing from the Orange/Yellow LED. I can connect to a static IP address but can't seem to get any bi-directional communication. I open a browser and try to go to a website but all I can see is the Resolving host message in the browser telling me that something is not just right. After trying to use Putty with no success, my guess is that the BBB is not getting any incoming packets at all. I'm open to other suggestions. I want to use the BBB for ADS-B receiving with an RTL-SDR. I can use a wireless dongle if I have to. Thanks. John On Tuesday, December 23, 2014 2:26:24 AM UTC-5, Christopher and Christina Myers wrote: Try my solution a couple of posts up - basically, just hit the reset button on the board with the board booted and Ethernet plugged in. On Monday, December 22, 2014, Micka micka...@gmail.com wrote: reboot multiple time and try to get the orange Led ! Le Mon Dec 22 2014 at 14:44:00, ars_n8...@windstream.net a écrit : I just purchased a Beaglebone Black Revision C and I appear to be having this
[beagleboard] BeagleBone Cape EEPROM format update
The SRM defines a very specific format for BeagleBone Black cape EEPROMs[1]. AFAIK, the only fields that are actually required are the Board Name and Version, which is used on boot to load the appropriate DTS file. If this is the case can we change the other fields to optional? There's a lot of great meta information in there, but if it's not required can the documentation be changed to make it explicitly not required? Josh [1] Table 17, section 8.2.4, page 101 of https://github.com/CircuitCo/BeagleBone-Black/blob/master/BBB_SRM.pdf?raw=true -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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: debian: release candidate: 2014-12-11
There are no device-tree overlays with the 3.14 kernel. You'll have to merge your device-tree changes with the main BBB device tree and build a new dtb file. Can you please elaborate a little on that? Can I use my old .dts file or do I need to recreate it somehow? If so, where can I find examples of how it needs to look like? Where do I need to place the dts once it's ready before calling make on the dtb-rebuilder? Thanks, Sebastian -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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] Mobile Developers - iOS and Android ::::: Columbus, OH
On 10/02/15 09:08, rajagut...@gmail.com wrote: Hi, This is Nagaraju Gutta, - Recruitment and Resources from SancroSoft USA Inc. We have an urgent requirement as follows: snip Requirement Details Mobile developers - iOS and Android Maybe you should spam iOS and Android mail lists, then... -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
