I got it working fine now:
hci0: Type: BR/EDR Bus: UART
BD Address: D0:B5:C2:F1:93:92 ACL MTU: 1021:6 SCO MTU: 180:4
RX bytes:587 acl:0 sco:0 events:28 errors:0
TX bytes:393 acl:0 sco:0 commands:28 errors:0
root@fx30:/legato/apps/32659631a8e706044673ab6fa0ce52b4/read-only/bin# ./hcitool lescan
LE Scan ...
70:B3:D5:19:9D:AD 70:B3:D5:19:9D:AD 1
The TI file is out of date for the IoT card, what fixed it was getting an updated firmware driver and replacing the one in the demo app. That’s all that was needed. It’s very important to get the right firmware driver for your bluetooth device.
One thing I’d still like some help with is, I want to develop a legato app that can call on the hci & rfcomm api, instead of running the hci tools on the command line, but the build_bluex_util scripts don’t produce any libraries that I can see - there are .lo and .la files for bluetooth but not a .so dynamic library. How would I go about producing a dynamic library that I can use in my legato application ?
update - actually I can see a libbluetooth-internal.a and a libbluetooth.so.x.x.x file after enabling build library support, but if I include them in a ldflags section of a cdef I still get build errors resolving hci_ api calls )…ahh it’s ok, figured it out…