Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: bmarkus on March 01, 2016, 12:44:57 AM
-
Hi,
looking for RPi3 testers. Let me know if you have a Raspberry Pi 3 board and willing to help in testing piCore.
Béla
-
Hand raised!
-
Hand raised!
Great, thanks! Do you have it already?
-
Yes, please count me in. I got my RPi3 this morning
http://goo.gl/SqColm
-
Hope Greg gets his Pi3 faster than he got his Zero..... lol
My zero should deliver today, and I just ordered a rpi3....looks like they have not quite arrived at the US warehouses yet.
-
Hand raised!
Great, thanks! Do you have it already?
Yes. I'm ready for testing.
-
Hope Greg gets his Pi3 faster than he got his Zero..... lol
My zero should deliver today, and I just ordered a rpi3....looks like they have not quite arrived at the US warehouses yet.
I ordered it on Monday night, picked it up on Tuesday.
I checked at the post office for the zero, and the result was zero. Lost in post!
-
Me too - arrived today!
-
Hi
New to these parts but have been playing a lot recently with an RPi2 and piCore - building a embedded network device based around the pi - Router / Captive Portal / VPN type thing.
Happy to assist and test on the RPi3 (mine has just arrived) - I will probably move over to the Pi3 hardware shortly anyway.
Cheers
Craig
-
i should have mine setup in a few days, too. you can count me in.
-
piCore 7.1beta1 base built on 4.1.18 kernel works fine on RPi1 and RPi2. Will make SD card image and few basic kernel module tcz's. It will be available for public testing in few days.
-
Hi Béla,
count with me too from today. It works well with piCore-7.0, very-little bit faster than RPi 2.
Guess that the first point will be to bring the build-in wifi working. Bluetooth is not important so far.
I have all the buses enabled, but didn't found how it is connected, It doesn't appear in the dmesg. Strange.
-
I've tested the Rasbian Jessie and the wifi and bluetooth are supported by the kernel itself.
It's exactly the same as for USB and LAN chip. No overlay needed.
-
jgrulich@
When I configured 4.1.18 kernel no any new WiFi or Bluetooth module appeared, so it must be already in earlier.
Canyou tell me which modules are used for them in Raspbian?
-
Hi Béla,
this is the lsmod:
pi@raspberrypi:~ $ lsmod
Module Size Used by
bnep 10336 2
hci_uart 13533 1
btbcm 4196 1 hci_uart
bluetooth 317981 22 bnep,btbcm,hci_uart
brcmfmac 177546 0
brcmutil 5501 1 brcmfmac
cfg80211 389253 1 brcmfmac
joydev 9024 0
evdev 10278 2
rfkill 16036 4 cfg80211,bluetooth
snd_bcm2835 19802 0
snd_pcm 73442 1 snd_bcm2835
snd_timer 18792 1 snd_pcm
bcm2835_rng 1763 0
bcm2835_gpiomem 2860 0
snd 50779 3 snd_bcm2835,snd_timer,snd_pcm
uio_pdrv_genirq 2944 0
uio 7753 1 uio_pdrv_genirq
ipv6 338574 34
and this is the part from dmesg:
[ 7.443747] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength init done for chip 43430 rev 1 pmurev 24
[ 7.444866] usbcore: registered new interface driver brcmfmac
[ 7.630579] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c
[ 7.653338] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 7.689981] bcm2835-rng 3f104000.rng: hwrng registered
[ 7.690112] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 7.690121] cfg80211: World regulatory domain updated:
[ 7.690130] cfg80211: DFS Master region: unset
[ 7.690131] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 7.690144] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 7.690151] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 7.690158] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 7.690181] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 7.690199] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 7.690207] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 7.690213] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 7.690220] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 8.260252] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[ 8.260280] brcmfmac: brcmf_add_if: ignore IF event
[ 8.995973] uart-pl011 3f201000.uart: no DMA platform data
[ 13.394610] Bluetooth: Core ver 2.20
[ 13.394690] NET: Registered protocol family 31
[ 13.394698] Bluetooth: HCI device and connection manager initialized
[ 13.395381] Bluetooth: HCI socket layer initialized
[ 13.395397] Bluetooth: L2CAP socket layer initialized
[ 13.395420] Bluetooth: SCO socket layer initialized
[ 13.401135] Bluetooth: HCI UART driver ver 2.3
[ 13.401146] Bluetooth: HCI UART protocol H4 registered
[ 13.401151] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 13.401156] Bluetooth: HCI UART protocol BCM registered
[ 13.580204] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.580216] Bluetooth: BNEP filters: protocol multicast
[ 13.580230] Bluetooth: BNEP socket layer initialized
-
Thanks. It looks OK, these modules are in the relevant TCZ extensions, must work. When it verified question is whether we want to add them to the base or keep in a TCZ.
-
piCore-7.1beta1 released, see http://forum.tinycorelinux.net/index.php/topic,19745.0.html
-
Bela
Still missing chars in cmdline.txt file.
_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/ram0 elevator=d
eadline rootwait quiet nortc loglevel=3 noembed
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/ram0 elevator=d
eadline rootwait quiet nortc loglevel=3 noembed
But i don't know if you have read my old post regarding this parameter, if needed or not.
But here are my old post.
http://forum.tinycorelinux.net/index.php/topic,19623.msg121927.html#msg121927
Thx a lot for building tiny core for raspberry pi.
//Patrik
-
patrikg@
you are right it is a typo in cmdline.txt, I will fix it in next upload. I do not want to switch back to USB 1.1 by default, let user do it when needed.
-
cmdline.txt fixed, new image uploaded.
-
Internal wifi is not working. Some issue with the firmware.
dmesg:
[ 6.739511] cfg80211: Calling CRDA to update world regulatory domain
[ 6.792722] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength init done for chip 43430 rev 1 pmurev 24
[ 6.793430] usbcore: registered new interface driver brcmfmac
[ 6.793549] brcmfmac_sdio mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2
[ 7.077639] uart-pl011 3f201000.uart: no DMA platform data
[ 7.079385] i2c /dev entries driver
[ 7.132078] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 7.799144] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 8.643876] random: nonblocking pool is initialized
[ 8.695523] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[ 8.809195] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 9.889147] cfg80211: Calling CRDA to update world regulatory domain
[ 13.039129] cfg80211: Calling CRDA to update world regulatory domain
[ 16.189127] cfg80211: Calling CRDA to update world regulatory domain
[ 19.339136] cfg80211: Calling CRDA to update world regulatory domain
[ 22.489146] cfg80211: Calling CRDA to update world regulatory domain
[ 25.639126] cfg80211: Calling CRDA to update world regulatory domain
[ 28.789129] cfg80211: Calling CRDA to update world regulatory domain
[ 31.939135] cfg80211: Calling CRDA to update world regulatory domain
[ 35.089130] cfg80211: Calling CRDA to update world regulatory domain
[ 38.239125] cfg80211: Calling CRDA to update world regulatory domain
[ 41.389126] cfg80211: Exceeded CRDA call max attempts. Not calling CRDA
lsmod:
tc@box:~$ lsmod
Module Size Used by Not tainted
i2c_dev 6020 0
brcmfmac 178877 0
brcmutil 5731 1 brcmfmac
cfg80211 421646 1 brcmfmac
rfkill 16625 1 cfg80211
evdev 10230 0
i2c_bcm2708 5002 0
spi_bcm2835 7252 0
bcm2835_gpiomem 3023 0
bcm2835_rng 1816 0
uio_pdrv_genirq 2966 0
uio 8340 1 uio_pdrv_genirq
-
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=138629&p=922898
-
Yes, the firmware is missing in the repo.
Please update the wireless kernel modules, or create the new firmware-brcmfmac.tcz
-
Yes, the firmware is missing in the repo.
Please update the wireless kernel modules, or create the new firmware-brcmfmac.tcz
Why update kernel modules?
I will create a firmware tcz as soon as someone send the firmware and confirms it works with RPi3. I can't test, no RPi3 in hand.
-
This is the working firmware:
https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm80211/brcm
and download the brcmfmac43430-sdio.bin and brcmfmac43430-sdio.txt files into the directory
/lib/firmware/brcm/
-
How about this
https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm80211/brcm
Sorry don't have rpi3.
-
Hi guys,
The on-board wifi seems to work OK. Thanks for the information.
Any chance of including the firmware for the "official" RPF USB wifi adaptor in the same extension?
tce.installed/firmware-brcmwifi is just copied from the other USB adpator firmware.
Here are my notes.
Files
-----
For Offical USB wifi adaptor:
/usr/local/tce.installed/firmware-brcmwifi
/lib/firmware/brcm/brcmfmac43143.bin
For wifi on-board RPi3:
/lib/firmware/brcm/brcmfmac43430-sdio.bin
/lib/firmware/brcm/brcmfmac43430-sdio.txt
download firmware-brcmwifi and brcmfmac43143.bin to home directory
download brcmfmac43430-sdio.bin and brcmfmac43430-sdio.txt to home directory
Instructions
------------
tce-load -w squashfs-tools.tcz
tce-load -i squashfs-tools.tcz
cd /tmp
mkdir -p brcm
cd brcm
mkdir -p usr/local/tce.installed/
mkdir -p lib/firmware/brcm/
cp ~/firmware-brcmwifi usr/local/tce.installed/
cp ~/brcmfmac43143.bin lib/firmware/brcm/
cp ~/brcmfmac43430-sdio.bin lib/firmware/brcm/
cp ~/brcmfmac43430-sdio.txt lib/firmware/brcm/
sudo -s
cd /tmp
mksquashfs brcm/ firmware-brcmwifi.tcz
regards
Greg
-
firmware-brcmfmac43430.tcz added to repo, please try.
-
Something went wrong and the files inside the tcz are not the correct ones.
Regs,
Jan
-
You are right, individual download from GitHub went wrong. Dowloaded the complete firmware as a zip archive is OK now.
Repo updated.
-
Did someone test the on-board Bluetooth?
-
LEDs are not working. There are no control folders ../soc/soc:leds/leds/led0 and led1.
I'm using this two lines in config.txt to switch the green LED off and red one for mmc activity.
dtparam=act_led_trigger=none
dtparam=pwr_led_trigger=mmc0
-
Did you try LED's on Raspbian?
-
OK, there is 4.1.19 upstream kernel. I will make piCore-7.0beta2
-
Don' be hurry Béla,
I've tested Rasbian 4.1.18 and latest 4.1.19 and both seems to work the same way. Strange is that there is ONLY one led0 control, means that the RED one can't be controlled, only the GREEN one can. The control capabilities are significantly extended, much more triggers are available.
-
Did someone test the on-board Bluetooth?
This statement appeared on one of the USA resellers web page
1. Bluetooth functionally is not available at launch. It will eventually be enabled by connecting your Pi to the internet and using the following
. It goes on with the normal firmware kernel update process
-
We have a RPi3 and would be very happy to test. Definitely not having any luck with 7.0.
-
Rasp Pi 3 here, I simply get the rainbow background when I try to run 7.0 and nothing happens at all.
-
Try the latest piCore here:
http://forum.tinycorelinux.net/index.php/topic,19784.0.html