All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11946] New: wilink-bt-firmware: moved from github to http://git.ti.com/ti-bt
Date: Thu, 06 Jun 2019 13:40:59 +0000	[thread overview]
Message-ID: <bug-11946-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=11946

            Bug ID: 11946
           Summary: wilink-bt-firmware: moved from github to
                    http://git.ti.com/ti-bt
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: mzweerspenko+bugzilla at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

On my compulab sbc iot i.mx7 gateway the ble doens't work with the old
firmware. There is a newer version on git://git.ti.com/ti-bt/service-packs.git

The path only changed a bit:
cp $(@D)/initscripts/TIInit_*.bts $(TARGET_DIR)/lib/firmware/ti-connectivity

I only have this hardware so ? cant test it any further that this.

<Addendum>
11.8.32 isn't a library version number but a hardware one.
bluez5_utils-5.50/tools/hciattach_ti.c:    sprintf(firmware_file_name,
FIRMWARE_DIRECTORY "TIInit_%d.%d.%d.bts", chip, maj_ver, min_ver);

<device log>

<<Current version from github>>
device# Found a Texas Instruments' chip!
Firmware file : /lib/firmware/ti-connectivity/TIInit_11.8.32.bts
Loaded BTS script version 1
texas: changing baud rate to 3000000, flow control to 1
Initialization timed out.

<< current version from git://git.ti.com/ti-bt/service-packs.git >>
device# Found a Texas Instruments' chip!
Firmware file : /lib/firmware/ti-connectivity/TIInit_11.8.32.bts
Loaded BTS script version 1
texas: changing baud rate to 3000000, flow control to 1
Device setup complete

device# blescan
Scanning for devices...
    Device (new): 03:FF:FF:3f:FF:38 (random), -87 dBm (not connectable)
    Device (new): 04:FF:2b:FF:a5:55 (random), -77 dBm (not connectable)
    Device (new): 0c:FF:90:FF:15:90 (random), -92 dBm (not connectable)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-06-06 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 13:40 bugzilla at busybox.net [this message]
2019-08-15 12:59 ` [Buildroot] [Bug 11946] wilink-bt-firmware: moved from github to http://git.ti.com/ti-bt bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-11946-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.