Yeah, I always find it suspect when am example is posted and demo'd but
does not seem to work for others.
Headbanging continues.
Jon
On Tuesday, October 22, 2019 at 4:03:38 PM UTC-7, Dobrin Alexiev wrote:
>
> In my case I also see often ping-pong_ball, or more often "segmentation
> fault".
>
Thanks so much. I have been badly stuck up on this.
The link at https://gist.github.com/geekman/5bdb5abdc9ec6ac91d5646de0c0c60c4
also seems to be doing the same. Do you mind having a look and verifying if it
looks ok?
Any specific kernel configuration that needs to go along with the script?
Pl
Correct, only one gadget driver can be loaded.. the default g_multi, or
this custom composite one.
On Tue, Oct 22, 2019, 8:58 PM Fariya Fatima wrote:
>
> Thanks. Does this mean I need to uninstall g_multi?
> I did find this script but when I do a
> echo musb-hdrc.0.auto > UDC (binding to UDC), I
Thanks. Does this mean I need to uninstall g_multi?
I did find this script but when I do a
echo musb-hdrc.0.auto > UDC (binding to UDC), I get failure device or
resource busy
Unsure what the issue is. Could you please help?
On Wednesday, October 23, 2019 at 7:05:41 AM UTC+5:30, RobertCNelson w
On Tue, Oct 22, 2019 at 8:24 PM Fariya Fatima wrote:
>
> Hi,
>
> I am using TI SDK for a variant of beaglebone black. The TI SDK requires
> drivers to be installed on the Windows PC to be able to get network over USB
> access. This is something which is unacceptable to our customer.
>
> I have n
Hi,
I am using TI SDK for a variant of beaglebone black. The TI SDK requires
drivers to be installed on the Windows PC to be able to get network over
USB access. This is something which is unacceptable to our customer.
I have noticed that when I try latest available Debian image on Beagelbone
In my case I also see often ping-pong_ball, or more often "segmentation
fault".
I wonder how can I debug this?
On Sunday, October 20, 2019 at 2:11:54 AM UTC-4, Jon Morss wrote:
>
> I am attempting to run the TIDL example with a Beaglebone AI and the only
> thing it seems to report identifying
Hi Stuart,
I tried to use the PocketBeagle with the battery and also found the extra
current draw. Ultimately I communicated with Octavo and got the following
reply. The OSD3358-SM SiP used on the pocketbeagle internally connects the
LDO1 regulator to both the RTC clock input (VDDS_RTC) as we
