WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Bluetooth PAN on rpi0W and piCore 9.0.3  (Read 8698 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14516
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #15 on: December 11, 2018, 09:20:00 PM »
Since it was only tested on an RPi3, the bluez extension was only posted to the piCore-9.x armv7 repo, but it should work on armv6?

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11178
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #16 on: December 11, 2018, 09:27:42 PM »
Hi Juanito
I thought it was the other way around. ARM7 is backward compatible with ARM6 so code compiled for ARM6 should run on ARM7.

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7183
    • My Community Forum
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #17 on: December 11, 2018, 09:33:46 PM »
Hm... Officially all RPi extensions expected to built for ARMv6 and same TCZ's available in v6/v7 repo.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14516
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #18 on: December 11, 2018, 09:41:43 PM »
The extension was built on an RPi3 using the piCore flags for armv6 - I think that at the time the bluetooth kernel modules extension did not exist in the armv6 repo, so the bluez extension was only posted in the armv7 repo.

Edit: There's also the issue of finding the appropriate equivalent to the armv7 firmware-rpi3-bt extension.
« Last Edit: December 11, 2018, 10:05:05 PM by Juanito »

Offline jwheeler91

  • Newbie
  • *
  • Posts: 2
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #19 on: December 12, 2018, 04:37:23 AM »
Ok thanks. I guess I might try just using raspian lite...

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 1063
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #20 on: December 13, 2018, 07:50:50 PM »
I've lost track of what is available on the piCore repos.  The firmware packages are quite old.  But the firmware is loading fine, according to the dmesg.

921600 noflow are not correct parameters for rpi0w.   /usr/local/bin/hciattach /dev/ttyAMA0 bcm43xx 3000000 flow - b8:27:eb:xx:xx:xx

Use the script that I posted earlier....that is how they do it on Raspbian too.   Also, make sure that you are not starting a serial console on ttyAMA0, as that would conflict with bluetooth.

AFAIK, the only extension related to bluetooth that doesn't run on a armv6 board is the sbc.tcz extension, that is related to bluetooth audio. I build all of the bluetooth packages, rebuilt upto bluez5.50
« Last Edit: December 13, 2018, 08:01:54 PM by Paul_123 »

Offline dcuser

  • Newbie
  • *
  • Posts: 1
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #21 on: January 12, 2019, 09:18:20 AM »
Hi.

I'm new to tinycore. Have been playing around with 9.0.3 for a few days and like it so far.

Trying to setup bluetooth on rpi0w and running into the same problem. raspbian lite works fine.  I was able to get it to work on rpi3 - followed the instructions above - however running into the same problems as other users with hciattach (with script) - Is there a way to get proper steps and packages for v6?

Questions if someone can help or provide working steps instead -
1. How does one install bluez.tcz without sbc.tcz [just modify dep file?]
2. The enable_uart in raspbian config is absent and so is the overlay [right set of parameters for rpi0w?]
3. Raspbian runtime shows /dev/serial1 as the device hciattach occurs on - docs here refer to ttyAMA0 [is it futile to try to match raspbian config? - raspbian kernel is newer]

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 1063
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #22 on: January 13, 2019, 08:39:38 AM »
Everything works for a zeroW,  the start script that works is the same used in raspbian, and is ousted up a few posts

Make sure you are not starting a serial console on the serial port, preventing Bluetooth from working.