[beagleboard] Re: BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
1st of all IF you used the FETs shown on Adafruit they are logic level FETs, so you can drive them directly from the BB. Resistors are only required if you had used the transistors instead of the FETs. As discussed you missed the GND wire (Black) as shown on Adafruit. Where did you measure the 200mV? From the BB GND to the outputs or elsewhere? As you don't have a common GND readings are pretty much meaningless. FETs have a large capacitance on the Gate, without a common ground you could have several hundred (or thousands) volts of static charge for a very short period, but it could be large enough to kill the processor. Very likely if you have carpets around. If you unplug everything you added to the BB will it boot up again? If not the above may be possible. You seem to be using P9_12, P9_16 and P9_21 they should be safe to use as I'm using them on a couple of projects without problems, you MUST add the GND wire from any pin 1 or 2 of either P8 or P9 to the GND track of your breadboard. I may think of something else later on... meanwhile, as I said above, unplug everything from the BB and see if it powers up, if not it's shopping time again. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
If I assume that the ground on the circuit didn't have a connection to the BBB ground Nothing to assume :-) , there is NO ground connection between the BB and the bread board from what the picture shows, just 3 wires (Red, Green, Blue) not 4. If Adafruit said they could not see anything wrong with the wiring I would be very worried about their technical support -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Minimum PC specs fro BBB drivers
And a bit more OS is Win XP. An interesting thing: both the usbser and the net drivers do not show any size on the control panel, the other 2 are 0.15MB each On my working PC (also XP) usbser and the net drivers show up as 393MB each and the other 2 are 0.15MB each. This is in spite of the fact that I copied the BONE_DRV.exe from my working PC just in case I had a corrupted file. Must be something simple... (not enough RAM??) On Sunday, March 1, 2015 at 4:38:44 PM UTC+11, JS-BBB wrote: Is there a minimum PC requirements to install BONE_DRV.exe? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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] Minimum PC specs fro BBB drivers
Is there a minimum PC requirements to install BONE_DRV.exe? I'm trying to use an old laptop which sits in the corner of my workshop to run some test code on a BBB. The laptop is a TE2000, 1GHz with 512M ram, maybe not enough resources? I have tried several times, the drivers seem to install correctly but then it tries to restart and I get the blue screen of death and must use the power switch to shut down. When the computer restarts I can see the serial port on com16 and the terminal program is happy to open it but there is no comms and the terminal eventually crashes, trying to remove the 4 drivers from the control panel results in the bottom 2 driver not uninstalling. More if needed. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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
On Friday, February 13, 2015 at 5:19:18 AM UTC+11, cooolf...@gmail.com wrote: I really wished BBB had serial port like most boards have. It does, I use the console port with a RS232 converter at 115K. I have soldered a R/A connector at the back of the board so that I can use it even if a cape is plugged in. It's designed to use a standard FTDI USB TTL adapter. The image I downloaded before was just a stripped down, console only, version which booted from SD. This allowed me to recover the EMCC version after fixing up the uEnv.txt file. https://rcn-ee.net/rootfs/bb.org/testing/2015-02-01/console/bone-debian-7.8-console-armhf-2015-02-01-2gb.img.xz The serial port console starts spitting out stuff even before the USB COM port does. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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: 5V Relay Board for BeagleBone Black RevC
Do you have a link to the instructable? Some of the ones you find should be called DESTRUCTABLES On Tuesday, February 10, 2015 at 12:44:02 AM UTC+11, cmc...@gmail.com wrote: 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.
Re: [beagleboard] Using GPIO2_6 to GPIO2_15 as inputs
Thanks Charles, I was afraid of that. I'm learning a lot, real fast. SRM?? Something new, I guess it's the equivalent of Read The Fabulous Manual? :-) So it's back to using the internal pull ups for those pins, not too bad I guess. If I need to make another board in the future I can use a couple of 74HC365 tristate buffers to isolate those pins at reset. On Friday, February 13, 2015 at 1:07:57 AM UTC+11, Charles Steinkuehler wrote: Is there some EEPROM or fuse settings for that? No. The boot pins are used by the hardware when it comes out of reset to determine the desired boot mode. If you wish to drive these pins, you need to insure you do so only after the system reset line goes high. This is all covered in the BBB SRM. -- Charles Steinkuehler cha...@steinkuehler.net javascript: -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Using GPIO2_6 to GPIO2_15 as inputs
Got the current SRM, my PDF was January 2013! I guess not Mr Coley's finger nails on the 1st page? :-) So does the BBB have 65K ways of booting up? It surely seems to be an overkill using 16 pins, but what do I know. :-) On Friday, February 13, 2015 at 7:30:38 AM UTC+11, Charles Steinkuehler wrote: SRM = System Reference Manual You can find it alongside the hardware design files: http://elinux.org/Beagleboard:BeagleBoneBlack#LATEST_PRODUCTION_FILES_.28C.29 Sections 8.1.1 and 8.3 cover using the LCD/boot pins. On 2/12/2015 2:16 PM, JS-BBB wrote: Thanks Charles, I was afraid of that. I'm learning a lot, real fast. SRM?? Something new, I guess it's the equivalent of Read The Fabulous Manual? :-) So it's back to using the internal pull ups for those pins, not too bad I guess. If I need to make another board in the future I can use a couple of 74HC365 tristate buffers to isolate those pins at reset. On Friday, February 13, 2015 at 1:07:57 AM UTC+11, Charles Steinkuehler wrote: Is there some EEPROM or fuse settings for that? No. The boot pins are used by the hardware when it comes out of reset to determine the desired boot mode. If you wish to drive these pins, you need to insure you do so only after the system reset line goes high. This is all covered in the BBB SRM. -- Charles Steinkuehler cha...@steinkuehler.net javascript: -- Charles Steinkuehler cha...@steinkuehler.net javascript: -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Using GPIO2_6 to GPIO2_15 as inputs
I know, I should have asked this question 6 months ago but I had very little idea about I/O pins then. Only knew that those pins were used elsewhere and that up to 65 I/O were, supposedly, available. So I have managed to disable HDMI and now I can access 48 I/O pins which I need, however the above are messing up boot when pulled high, which is what the cape does. After Googling until my eyes popped out I thought I'd ask here if there is a way of disabling the scanning of those pins at boot up and, somehow, allow booting from EMMC only. Is there some EEPROM or fuse settings for that? I guess I could use internal pull ups of those 10 pins after booting up but it would be much nicer if I used external pull ups like other 38 pins. Another option would be to use tristate buffers which would enable I/O access after boot up but that would require an additional I/O pin which may not be easily accessible. Anyway it would mean a PCB revision which is not really what I want to do right now. So, unless there is a magic way of disabling I/O pins look up, the only other option seems to be internal pull ups. Unfortunately nodejs doesn't seem to like INPUT_PULLUP for some reason so I can't test it. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Beaglebone Black not booting due to modification of uEnv.txt
Thank you very, very much. All good now, could not reply earlier because I have been booting myself after I figured out what I did wrong. :-) Both the messed up uEnv.txt file and the copy were there so I just had to delete the bad uEnv.txt file and copy the back up I had made. The file is now also copied to my PC...just in case On Wednesday, February 11, 2015 at 2:50:02 AM UTC+11, Graham wrote: Several Possibilities: 1.) When you write something to the file system, either a new file or modify a file, you need to type 'sync' on the command line to flush the buffers to the file system, otherwise you can loose the changes at unmount/shutdown. 2.) On the earlier Debian distributions, like 7.5, the uEnv.txt file is not in the 'root' partition, but is in the 'boot' partition, which is what I suspect is going on. mount /dev/mmcblk1p2 disk will mount the 'root' partition mount /dev/mmcblk1p1 disk will mount the 'boot' partition (or something like that, I'm working from memory) Since you can't mount two different partitions with the same name, if you try to mount them at the same time, you will need to call them something different, like disk1 and disk2 or disk_root and disk_boot. --- Graham == On Tue, Feb 10, 2015 at 3:28 AM, JS-BBB jsampe...@gmail.com javascript: wrote: First of all apologies to the OP for crashing his thread :-) but it seems to be the same issue. I have initrd.img-3.8.13-bone47 (Debian) on the EMMC which becomes visible after the above instructions, the disk directory is still on the SD so I only need the mount /dev/mmcblk1p2 disk bit to access it and I can see other stuff I had put in my own directory for test purposes (bonescripts). However I can't see the original uEnv.txt file or the backup copy I had made before the fatal bricking, is it possible they are hiding elsewhere but boot or uboot directories of the EMCC? Copying the uEnv.txt from the SD to the boot directory of the EMCC doesn't restore functionality but it is possible that that files needs to be different than what's on the SD?? I have only started to mess around with the BBB and very lost! On Tuesday, February 10, 2015 at 9:34:27 AM UTC+11, Graham wrote: 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 jsampe...@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 the Google Groups BeagleBoard group. To unsubscribe from this group 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
First of all apologies to the OP for crashing his thread :-) but it seems to be the same issue. I have initrd.img-3.8.13-bone47 (Debian) on the EMMC which becomes visible after the above instructions, the disk directory is still on the SD so I only need the mount /dev/mmcblk1p2 disk bit to access it and I can see other stuff I had put in my own directory for test purposes (bonescripts). However I can't see the original uEnv.txt file or the backup copy I had made before the fatal bricking, is it possible they are hiding elsewhere but boot or uboot directories of the EMCC? Copying the uEnv.txt from the SD to the boot directory of the EMCC doesn't restore functionality but it is possible that that files needs to be different than what's on the SD?? I have only started to mess around with the BBB and very lost! On Tuesday, February 10, 2015 at 9:34:27 AM UTC+11, Graham wrote: 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 jsampe...@gmail.com javascript: 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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] 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.
[beagleboard] Re: Using I/O pins BBB
Just in case anyone else comes up with the same issue I'm posting a list of
pins which can be used without doing anything special, the pins commented
out cannot be used without some (yet to discovered) incantation, mostly see
to be assigned to a LCD cape??
//CON 1
b.pinMode('P9_13', b.INPUT);// GPIO0-31
b.pinMode('P9_11', b.INPUT);// GPIO0-30
b.pinMode('P9_12', b.INPUT);// GPIO1-28
b.pinMode('P9_16', b.INPUT);// GPIO1-19
b.pinMode('P9_14', b.INPUT);// GPIO1-18
b.pinMode('P9_15', b.INPUT);// GPIO1-16
//CON 2
b.pinMode('P9_30', b.INPUT);// GPIO3-16
// b.pinMode('P9_28', b.INPUT);// GPIO3-17
b.pinMode('P9_21', b.INPUT);// GPIO0-3
b.pinMode('P9_26', b.INPUT);// GPIO0-14
b.pinMode('P9_22', b.INPUT);// GPIO0-2
b.pinMode('P9_23', b.INPUT);// GPIO1-17
//CON 3
// b.pinMode('P9_31', b.INPUT);// GPIO3-14
// b.pinMode('P9_29', b.INPUT);// GPIO3-15
b.pinMode('P9_41', b.INPUT);// GPIO0-20
// b.pinMode('P8_33', b.INPUT);// GPIO0-9
b.pinMode('P9_42', b.INPUT);// GPIO0-7
// b.pinMode('P8_31', b.INPUT);// GPIO0-10
//CON 4
// b.pinMode('P8_41', b.INPUT);// GPIO2-10
// b.pinMode('P8_43', b.INPUT);// GPIO2-8
// b.pinMode('P8_35', b.INPUT);// GPIO0-8
// b.pinMode('P8_45', b.INPUT);// GPIO2-6
// b.pinMode('P8_37', b.INPUT);// GPIO2-14
// b.pinMode('P8_39', b.INPUT);// GPIO2-12
//CON 5
b.pinMode('P8_7', b.INPUT);// GPIO2-2
b.pinMode('P8_8', b.INPUT);// GPIO2-3
b.pinMode('P8_9', b.INPUT);// GPIO2-5
b.pinMode('P8_10', b.INPUT); // GPIO2-4
b.pinMode('P8_11', b.INPUT); // GPIO1-13
b.pinMode('P8_12', b.INPUT); // GPIO1-12
//CON 6
b.pinMode('P8_18', b.INPUT); // GPIO2-1
b.pinMode('P8_17', b.INPUT); // GPIO0-27
b.pinMode('P8_13', b.INPUT); // GPIO0-23
b.pinMode('P8_16', b.INPUT); // GPIO1-14
b.pinMode('P8_14', b.INPUT); // GPIO0-26
b.pinMode('P8_15', b.INPUT); // GPIO1-15
//CON 7
// b.pinMode('P8_27', b.INPUT); // GPIO2-22
//** b.pinMode('P8_19', b.INPUT); // GPIO0-22 **OK used for output
for test
// b.pinMode('P8_29', b.INPUT); // GPIO2-23
// b.pinMode('P8_34', b.INPUT); // GPIO2-17
// b.pinMode('P8_30', b.INPUT); // GPIO2-25
// b.pinMode('P8_32', b.INPUT); // GPIO0-11
//CON 8
// b.pinMode('P8_46', b.INPUT); // GPIO2-7
// b.pinMode('P8_44', b.INPUT); // GPIO2-9
// b.pinMode('P8_36', b.INPUT); // GPIO2-16
// b.pinMode('P8_42', b.INPUT); // GPIO2-11
// b.pinMode('P8_38', b.INPUT); // GPIO2-15
// b.pinMode('P8_40', b.INPUT); // GPIO2-13
hmm does the code button work?
On Monday, February 2, 2015 at 7:10:24 PM UTC+11, JS-BBB wrote:
OK trying to post again, this morning's post seemed to have gone nowhere.
I'm trying out the push button/led example using node.js and Bonescripts,
successfully modified it to use 6 I/O pins ORed together so that if any pin
is active the LED comes on.
The issue I'm having is that not all pins seem to be accessible and the
script fail. ie P8_3, P8_40 and others.
Is this to do with the default power up boot mode which makes some pins
not user accessible? Do we know which mode the board wakes up in
(MODE0-MODE7)?
Masochistically I'm using nano as the editor not knowing better and I feel
I have gone back in time 30 years. :-) But it makes me feel young(er )
again.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Post not showing
Thank you, just finding my way around. On Monday, February 2, 2015 at 6:16:27 PM UTC+11, JS-BBB wrote: I posted a question this morning, trying again to see if this one appears. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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: Using I/O pins BBB
This is now a double post, don't know if It can be deleted or locked Other thread here https://groups.google.com/forum/#!category-topic/beagleboard/newbies/BLbSy-tO_V0 On Monday, February 2, 2015 at 7:10:24 PM UTC+11, JS-BBB wrote: OK trying to post again, this morning's post seemed to have gone nowhere. I'm trying out the push button/led example using node.js and Bonescripts, successfully modified it to use 6 I/O pins ORed together so that if any pin is active the LED comes on. The issue I'm having is that not all pins seem to be accessible and the script fail. ie P8_3, P8_40 and others. Is this to do with the default power up boot mode which makes some pins not user accessible? Do we know which mode the board wakes up in (MODE0-MODE7)? Masochistically I'm using nano as the editor not knowing better and I feel I have gone back in time 30 years. :-) But it makes me feel young(er ) again. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Using I/O pins BBB
This is now a double post, don't know if It can be deleted or locked Other thread here https://groups.google.com/forum/#!category-topic/beagleboard/newbies/BLbSy-tO_V0 On Monday, February 2, 2015 at 7:10:24 PM UTC+11, JS-BBB wrote: OK trying to post again, this morning's post seemed to have gone nowhere. I'm trying out the push button/led example using node.js and Bonescripts, successfully modified it to use 6 I/O pins ORed together so that if any pin is active the LED comes on. The issue I'm having is that not all pins seem to be accessible and the script fail. ie P8_3, P8_40 and others. Is this to do with the default power up boot mode which makes some pins not user accessible? Do we know which mode the board wakes up in (MODE0-MODE7)? Masochistically I'm using nano as the editor not knowing better and I feel I have gone back in time 30 years. :-) But it makes me feel young(er ) again. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Using I/O pins BBB
On Tuesday, February 3, 2015 at 4:07:52 PM UTC+11, lazarman wrote: *If its doesnt work what does successfully modified mean? * Thanks for replying, Successfully means that the code WORKS with the pins I'm using but I can't access other pins like the ones above and possibly others. I have a cape with 48 inputs, so far I have 7 pins accessible, haven't tried many of the others yet. *Did you check what gpio pins are being used by board HW and cant be toggled * That's what I'm trying to find out, which of the 8 modes (MODE0 to MODE7) does the boards wake up in so that I can see which pins are useable? The board is new and logging in as root. Someone else will be writing the final code (and he is likely to read this... :-) ) and he knows what he is doing. I'm just messing around and trying to test the cape I have designed and built according to some pin out provided. These are the same pins used in the ledscape project AFAIK. So it is possible that the board need to be switched to another mode in order to use those pins fully and maybe I should give up while I'm sort of ahead. :-) *From:* JS-BBB jsampe...@gmail.com javascript: *To:* beagl...@googlegroups.com javascript: *Sent:* Monday, February 2, 2015 2:42 PM *Subject:* [beagleboard] Re: Using I/O pins BBB On Monday, February 2, 2015 at 7:10:24 PM UTC+11, JS-BBB wrote: I'm trying out the push button/led example using node.js and Bonescripts, successfully modified it to use 6 I/O pins ORed together so that if any pin is active the LED comes on. The issue I'm having is that not all pins seem to be accessible and the script fail. ie P8_3, P8_40 and others. -- -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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] Using I/O pins BBB
OK trying to post again, this morning's post seemed to have gone nowhere. I'm trying out the push button/led example using node.js and Bonescripts, successfully modified it to use 6 I/O pins ORed together so that if any pin is active the LED comes on. The issue I'm having is that not all pins seem to be accessible and the script fail. ie P8_3, P8_40 and others. Is this to do with the default power up boot mode which makes some pins not user accessible? Do we know which mode the board wakes up in (MODE0-MODE7)? Masochistically I'm using nano as the editor not knowing better and I feel I have gone back in time 30 years. :-) But it makes me feel young(er ) again. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Post not showing
I posted a question this morning, trying again to see if this one appears. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group 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: Post not showing
On Monday, February 2, 2015 at 6:16:27 PM UTC+11, JS-BBB wrote: I posted a question this morning, trying again to see if this one appears. Not to worry, this one appeared, just trying to find my way here. I'll re post the question from this morning. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
