Gianfranco
>
> On Thursday, November 19, 2015 at 4:50:58 PM UTC+1, Kees k wrote:
>>
>> I did some work on this in January. I am not sure it worked well, at
>> least it did something.
>> The code (so far) may help:
>> https://github.com/kkwekkeboom/am335x
I did some work on this in January. I am not sure it worked well, at least
it did something.
The code (so far) may help:
https://github.com/kkwekkeboom/am335x_pru_package/blob/csk_spidriver2/pru_sw/example_apps/PRU_spidriver/PRU_spidriver.p
On Wednesday, November 18, 2015 at 2:15:31 PM UTC+1,
Hello all,
Today I looked on http://elinux.org/Beagleboard:BeagleBoneBlack and saw
that the montly shipments are much lower in 2015.
Is this because there are two manufacturers now? (element14/embest and
circuitco) Or because of decreasing demand?
Kind regards
Kees
--
For more options,
Good morning,
In one of my projects I interface with subsystems using a spibus, which
performs really bad. If I look at the spidev driver, this thing uses a
spinlock (busy polling) while performing the datatransfer and thereby
blocking the kernel.
Is there are any alternative? E.g.
1. A
I have seen this problem repeatedly by A6 revision hardware, but not with
revision A5C hardware (I am running exactly the same software on both).
Noteworthy is that the PHY problem only appears when powering the BBB via
the headers. Powering via USB does not give any problems.
I tried the
, c...@isbd.net wrote:
Robert Nelson robert...@gmail.com javascript: wrote:
On Thu, Mar 20, 2014 at 4:48 AM, Kees k keeskwe...@gmail.comjavascript:
wrote:
I have seen this problem repeatedly by A6 revision hardware, but not
with
revision A5C hardware (I am running exactly the same
, Gerald wrote:
Where are you looking exactly?
Gerald
On Thu, Mar 20, 2014 at 8:51 AM, Kees k keeskwe...@gmail.comjavascript:
wrote:
The 5V is fine (maybe a little spike of 0.8V after 60 ms PS).
However, the 3.3V gives a strange 2-stage powerup cycle. I compared a
revision A5C
Haha, I was looking at the wrong file (BB white A6). Sorry for the trouble;
it seems our cape causes this difference between A5C and A6.
On Tuesday, November 26, 2013 11:22:42 PM UTC+1, AndrewTaneGlen wrote:
Hello,
I have noticed very rare cases (~1/50) of the ethernet phy on the
, 2014 3:36:29 PM UTC+1, Kees k wrote:
Hello all,
Right now I have a beaglebone black (A6), which has been used for 1-2
weeks. Unfortunately, it stopped booting this week. Some days ago it did
not boot, but after resupplying power it it did. Now the BBB does not boot
at all.
-USR0-USR3 never
for reflashing the eMMC..
http://www.elinux.org/Beagleboard:Updating_The_Software
Gerald
On Thu, Feb 6, 2014 at 8:36 AM, Kees k keeskwe...@gmail.com javascript:
wrote:
Hello all,
Right now I have a beaglebone black (A6), which has been used for 1-2
weeks. Unfortunately, it stopped
Hello all,
Right now I have a beaglebone black (A6), which has been used for 1-2
weeks. Unfortunately, it stopped booting this week. Some days ago it did
not boot, but after resupplying power it it did. Now the BBB does not boot
at all.
-USR0-USR3 never lit
-PWR LED lits
-LDO pin 3 (out) =
Hey, did you try another power supply? Probably the PS has problem
supplying the current and drops voltage? Or there is a current limitation.
I tried to reproduce by only connecting P9.5, P9.6 and P9.1 (GND) , but
could not.
On Tuesday, November 19, 2013 2:00:55 AM UTC+1, James Littlefield
I have the same problem, but only when using multiple serial ports at
higher baudrates. I use libmodbus including
*MODBUS_ERROR_RECOVERY_PROTOCOL. *
I notice many CRC errors and timeouts when using four serial ports together.
On Monday, August 26, 2013 8:37:42 AM UTC+2, pyro...@gmail.com wrote:
13 matches
Mail list logo
