Sure. Right now, I just keep track of how many messages are in flight and
I don't allow it to queue too many.
That's useful once you know what the bug is. Fortunately, I hit this bug
before I had two threads (one receiving USB and one receiving ethernet)
which would have made hunting it down
I've just posted v2 of the PRU Cookbook[1]. It should help with some of
your questions.
I suggest doing all the development in cloud9 on the Beagle. the PRU
compiler is already installed on the current images.
--Mark
[1] https://github.com/MarkAYoder/PRUCookbook
On Friday, June 19, 2020 at
wm.b.barnett wrote:
>
> Are there 2GB Linux images available? I have an older B-version and would
> like to use it in a small application.
>
>
Yes, 2 GB Linux Images are available but there is the limitations for the
speed and performance. You cannot use it for complex applications.
However, if
Hi there,
My BeagleBone Green has had major problems with the Ethernet phy since I
got it many years ago. There is a patch for Linux here:
https://github.com/RobertCNelson/bb-kernel/blob/am33x-v5.3/patches/drivers/ti/cpsw/0001-cpsw-search-for-phy.patch
I asked in #beagle on FreeNode IRC about t
The only part that shouldn't match is the logo (which we have stripped from
the source). We have, at times, taken the source design and handed it off
for manufacturing to be certain it matches. However, in this case, we
relied on Embest to provide us with matching design files to the production
han
Bill Barnett wrote:
> [-- text/plain, encoding 7bit, charset: UTF-8, 14 lines --]
>
> Are there 2GB Linux images available? I have an older B-version and would
> like to use it in a small application.
>
The 'console' versions are smallest, the image file is only about 1Gb.
You'll only have ssh
You could increase the vring buffers or check for full and retry depending on
how critical the timing is.
Sent from Yahoo Mail on Android
On Tue, Jun 23, 2020 at 2:04 AM, Andrew P. Lentvorski
wrote: Urk, sorry I didn't quite get the implications of this statement:
The kfifo is used onl
Urk, sorry I didn't quite get the implications of this statement:
The kfifo is used only on the receive path because of the asynchronous
> callbacks. The
> Tx-path is synchronous, the copy is attempted directly on the vring buffers
>
That means that kfifo doesn't exist on send so the only avail
