I'm working with a Beaglebone Black to do some signal acquisition using a
laser as a light source.
The sampling/acquisition system is driven through the PRU since I need
pretty tight timing - including pulsing a laser to illuminate a sample.
A problem that we just noticed is that as soon as I l
d.
>
> On 3/30/2016 8:00 AM, Phil Mills wrote:
>
> I'm working with a Beaglebone Black to do some signal acquisition using a
> laser as a light source.
>
> The sampling/acquisition system is driven through the PRU since I need
> pretty tight timing - including pulsing
used on PRU pins) at that moment?*
On Wed, Mar 30, 2016 at 9:32 AM Robert Nelson
wrote:
> On Wed, Mar 30, 2016 at 10:27 AM, Phil Mills wrote:
> > Board spins eat up weeks of project - software / firmware changes are
> > "free". ;-)
> >
> > ...so the powe
on wrote:
>
> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills > wrote:
> > I have inherited responsibility for a bunch of 3rd-party direct clones
> of a
> > Beaglebone Black C5 (only known change is in silkscreening).
> >
> > Since none of these have any contents
:
> On Mon, Apr 18, 2016 at 9:51 AM, Phil Mills wrote:
>
>> Robert,
>>
>> It's been a while on this, but can you re-post the flasher img.xz
>> someplace (bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz
>> <http://rcn-ee.com/rootfs/bb.org/release/
I have a Beaglebone Black with a fresh flash of the 2015-03-01 Debian image
(bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img) that I cannot scp or
rsync large files to.
>From my Wheezy 64-bit host VM, I try to scp a 27MB file to the Beaglebone
via ethernet and the transfer stalls out after <1
Transfer using several Windows utilities (WinSCP and SmarTTY) fail
similarly - the transfer starts out find and then throttles itself to
exinction.
On Thu, Jun 25, 2015 at 4:16 PM, Phil Mills wrote:
> I have a Beaglebone Black with a fresh flash of the 2015-03-01 Debian
> image (bone-
Testing with various Windows SCP utilities fails in a similar way. The
transfer starts out fine and then rapidly throttles down to extinction.
WinSCP, SmarTTY
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Group
twork staff towards would be helpful.
On Thursday, June 25, 2015 at 5:05:59 PM UTC-6, Phil Mills wrote:
>
> Testing with various Windows SCP utilities fails in a similar way. The
> transfer starts out fine and then rapidly throttles down to extinction.
>
> WinSCP, SmarTTY
>
I have inherited responsibility for a bunch of 3rd-party direct clones of a
Beaglebone Black C5 (only known change is in silkscreening).
Since none of these have any contents written to the onboard EEPROM, they
fail to boot with "C" written to the serial console with no uSD card,
and
>
> the SRM, is still valid and is not stale or old.
>
> Gerald
>
>
> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills > wrote:
>
>> I have inherited responsibility for a bunch of 3rd-party direct clones of
>> a Beaglebone Black C5 (only known change is in silkscreening).
nformation to add to a wiki somewhere - I can't be the
only person with blank (or inadvertently borked) BBB EEPROMs running
around.
-phil
On Tuesday, September 8, 2015 at 3:30:18 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills > wrote:
> > I h
e EEPROM than what RCN's
described?
If so, I'd really appreciate a description of how YOU get to an unbootable
BBB to a state where you can write to a blank/corrupted EEPROM.
-phil
On Tuesday, September 8, 2015 at 3:35:32 PM UTC-6, Gerald wrote:
>
> I2C writes is what we d
figuration sequence
won't be any trouble at all.
While I'm asking questions: is there a good reference script / utility to
create an image file (.img.xz format) from an existing BBB ?
-phil
On Tuesday, September 8, 2015 at 4:04:40 PM UTC-6, RobertCNelson wrote:
>
> On Tue,
ep 8, 2015, at 14:38 , Phil Mills >
> wrote:
> >
> > ...now I just have to convince our IT staff / McAffee to white-list your
> web server (if it ain't one thing, it's another) so I can get those files.
>
> Ugh, where do you work that you have s
e connected
8. TP4 grounded to P8-1
9. Power applied via mini-USB cable
10. ""
Suggestions or troubleshooting steps?
I have erased/re-formatted/reloaded the cards 2x with same results.
-phil
On Tuesday, September 8, 2015 at 3:45:03 PM UTC-6, RobertCNelson wrote:
>
>
the board.
I think that's got me running - now to verify it on a few more boards in my
pile.
Much thanks, Robert.
On Wednesday, September 9, 2015 at 11:59:03 AM UTC-6, RobertCNelson wrote:
>
> On Wed, Sep 9, 2015 at 12:52 PM, Phil Mills > wrote:
> > Robert,
> >
I'd like to be able to read/write data from the BBB's on-board EEPROM
programatically using the ioctl(...) interface just like any other i2c
eeprom my software might be asked to go deal with.
Of course the kernel claims that device for itself pretty quickly upon boot
which means I can't get to
like to get around.
On Tue, Aug 9, 2016 at 1:43 PM Gerald Coley wrote:
> You will need to modify the hardware to remove the write protect before
> you can do any writes..
>
> Gerald
>
> On Tue, Aug 9, 2016 at 2:41 PM, Phil Mills wrote:
>
>> I'd like to
ote:
>>
>>> william@beaglebone:~$ sudo dd count=30 bs=1
>>> if=/sys/bus/i2c/devices/0-0050/0-00500/nvmem
>>> ▒U3▒A335BNLT00C03214BBBK0403▒▒30+0 records in
>>> 30+0 records out
>>> 30 bytes (30 B) copied, 0.0114076 s, 2.6 kB/s
>>>
>&
20 matches
Mail list logo
