WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

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

Offline gjm

  • WikiUser
  • *
  • Posts: 7
Bluetooth PAN on rpi0W and piCore 9.0.3
« on: May 24, 2018, 11:54:53 AM »
Hi all,

I've been trying to setup Bluetooth on a rpi0W following various posts on here, but all seem to relate either to piCore 8.x.x and/or rpi3 so I'm really struggling to get it all working as I can't. 

Ultimately I'd like to be able to set up the rpi0W as a PAN (either GN or NAP) so that clients can access HTML files from an HTTPD running on the rpi0W but would be happy just to get the Bluetooth working in any capacity.

Device: rpi0W
OS: piCore 9.0.3

Other forum threads talk about tce firmware-rpi3-bt and bluez but I can't find anything in the TCZ's other than bluetooth-4.9.22-piCore.

Any help gratefully received.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 10704
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #1 on: May 24, 2018, 11:00:00 PM »
there's a bluez extension in the piCore 9.x armv7 repo - this might also work for armv6?

Offline gjm

  • WikiUser
  • *
  • Posts: 7
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #2 on: May 25, 2018, 03:41:04 AM »
Hi and many thanks for your reply.

I've taken your advice and installed the ARM7 version of BlueZ.  tce-load -i bluez returns an OK so I assume that's all good.

In one of your threads (http://forum.tinycorelinux.net/index.php/topic,20854.msg133929.html#msg133929) I follow your instructions as far as the dmesg command which completes as per your example but when I move onto the next part running dbus start I get an error "not found".  The same for trying to run bluetoothd -nd... "not found"

I'm obviously missing something here but not sure what exactly?

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 10704
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #3 on: May 25, 2018, 04:55:58 AM »
Does the following show that dbus is loaded:
Code: [Select]
$ tce-status -i | grep dbus

Offline gjm

  • WikiUser
  • *
  • Posts: 7
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #4 on: May 25, 2018, 05:42:49 AM »
It responds with
Code: [Select]
tc@box:/mnt/mmcblk0p2/tce/optional$ tce-status -i | grep dbus
dbus
dbus-dev
dbus-glib

    [EDIT]: Replaced  tt  tags with  code  tags.  Rich
« Last Edit: May 25, 2018, 06:11:48 AM by Rich »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 10704
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #5 on: May 25, 2018, 05:53:01 AM »
..and this doesn't work:
Code: [Select]
$ sudo /usr/local/etc/init.d/dbus start
$ ps aux | grep dbus

Offline gjm

  • WikiUser
  • *
  • Posts: 7
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #6 on: May 25, 2018, 05:58:59 AM »
.... and that gives

Code: [Select]
tc@box:/mnt/mmcblk0p2/tce/optional$ sudo /usr/local/etc/init.d/dbus start
tc@box:/mnt/mmcblk0p2/tce/optional$ ps aux | grep dbus
 1620 tc       /usr/local/bin/dbus-daemon --system
 1622 tc       grep dbus

 dbus  didn't work previously and the only thing I've done since it didn't work is install BlueZ!

    [EDIT]: Replaced  tt  tags with  code  tags.  Rich
« Last Edit: May 25, 2018, 06:13:25 AM by Rich »

Offline gjm

  • WikiUser
  • *
  • Posts: 7
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #7 on: May 25, 2018, 06:08:43 AM »
If i then continue with your instructions and issue  sudo /usr/local/lib/bluetooth/bluetoothd -nd  I get

Code: [Select]
tc@box:/mnt/mmcblk0p2/tce/optional$ sudo /usr/local/lib/bluetooth/bluetoothd -nd
bluetoothd[1623]: Bluetooth daemon 5.43
bluetoothd[1623]: src/main.c:parse_config() parsing main.conf
bluetoothd[1623]: src/main.c:parse_config() Key file does not have key “DiscoverableTimeout” in group “General”
bluetoothd[1623]: src/main.c:parse_config() Key file does not have key “PairableTimeout” in group “General”
bluetoothd[1623]: src/main.c:parse_config() Key file does not have key “AutoConnectTimeout” in group “General”
bluetoothd[1623]: src/main.c:parse_config() Key file does not have key “Privacy” in group “General”
bluetoothd[1623]: src/main.c:parse_config() name=Rpi
bluetoothd[1623]: src/main.c:parse_config() Key file does not have key “Class” in group “General”
bluetoothd[1623]: src/main.c:parse_config() Key file does not have key “DeviceID” in group “General”
bluetoothd[1623]: src/main.c:parse_config() Key file does not have key “ReverseServiceDiscovery” in group “General”
bluetoothd[1623]: src/adapter.c:adapter_init() sending read version command
bluetoothd[1623]: Starting SDP server
bluetoothd[1623]: src/sdpd-service.c:register_device_id() Adding device id record for 0002:1d6b:0246:052b
bluetoothd[1623]: src/plugin.c:plugin_init() Loading builtin plugins
bluetoothd[1623]: src/plugin.c:add_plugin() Loading hostname plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading wiimote plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading autopair plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading policy plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading a2dp plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading avrcp plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading network plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading input plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading hog plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading gap plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading scanparam plugin
bluetoothd[1623]: src/plugin.c:add_plugin() Loading deviceinfo plugin
bluetoothd[1623]: src/plugin.c:plugin_init() Loading plugins /usr/local/lib/bluetooth/plugins
bluetoothd[1623]: profiles/input/suspend-none.c:suspend_init()
bluetoothd[1623]: profiles/network/manager.c:read_config() /usr/local/etc/bluetooth/network.conf: Key file does not have key “DisableSecurity” in group “General”
bluetoothd[1623]: profiles/network/manager.c:read_config() Config options: Security=true
bluetoothd[1623]: src/main.c:main() Entering main loop
bluetoothd[1623]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 0 soft 0 hard 0
bluetoothd[1623]: Bluetooth management interface 1.14 initialized
bluetoothd[1623]: src/adapter.c:read_version_complete() sending read supported commands command
bluetoothd[1623]: src/adapter.c:read_version_complete() sending read index list command
bluetoothd[1623]: src/adapter.c:read_commands_complete() Number of commands: 65
bluetoothd[1623]: src/adapter.c:read_commands_complete() Number of events: 35
bluetoothd[1623]: src/adapter.c:read_commands_complete() enabling kernel-side connection control
bluetoothd[1623]: src/adapter.c:read_index_list_complete() Number of controllers: 0

If I open up a separate terminal window and issue
Code: [Select]
hciattach /dev/ttyAMA0 bcm43xx 921600 noflowI get:
Code: [Select]
bcm43xx_init
Failed to reset chip, invalid HCI event
Can't initialize device: Success

Back in the original terminal window nothing happens until several minutes have elapsed and then I get

Code: [Select]
bluetoothd[1623]: Terminating
bluetoothd[1623]: src/adapter.c:adapter_shutdown()
bluetoothd[1623]: src/plugin.c:plugin_cleanup() Cleanup plugins
bluetoothd[1623]: profiles/input/suspend-none.c:suspend_exit()
bluetoothd[1623]: Stopping SDP server
bluetoothd[1623]: Exit

    [EDIT]: Replaced  tt  tags with  code  tags.  Rich
« Last Edit: May 25, 2018, 06:31:20 AM by Rich »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 10704
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #8 on: May 25, 2018, 06:35:17 AM »
My guideline was for an RPi3 - I guess an RPi0w must require slightly different commands, but I don't have one to play with..

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6426
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #9 on: May 25, 2018, 06:40:25 AM »
Hi gjm
....  dbus  didn't work previously and the only thing I've done since it didn't work is install BlueZ!

I'm guessing you probably didn't install  dbus  previously. Installing  bluez  resulted in  dbus  being installed since it's a
dependency of  bluez.

Instead of using  tt  tags please use  code  tags. This will still preserve spacing as it too uses a monotype font in addition to
adding scroll bars for longer printouts.

Offline gjm

  • WikiUser
  • *
  • Posts: 7
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #10 on: May 25, 2018, 06:46:57 AM »
Thanks for you help Juanito, I think I'm going to go back to my base image and start afresh to see if that yields different results probably due to the install order and dependencies etc.  I will post back my findings here regardless.  Thanks again.

Rich:  Yes, sorry about the incorrect tags, point noted and taken on board for future. ;-)  And yes I think you're right about the dependencies, hence going back and starting from scratch in what, hopefully, will be the correct order.  Watch this space.

Offline Paul_123

  • Sr. Member
  • ****
  • Posts: 463
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #11 on: June 08, 2018, 04:35:16 PM »
The ZeroW is definitely a slightly different setup than a pi3.   But the default dbus.tcz works fine, at least for audio setup.  I've not done networking.

You need to grab this firmware from the armv7 repo   http://distro.ibiblio.org/tinycorelinux/9.x/armv7/tcz/firmware-rpi3-bt.tcz   This is a dependency of bluetooth-4.9.22-piCore.tcz.

Make sure you are setting up hciattach like this post.   http://forum.tinycorelinux.net/index.php/topic,20854.msg133929.html#msg133929  You will also need to load the kernel module hci_uart before running hciattach.  After hciattach has loaded the firmware and started, then you can start bluze/dbus by running /usr/local/etc/init.d/bluez start

What I cannot remember is if bluez 5.43 works with the rpi 0W.  I am using bluez 5.48 on my setups.

Note:
The sbc.tcz extension on the armv7 repo is definitely not compatible with the rpi0W, but if your are not trying to use Bluez-Alsa for audio, you should be fine.
« Last Edit: June 08, 2018, 04:39:32 PM by Paul_123 »

Offline milo77

  • WikiUser
  • *
  • Posts: 1
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #12 on: July 08, 2018, 05:19:30 PM »
Hi Paul_123,

I was wondering if you could share your setup for the RPi Zero W. I am currently struggling in enabling bluetooth.

I have currently tried those:
$ tce-load -i bluez.tcz dbus.tcz firmware-rpi3-bt.tcz libudev.tcz sbc.tcz bluetooth-4.9.22-piCore.tcz
$ sudo modprobe hci_uart

But then:
$ sudo hciattach /dev/ttyAMA0 bcm43xx 3000000 flow
Gives:
bcm43xx_init
Failed to reset chip, invalid HCI event
Can't initialize device: Success

If I try for second time I get:
Bluetooth Hardware Address:b8:27:eb:4c:9a:6d
bcm43xx_init
Initialization timed out.

Thank you!



Offline Paul_123

  • Sr. Member
  • ****
  • Posts: 463
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #13 on: July 08, 2018, 07:30:04 PM »
First, make sure that you have not disabled bluetooth in your boot config.txt

Then this is the official way of starting hciattach for all of the rpi variants.

Code: [Select]
sudo modprobe hci_uart
HCIATTACH=/usr/local/bin/hciattach
SERIAL=`grep Serial /proc/cpuinfo | cut -c19-`
B1=`echo $SERIAL | cut -c3-4`
B2=`echo $SERIAL | cut -c5-6`
B3=`echo $SERIAL | cut -c7-8`
BDADDR=`printf b8:27:eb:%02x:%02x:%02x $((0x$B1 ^ 0xaa)) $((0x$B2 ^ 0xaa)) $((0x$B3 ^ 0xaa))`

# Rpi3 Serial port
SERIAL_DEV="/dev/ttyAMA0"

if [ "$(cat /proc/device-tree/aliases/uart0)" = "$(cat /proc/device-tree/aliases/serial1)" ] ; then
if [ "$(wc -c /proc/device-tree/soc/gpio@7e200000/uart0_pins/brcm\,pins | cut -f 1 -d ' ')" = "16" ] ; then
$HCIATTACH $SERIAL_DEV bcm43xx 3000000 flow - $BDADDR
else
$HCIATTACH $SERIAL_DEV bcm43xx 921600 noflow - $BDADDR
fi
else
$HCIATTACH $SERIAL_DEV bcm43xx 460800 noflow - $BDADDR
fi

If that fails, take a look at dmesg for any clues.

Offline jwheeler91

  • WikiUser
  • *
  • Posts: 2
Re: Bluetooth PAN on rpi0W and piCore 9.0.3
« Reply #14 on: December 11, 2018, 09:29:48 AM »
I am struggling with the same issue on my Pi0W. First time running the hci attach script (which always runs 921600 noflow), it always fails. Then following attempts timeout:

Code: newbielink:javascript:void(0); [nonactive]
Bluetooth Hardware Address:b8:27:eb:44:60:5d
bcm43xx_init
Failed to reset chip, invalid HCI event
Can't initialize device: Success

Code: newbielink:javascript:void(0); [nonactive]
Bluetooth Hardware Address:b8:27:eb:44:60:5d
bcm43xx_init
Initialization timed out.

I've pulled the tczs for bluez and the firmware from the v7 repo, but everything else came from the v6 repo.

My dmesg output is the following:
Code: newbielink:javascript:void(0); [nonactive]
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.22-piCore (root@box) (gcc version 6.3.0 (piCore) ) #1 Sat Apr 15 15:30:03 UTC 2017
[    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] OF: fdt:Machine model: Raspberry Pi Zero W Rev 1.1
[    0.000000] cma: Reserved 8 MiB at 0x1b000000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 114688
[    0.000000] free_area_init_node: node 0, pgdat c0931188, node_mem_map dac10000
[    0.000000]   Normal zone: 1008 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 114688 pages, LIFO batch:31
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 113680
[    0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:EE:CA:F7 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=115200 root=/dev/ram0 elevator=deadline rootwait quiet nortc loglevel=3 noembed waitusb=1
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 431360K/458752K available (6035K kernel code, 492K rwdata, 1968K rodata, 400K init, 739K bss, 19200K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xdc800000 - 0xff800000   ( 560 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdc000000   ( 448 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc05ecef4   (6036 kB)
[    0.000000]       .init : 0xc085c000 - 0xc08c0000   ( 400 kB)
[    0.000000]       .data : 0xc08c0000 - 0xc093b038   ( 493 kB)
[    0.000000]        .bss : 0xc093b038 - 0xc09f3e60   ( 740 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000028] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
[    0.000059] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
[    0.000149] bcm2835: system timer (irq = 27)
[    0.000594] Console: colour dummy device 80x30
[    0.000632] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
[    0.060288] pid_max: default: 32768 minimum: 301
[    0.060705] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.060720] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.061777] Disabling cpuset control group subsystem
[    0.061975] CPU: Testing write buffer coherency: ok
[    0.062033] ftrace: allocating 21825 entries in 65 pages
[    0.180417] Setting up static identity map for 0x8200 - 0x8238
[    0.182408] devtmpfs: initialized
[    0.191489] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[    0.191911] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.191936] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.193215] pinctrl core: initialized pinctrl subsystem
[    0.194638] NET: Registered protocol family 16
[    0.197228] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.207189] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[    0.207204] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.207309] Serial: AMBA PL011 UART driver
[    0.210170] bcm2835-mbox 2000b880.mailbox: mailbox enabled
[    0.210910] uart-pl011 20201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.211858] irq: no irq domain found for /soc/aux@0x7e215000 !
[    0.259445] bcm2835-dma 20007000.dma: DMA legacy API manager at dc80d000, dmachans=0x1
[    0.262248] SCSI subsystem initialized
[    0.262515] usbcore: registered new interface driver usbfs
[    0.262626] usbcore: registered new interface driver hub
[    0.262813] usbcore: registered new device driver usb
[    0.270472] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-04-04 18:41
[    0.272376] clocksource: Switched to clocksource timer
[    0.326874] VFS: Disk quotas dquot_6.6.0
[    0.326992] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.327284] FS-Cache: Loaded
[    0.327635] CacheFiles: Loaded
[    0.347186] NET: Registered protocol family 2
[    0.348527] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.348612] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.348683] TCP: Hash tables configured (established 4096 bind 4096)
[    0.348780] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.348805] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.349095] NET: Registered protocol family 1
[    0.349832] RPC: Registered named UNIX socket transport module.
[    0.349842] RPC: Registered udp transport module.
[    0.349847] RPC: Registered tcp transport module.
[    0.349852] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.350304] Trying to unpack rootfs image as initramfs...
[    0.994491] Freeing initrd memory: 4464K (dbb94000 - dbff0000)
[    1.026391] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
[    1.028741] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[    1.045138] zbud: loaded
[    1.049300] FS-Cache: Netfs 'nfs' registered for caching
[    1.051013] NFS: Registering the id_resolver key type
[    1.051058] Key type id_resolver registered
[    1.051064] Key type id_legacy registered
[    1.060530] jitterentropy: Initialization failed with host not compliant with requirements: 2
[    1.060702] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    1.061077] io scheduler noop registered
[    1.061090] io scheduler deadline registered (default)
[    1.061556] io scheduler cfq registered
[    1.067868] BCM2708FB: allocated DMA memory 5b100000
[    1.067927] BCM2708FB: allocated DMA channel 0 @ dc80d000
[    1.075606] Console: switching to colour frame buffer device 82x26
[    1.081312] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    1.082315] bcm2835-aux-uart 20215040.serial: could not get clk: -517
[    1.084115] bcm2835-rng 20104000.rng: hwrng registered
[    1.084286] vc-cma: Videocore CMA driver
[    1.084295] vc-cma: vc_cma_base      = 0x00000000
[    1.084303] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    1.084308] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    1.084678] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
[    1.110096] brd: module loaded
[    1.122627] loop: module loaded
[    1.122649] Loading iSCSI transport class v2.0-870.
[    1.123641] usbcore: registered new interface driver smsc95xx
[    1.123668] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.349862] Core Release: 2.80a
[    1.349878] Setting default values for core params
[    1.349912] Finished setting default values for core params
[    1.550289] Using Buffer DMA mode
[    1.550301] Periodic Transfer Interrupt Enhancement - disabled
[    1.550308] Multiprocessor Interrupt Enhancement - disabled
[    1.550317] OTG VER PARAM: 0, OTG VER FLAG: 0
[    1.550404] Dedicated Tx FIFOs mode
[    1.551058] WARN::dwc_otg_hcd_init:1053: FIQ DMA bounce buffers: virt = 0xdb114000 dma = 0x5b114000 len=9024
[    1.551086] FIQ FSM acceleration enabled for :
[    1.551086] Non-periodic Split Transactions
[    1.551086] Periodic Split Transactions
[    1.551086] High-Speed Isochronous Endpoints
[    1.551086] Interrupt/Control Split Transaction hack enabled
[    1.551096] dwc_otg: Microframe scheduler enabled
[    1.551182] WARN::hcd_init_fiq:459: FIQ on core 0 at 0xc0466f8c
[    1.551194] WARN::hcd_init_fiq:460: FIQ ASM at 0xc0467268 length 36
[    1.551220] WARN::hcd_init_fiq:486: MPHI regs_base at 0xdc8a5000
[    1.551292] dwc_otg 20980000.usb: DWC OTG Controller
[    1.551355] dwc_otg 20980000.usb: new USB bus registered, assigned bus number 1
[    1.551441] dwc_otg 20980000.usb: irq 56, io mem 0x00000000
[    1.551495] Init: Port Power? op_state=1
[    1.551500] Init: Power Port (0)
[    1.551912] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.551927] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.551937] usb usb1: Product: DWC OTG Controller
[    1.551945] usb usb1: Manufacturer: Linux 4.9.22-piCore dwc_otg_hcd
[    1.551954] usb usb1: SerialNumber: 20980000.usb
[    1.553221] hub 1-0:1.0: USB hub found
[    1.553314] hub 1-0:1.0: 1 port detected
[    1.554227] dwc_otg: FIQ enabled
[    1.554236] dwc_otg: NAK holdoff enabled
[    1.554241] dwc_otg: FIQ split-transaction FSM enabled
[    1.554263] Module dwc_common_port init
[    1.554761] usbcore: registered new interface driver usb-storage
[    1.555233] mousedev: PS/2 mouse device common for all mice
[    1.556928] bcm2835-wdt 20100000.watchdog: Broadcom BCM2835 watchdog timer
[    1.557407] bcm2835-cpufreq: min=700000 max=1000000
[    1.558784] sdhci: Secure Digital Host Controller Interface driver
[    1.558792] sdhci: Copyright(c) Pierre Ossman
[    1.559178] sdhost-bcm2835 20202000.sdhost: could not get clk, deferring probe
[    1.561507] mmc-bcm2835 20300000.mmc: could not get clk, deferring probe
[    1.561648] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.562078] ledtrig-cpu: registered to indicate activity on CPUs
[    1.562216] hidraw: raw HID events driver (C) Jiri Kosina
[    1.562554] usbcore: registered new interface driver usbhid
[    1.562560] usbhid: USB HID core driver
[    1.563655] vchiq: vchiq_init_state: slot_zero = 0xdb180000, is_master = 0
[    1.566094] Initializing XFRM netlink socket
[    1.566144] NET: Registered protocol family 17
[    1.566295] Key type dns_resolver registered
[    1.568201] registered taskstats version 1
[    1.568381] zswap: loaded using pool lzo/zbud
[    1.661322] Key type encrypted registered
[    1.661644] vc-sm: Videocore shared memory driver
[    1.661659] [vc_sm_connected_init]: start
[    1.663010] [vc_sm_connected_init]: end - returning 0
[    1.670242] 20201000.serial: ttyAMA0 at MMIO 0x20201000 (irq = 81, base_baud = 0) is a PL011 rev2
[    1.672246] console [ttyS0] disabled
[    1.672294] 20215040.serial: ttyS0 at MMIO 0x0 (irq = 214, base_baud = 31250000) is a 16550
[    1.673422] sdhost: log_buf @ db113000 (5b113000)
[    1.752442] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    1.754865] mmc-bcm2835 20300000.mmc: mmc_debug:0 mmc_debug2:0
[    1.754878] mmc-bcm2835 20300000.mmc: DMA channel allocated
[    1.778018] random: fast init done
[    1.819767] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.821857] mmc0: new high speed SDHC card at address 1234
[    1.822842] mmcblk0: mmc0:1234 SA08G 7.21 GiB
[    1.824984]  mmcblk0: p1 p2
[    1.832631] of_cfs_init
[    1.832739] of_cfs_init: OK
[    1.833191] Warning: unable to open an initial console.
[    1.834253] Freeing unused kernel memory: 400K (c085c000 - c08c0000)
[    1.834259] This architecture does not have kernel memory protection.
[    1.859625] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.861401] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.863214] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.866534] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.983335] mmc1: new high speed SDIO card at address 0001
[    3.794873] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
[    4.276693] zram: Added device: zram0
[    4.330975] zram0: detected capacity change from 0 to 106201088
[    4.357899] Adding 103708k swap on /dev/zram0.  Priority:-1 extents:1 across:103708k SSFS
[    4.665057] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    5.946018] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    6.109473] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[   17.378517] usbcore: registered new interface driver brcmfmac
[   17.593617] brcmfmac: Firmware version = wl0: Aug  7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[   18.430153] i2c /dev entries driver
[   18.563514] uart-pl011 20201000.serial: no DMA platform data
[   20.546415] brcmfmac: power management disabled
[   47.139328] Bluetooth: Core ver 2.22
[   47.139541] NET: Registered protocol family 31
[   47.139551] Bluetooth: HCI device and connection manager initialized
[   47.139581] Bluetooth: HCI socket layer initialized
[   47.139602] Bluetooth: L2CAP socket layer initialized
[   47.139658] Bluetooth: SCO socket layer initialized
[   47.150172] Bluetooth: HCI UART driver ver 2.3
[   47.150190] Bluetooth: HCI UART protocol H4 registered
[   47.150196] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   47.150458] Bluetooth: HCI UART protocol Broadcom registered
[   47.593643] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   47.593655] Bluetooth: BNEP filters: protocol multicast
[   47.593687] Bluetooth: BNEP socket layer initialized
[  461.522470] random: crng init done