Re: [beagleboard] Re: os x trouble making SD image

Hold down the boot button before you plug power.. you just have an old u-boot in emmc. Grab one of the flasher images and update it. On May 20, 2017 12:07 AM, "mron" wrote: I just tried the SD card in a different BBB. It works fine. THere's something amiss with the

[beagleboard] Re: os x trouble making SD image

I just tried the SD card in a different BBB. It works fine. THere's something amiss with the old BBB. Is there an update to u-boot I need to install? On Friday, May 19, 2017 at 10:02:40 PM UTC-7, mron wrote: > > I'm trying to make an SD card with the latest Jessie img. I downloaded >

[beagleboard] os x trouble making SD image

I'm trying to make an SD card with the latest Jessie img. I downloaded "bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz" to my mac and checked the shasum. I decompressed it and used "dd if=bone-debian-8.7-iot-armhf-2017-03-19-4gb.img of=/dev/diskX bs=1m" to write to it. Here's the BBB boot

Re: [beagleboard] Pin confusion from existing examples...

On Fri, May 19, 2017 at 3:34 AM, Niels Jakob Buch wrote: > The frustration level is growing... > Sounds like you're experiencing the same thing I did when first starting. One of the biggest hurdles here is going to be related to your knowledge of Linux. After that, knowing the

Re: [beagleboard] Help! Beaglebone Blue seems to have died

On Fri, May 19, 2017 at 8:42 AM, Clark Sann wrote: > William > > If I power my IO through the 3.3V bus on the BB Blue, which turns on as > the BB Blue turns on, will that be sufficient to protect the GPIO? > As Jason mentioned. Please make a separate new post / thread so as

[beagleboard] Re: [beagle-alpha] Re: Quick update regarding BeagleBone Blue documentation

> On May 19, 2017, at 1:33 PM, Clark Briggs wrote: > > Jason, > I’ve been reading/lurking aka not running one. > Trouble shooting says ssh uses root and blank. I thought that was different > now. > Ok, maybe that section is not in getting started. But check it.

[beagleboard] Re: Quick update regarding BeagleBone Blue documentation

I think I've completed the getting-started portion and now need to move to updating bone101. Everyone please look at http://jadonk.github.io/beaglebone-getting-started/START.htm and let me know if anything needs further adjustment on that page itself. On Fri, May 5, 2017 at 9:11 PM James

Re: [beagleboard] Re: Help! Beaglebone Blue seems to have died

On Thu, Apr 13, 2017 at 8:43 AM wrote: > I'm seeing a problem that may be related. We have now fried 3 BeagleBone > Blues Rev A2. > I recommend starting a new thread for a different issue. Otherwise, I find it difficult to see if issues are getting useful responses. I

Re: [beagleboard] Help! Beaglebone Blue seems to have died

William If I power my IO through the 3.3V bus on the BB Blue, which turns on as the BB Blue turns on, will that be sufficient to protect the GPIO? Clark On Friday, March 31, 2017 at 3:48:04 PM UTC-5, William Hermans wrote: > > For instance, if you had any IO connected to this board through any

Re: [beagleboard] Adding Quick Links to Cloud 9 on bone101 page

https://github.com/beagleboard/bone101 is a good place to submit patches. It'll show up live initially at http://beagleboard.github.io/bone101/Support/bone101/ and I'll try to move it to https://beagleboard.org/support/bone101 as I can. I thought the "Fork me on github" link on the top-right made

[beagleboard] Adding Quick Links to Cloud 9 on bone101 page

I've added some "Quick Links" on the bone101 to take you straight to Cloud 9. What repo do I fork so I can do a pull request? --Mark -- For more

[beagleboard] Re: Help! Beaglebone Blue seems to have died

Mine was working fine, until I let the battery that was running it die down. Then it wouldn't restart (same lights as in parent photo). Also seemed to be running hot. I was very excited about this board, but I need more reliability then this. On Thursday, March 30, 2017 at 10:53:30 AM UTC-4,

Re: [beagleboard] Re: Flashing eMMC memory from SD card with Chipsee Debian Jessie

It works great. Thank you. :) Now I have two identical BBBs with Chipsee display. Only one question. Flasher on SD card consists now of one ext4 partition "rootfs". Is it possible to make *.img backup file from this ext4(linux) partitioned SD card on OS Windows 8.1? Win32DiskImager and Windows

[beagleboard] Pin confusion from existing examples...

The frustration level is growing... The Cloud9 IDE seems pretty powerful, but the examples shipped on the image, which is for different editions of BeagleBone does not have any indication is to which ones are meant to work on which board? Thats really strange, and it takes quite some attempts

[beagleboard] Re: I²C reads on broken out bus #1 always return 0

Status Update (a bit off topic for beagleboard, I suppose): I took the MPLABX PIC code that the PiBorg folks provided for their motor controller and ported it to the sdcc compiler, so I have a chance to understand what's going on. Result is here: https://github.com/tkurbad/PicoBorgRev_PIC If

Re: [beagleboard] Weird behaviour: input/output error and no commands after few minutes

I just checked and the JST-SH connector pins, inside the terminal are only 1mm apart. https://is.alicdn.com/img/pb/863/022/524/524022863_862.jpg I guess I will wait for the wire assemblies. On Friday, 19 May 2017 00:06:02 UTC+2, William Hermans wrote: > > > > On Thu, May 18, 2017 at 2:06 PM,

[beagleboard] Re: NodeRed Beagleboard module not part of default image?

Realised that the Nodered Beaglebone library is depending on the Node serial library which has no platform support of this. https://github.com/EmergingTechnologyAdvisors/node-serialport#platform-support I guess this requires some substantial hacking...? I had hoped this worked out of the box

[beagleboard] Re: Node.js or Python bindings for robotics cape?

I am needing this too, and are looking for mature libraries, but havent found any. Havent even been able to use NodeRed on the Blue. On Friday, 19 May 2017 07:14:50 UTC+2, Ari Krupnik wrote: > > I see these node.js bindings, but I can't tell how ready they are for use: >

Re: [beagleboard] Inaccurate timing - Time.h issue

Dear David, Thanks for the suggestion, IT WORKED! latency reduced to 4 uSec that's huge. and yes, I made mistake in pasting the code and removing the comments. Thanks a ton. Reposting the code bellow: #include #include #include #include int main() { struct timespec sT, eT

Re: [beagleboard] Trouble using SPI interfaces on new BBBW

I'm running Adafruit-BBIO Version: 1.0.0. On Thu, May 18, 2017 at 9:00 AM, Garth Webb wrote: > I'll check, but I won't be able to try this until tonight. However this > brings up another question; is there something I can try directly on the > /dev/* devices to see if

Re:[beagleboard] Inaccurate timing - Time.h issue

I suggest you call clock_gettime () twice with nothing between these calls. printf() is a complicated function that may interact with hardware, for example, a serial port or ethernet. The time required to do input or output may depend on the state of the hardware, or on the operation of a