TI also provide instructions on building an image
(u-boot/kernel/filesystem) using Yocto at
http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Overview_Building_the_SDK.html
I have used this to build a stripped down kernel with only the kernel
drivers I needed plus a minimal
Hi Daniel,
What I am assuming from your question is that you want to use the TI SDK
u-boot and put it onto a BBB SD card with a debian file system. Note that I
haven't tried this exact thing but I hope to give you pointers to get
started.
The TI SDK assumes a boot partition where it puts the
Hi Jonny,
Looking at that link from Segger it appears that they only support the
cortex-M core devices from TI, so that wouldn't help on a BBB.
The other factor that is important for some of us is that the Segger EDU
emulators are explicitly for non-commercial use. If you are commercial use
Hi Phil,
No it doesn't. It uses a TI Bluetooth device (WL18xx) rather than a
Qualcomm one.
Iain
On Monday, February 10, 2020 at 2:19:07 AM UTC, phil.mar...@gmail.com wrote:
>
> Does Beaglebone Black Wireless support APTX Low Latency Bluetooth?
>
--
For more options, visit
Robert
I've been following the threads earlier in the year about using SGX. As a
first step I tried to build kmscube from git.ti.com.
I used the August Stretch IoT snapshot as recommended (
Hi John,
There are two options I use depending upon my goals
- use the TI SDK (
http://software-dl.ti.com/processor-sdk-linux/esd/AM335X/latest/index_FDS.html).
It is simplest to build (install SDK and do "make"). The BBBW might not be
officially supported but the device tree file is there. The
There is no support in the Wl18xx Wi-Fi device on the BBBW, neither in
the Linux driver nor the actual device firmware.
If you want ad-hoc you would need to use a USB dongle with a Wi-Fi
that does support ad-hoc, but then you might as well use a BBB for
that.
There is low level support for TI's
Hi Matt,
The problem is that the wl18xx has been shut down when WL_EN goes low
when you enter suspend, however on resume connman "thinks" everything
is normal and keeps communicating with it and just getting no
response.
I'm not sure if connmanctl actually drives the WL_EN pin when it
disables and
r 2
** ERROR 0 ***
Can you please advise about it?
Thanks
Jose
On Wednesday, March 1, 2017 at 10:51:14 AM UTC-5, Iain Hunter wrote:
A follow up on this one.
- If you are just missing the user space script to
ean BBBW instead of BBBGW? or if i get you correctly, we should
> create a new patch based on the BBGW device tree but just change the mmc2
> to mmc3?
>
> thanks
>
> On Fri, Mar 3, 2017 at 12:05 AM, Iain Hunter <drhunte...@gmail.com> wrote:
>
>> Hi Nicolas,
>> I'
A follow up on this one.
- If you are just missing the user space script to setup the mesh you can
get them from
https://git.ti.com/wilink8-wlan/wl18xx-target-scripts/trees/R8.7_SP1 - they
are installed as part of the build script, otherwise clone them
independently
- The mesh patches have been
*/
ref-clock-frequency = 3840;
};
};
edma {
ti,edma-xbar-event-map = /bits/ 16 1 32 2 33;
};
On Thu, Aug 27, 2015 at 10:03 PM, Iain Hunter drhunte...@gmail.com
wrote:
Did you use device tree in the end or modify a board.c?
If so that looks like the mmc port is not being probed
snd_soc_tlv320aic32x416689 1
snd_soc_davinci_mcasp18424 2
snd_soc_edma1166 1 snd_soc_davinci_mcasp
uio_pdrv_genirq 3625 0
uio 9898 1 uio_pdrv_genirq
root@arm:~#
On Thu, Aug 20, 2015 at 4:18 PM, Iain Hunter drhunte...@gmail.com wrote:
Hi
Hi,
As a follow up I agree with the previous statement that wl127x drivers have
no device tree support. So you'll need to merge device tree support from
wl18xx drivers. As far as I can remember there are no major changes to
parameters passed by device tree to WiFi driver from wl127x to wl18xx. As
, visit https://groups.google.com/d/optout.
From 25aca78652ff48831516cebb7adea39f71d95974 Mon Sep 17 00:00:00 2001
From: Iain Hunter i-hunt...@ti.com
Date: Thu, 2 Jul 2015 14:44:08 +0100
Subject: [PATCH] use standard location for udhcpd.conf
---
boot/autoconfigure_usb0.sh |4 ++--
1 file changed
Thanks Robert,
What I saw on the x86 was that eth1 was successfully brought up - all it
missed was an IP address. So ifconfig eth1 had MAC address etc, just no
address.
Thanks, Iain
On 1 July 2015 at 18:26, Robert Nelson robertcnel...@gmail.com wrote:
On Wed, Jul 1, 2015 at 12:09 PM, Robert
16 matches
Mail list logo
