The Raspberry Pi 3 Model B Q&A thread

[fruitoftheloom]

...
Raspbian Jessie compatible with an update / upgrade as above..

Raspbian Wheezy not compatible...

Actually, it's sort of compatible

I'm trying to work out why my vga666 display is a no-show on this RPi3 Jessie.
So, I've booted from my most recent (updated) "bouncing-menu" wheezy µSD card.


[email protected] ~ $ cat /etc/os-release

PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)"
NAME="Raspbian GNU/Linux"
VERSION_ID="7"
VERSION="7 (wheezy)"
ID=raspbian
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
[email protected] ~ $

I was just repeating what someone else wrote

viewtopic.php?f=91&t=138149#p917071

[fourdee4d]

I feel like an idiot for asking this question, but here goes:

How do we enable the onboard Wifi?

Is it a module we need to enable?

Code: Select all

[email protected]:~# lsmod
Module                  Size  Used by
brcmfmac              177546  0
brcmutil                5501  1 brcmfmac
cfg80211              389253  1 brcmfmac
rfkill                 16036  1 cfg80211
sg                     18023  0
bcm2835_gpiomem         2860  0
bcm2835_rng             1763  0
uio_pdrv_genirq         2944  0
uio                     7753  1 uio_pdrv_genirq
snd_bcm2835            19802  0
snd_pcm                73442  1 snd_bcm2835
snd_timer              18792  1 snd_pcm
snd                    50779  3 snd_bcm2835,snd_timer,snd_pcm
fuse                   80694  1
ipv6                  338574  20

Code: Select all

[email protected]:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr b8:27:eb:8e:53:5b
          inet addr:192.168.0.104  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::ba27:ebff:fe8e:535b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:613 errors:0 dropped:0 overruns:0 frame:0
          TX packets:177 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:43129 (42.1 KiB)  TX bytes:28252 (27.5 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Doesnt seem to run through USB bus:

Code: Select all

[email protected]:~# lsusb
Bus 001 Device 004: ID 0781:5583 SanDisk Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Can we control it in config.txt?

I cant find any documentation anywhere regarding wifi/bluetooth enable/control.

[fruitoftheloom]

I feel like an idiot for asking this question, but here goes:

How do we enable the onboard Wifi?

Is it a module we need to enable?

Code: Select all

[email protected]:~# lsmod
Module                  Size  Used by
brcmfmac              177546  0
brcmutil                5501  1 brcmfmac
cfg80211              389253  1 brcmfmac
rfkill                 16036  1 cfg80211
sg                     18023  0
bcm2835_gpiomem         2860  0
bcm2835_rng             1763  0
uio_pdrv_genirq         2944  0
uio                     7753  1 uio_pdrv_genirq
snd_bcm2835            19802  0
snd_pcm                73442  1 snd_bcm2835
snd_timer              18792  1 snd_pcm
snd                    50779  3 snd_bcm2835,snd_timer,snd_pcm
fuse                   80694  1
ipv6                  338574  20

Code: Select all

[email protected]:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr b8:27:eb:8e:53:5b
          inet addr:192.168.0.104  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::ba27:ebff:fe8e:535b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:613 errors:0 dropped:0 overruns:0 frame:0
          TX packets:177 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:43129 (42.1 KiB)  TX bytes:28252 (27.5 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Doesnt seem to run through USB bus:

Code: Select all

[email protected]:~# lsusb
Bus 001 Device 004: ID 0781:5583 SanDisk Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Can we control it in config.txt?

I cant find any documentation anywhere regarding wifi/bluetooth enable/control.

If you have a fully updated Operating System it is enabled by default

You will not find on USB BUS as both WiFi and Bluetooth are connected to GPIO

[Kratos]

The problem with those measurements is that they don't measure instantaneous peak power consumption which is extremely important. When your processor kicks off to do something important it can easily triple the power consumption for a few micro seconds. You'll not notice this on a DVM...

Thanks for this Gordon. I will put a comment on the blog next time I update it in a day or two. The main reason I do these measurements is so that people using battery power can calculate their required capacity.

I to found your power measurements very helpful. Please update your power chats to include the Raspberry Pi 3.

Kratos

[Kratos]

I have some questions about the Raspberry Pi 3:


6. How is YouTube performance?

Thanks for the help.
Kratos

Youtube performance is better than in rpi2 , https://goo.gl/yK5uBt

Thank you for taking the time to do this!

Kratos

[l_k3]

The Raspberry Pi camera module does not work with the Raspberry Pi3.
I connected the camera module to the CSI port and tried to use
raspistill to make a picture. It seems that the Pi3 camera (software/driver?)
is not able to find the camera module.

raspistill says:

mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)
mmal: mmal_component_create_core: could not create component 'vc.ril.camera' (1)
mmal: Failed to create camera component
mmal: main: Failed to create camera component
mmal: Camera is not detected. Please check carefully the camera module is installed correctly

The camera module is activated by raspi-config. I double checked the connections and
already tried a new camera module. Both modules work with the Pi2.

Can someone confirm that? Any suggestions?

Thanks
Mario

[richardski]

Farnell did well as RPi 3B ordered at 0830 Hrs on the 29th Feb and arrived 1500 Hrs on the 1st Feb.

Fresh install of NOOBS 1.8.0 with all updates shows up as:

uname -a
[email protected]:~ $ uname -a
Linux raspberrypi 4.1.18-v7+ #848 SMP Mon Feb 29 14:19:45 GMT 2016 armv7l GNU/Linux

cat /proc/version
[email protected]:~ $ cat /proc/version
Linux version 4.1.18-v7+ ([email protected]) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #848 SMP Mon Feb 29 14:19:45 GMT 2016

However the CPU info is at odds with chip info:

cat /proc/cpuinfo
[email protected]:~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture : 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

Hardware : BCM2709
Revision : a02082
Serial : 00000000d2cd3426


lscpu
[email protected]:~ $ lscpu
Architecture: armv7l
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Model name: ARMv7 Processor rev 4 (v7l)
CPU max MHz: 1200.0000
CPU min MHz: 600.0000

Which is an interesting result:)

Richard

[gregeric]

I feel like an idiot for asking this question, but here goes:

How do we enable the onboard Wifi?

Is it a module we need to enable?

Code: Select all

[email protected]:~# lsmod
Module                  Size  Used by
brcmfmac              177546  0
brcmutil                5501  1 brcmfmac
cfg80211              389253  1 brcmfmac
rfkill                 16036  1 cfg80211
sg                     18023  0
bcm2835_gpiomem         2860  0
bcm2835_rng             1763  0
uio_pdrv_genirq         2944  0
uio                     7753  1 uio_pdrv_genirq
snd_bcm2835            19802  0
snd_pcm                73442  1 snd_bcm2835
snd_timer              18792  1 snd_pcm
snd                    50779  3 snd_bcm2835,snd_timer,snd_pcm
fuse                   80694  1
ipv6                  338574  20

Doesnt seem to run through USB bus:

Code: Select all

[email protected]:~# lsusb
Bus 001 Device 004: ID 0781:5583 SanDisk Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Can we control it in config.txt?

I cant find any documentation anywhere regarding wifi/bluetooth enable/control.

What is it you are running, DietPi, not the latest Raspbian Jessie image?

All the same, the driver seems to be loaded, witness the brcmfmac module etc in lsmod.

There is no lssdio equivalent of lsusb. Instead, you can

Code: Select all

sudo cat /sys/kernel/debug/mmc1/ios

to see how the sdio bus is configured.

And

Code: Select all

ls -R /sys/bus/sdio

to see what devices are hanging off it.

[gregeric]

I'm very interested in what the GPIOs are used for.
Is there a chance we get a list to see what has changed regarding B+ B2 ?
Especially for the BT/WIFI

Full Pi 3 pin-mapping can be seen in bcm2710-rpi-3-b.dts over here: https://github.com/raspberrypi/linux/co ... 3bd3fa48b7

Thanks a lot !
Unfortunately there is no information about the GPIOs for cam, lan9514 reset,clock and usb-current-limit.
What I got from the dts:

BT: uses GPIO 28-31 for PCM, 32-33 for UART0 and 43 as clock.
Wifi: uses GPIO 34-39 for SDIO

So only GPIO 40,41,42,44,45 is left. Assuming that:
Audio is on GPIO 40,45
Cam-GPIOs on 41,42
and that clock on GPIO 43 is also for the lan9514
there is only GPIO 44 left for either lan9514 reset or for the usb current-limit.
So I guess there is no longer a ethernet reset and the power-led and brownout detection have gone.

Feeding an under-voltage into the Pi3 I'm gettting a constant flashing power LED, no rainbow square, apparently confirming no gpio to spare for the B+/Pi2 signalling scheme, all done in discrete logic?

Looks like they have wrung every feature out of the onboard peripherals with the Pi3, not a single GPIO to spare.

[ChristianRodz]

Sombody knows if it is possible to run a 2.5 external HDD in the new Raspberry Pi 3 from the box or we need to change /boot/config.txt and add max_usb_current=1?? Or maybe if is not possible we need to buy an external usb hub?

[tvjon]

The Raspberry Pi camera module does not work with the Raspberry Pi3.
....
Can someone confirm that? Any suggestions?

Thanks
Mario

Camera works just fine.

Have you enabled it via

raspi-config?

[ukscone]

Sombody knows if it is possible to run a 2.5 external HDD in the new Raspberry Pi 3 from the box or we need to change /boot/config.txt and add max_usb_current=1?? Or maybe if is not possible we need to buy an external usb hub?

I don't know about an off the shelf setup but i've been using a pidrive cable and harddisk on my Pi3 for almost 3 weeks with no problems.

http://store.wdc.com/store/wdus/en_US/l ... WD_PiDrive

and there might still be a discount of 20 to 30 percent available
https://community.wd.com/t/wd-pidrive-c ... ely/136693

[fruit-uk]

Farnell did well as RPi 3B ordered at 0830 Hrs on the 29th Feb and arrived 1500 Hrs on the 1st Feb.

Incredibly well looking at those dates

[fruitoftheloom]

Sombody knows if it is possible to run a 2.5 external HDD in the new Raspberry Pi 3 from the box or we need to change /boot/config.txt and add max_usb_current=1?? Or maybe if is not possible we need to buy an external usb hub?

I was under the impressionn that max_current was no longer needed as it now defaults to 1200Ma on the USB ?

That is why a 5V2.5A is recommended !

[gregeric]

I was under the impressionn that max_current was no longer needed as it now defaults to 1200Ma on the USB ?

The FET which was used to switch in a parallel resistor so as to lower the value of the 2553's R_LIM is gone, so yes, total USB peripheral current draw is hard-wired to a nominal 1200mA (*) trip level.

Edit: (*) I haven't measure the R_LIM to see if it's other than the old 19.5kOhm value which set 1200.

Edit2: R50 measured as 19.65kOhm on mine, so the same nominal 1200mA trip level.

[fruitoftheloom]

I was under the impressionn that max_current was no longer needed as it now defaults to 1200Ma on the USB ?

The FET which was used to switch in a parallel resistor so as to lower the value of the 2553's R_LIM is gone, so yes, total USB peripheral current draw is hard-wired to a nominal 1200mA (*) trip level.

Edit: (*) I haven't measure the R_LIM to see if it's other than the old 19.5kOhm value which set 1200.

Would be good if did not have to spend time searching for this info.. but thanks for confirmation

[l_k3]

The Raspberry Pi camera module does not work with the Raspberry Pi3.
....
Can someone confirm that? Any suggestions?

Thanks
Mario

Camera works just fine.

Have you enabled it via

raspi-config?

Yes, as i wrote in my post.

[gregeric]

Would be good if did not have to spend time searching for this info.. but thanks for confirmation

Where's the fun in that?

As adun has noticed, they ran out of GPIOs so something had to give!

[tdenson]

That worked fine after updating thanks all

[tvjon]

The Raspberry Pi camera module does not work with the Raspberry Pi3.
....
Can someone confirm that? Any suggestions?

Thanks
Mario

Camera works just fine.

Have you enabled it via

raspi-config?

Yes, as i wrote in my post.

Check

viewtopic.php?f=28&t=138231&p=917735

in case it's relevant.

In fact it may be useful to post your

/boot/config.txt

[adun]

Would be good if did not have to spend time searching for this info.. but thanks for confirmation

Where's the fun in that?

As adun has noticed, they ran out of GPIOs so something had to give!

Even the act led has moved to a virtgpio. I assume they needed GPIO 47 again for sd-card detect. As the pi can now boot directly from usb / pxe.

[lashturner]

I am wondering what would the difference in price if a cortex A72 could have been used instead of A53 as I was curious about soc and was trying to gain some knowledge on processors. I was just looking up the Cortex A53 and saw there were newer ones on wiki. Wish I had learned this 40 yrs ago when I was 26.

[jamesh]

I am wondering what would the difference in price if a cortex A72 could have been used instead of A53 as I was curious about soc and was trying to gain some knowledge on processors. I was just looking up the Cortex A53 and saw there were newer ones on wiki. Wish I had learned this 40 yrs ago when I was 26.

Considerable, the A72 is a HUGE core, each core is a couple of times larger than all 4 cores of an A53, so a quad core A72 would be >8 times larger ins silicon area than an A53, which would make the chip very expensive.

They are very quick though!

[gregeric]

Even the act led has moved to a virtgpio. I assume they needed GPIO 47 again for sd-card detect. As the pi can now boot directly from usb / pxe.

I started a new thread on RPi3B schematics for us to tease this all out: viewtopic.php?f=63&t=138280

[PeterO]

Having just put a PI3 into a Pibow case I find that the decision to replace the sdcard holder with a friction fit means it is now actually impossible (with my big fingers) to remove the card without using long-nose pliers to grab the card. If you aren't careful it would be very easy to damage the holder or even snap/crunch the card This seems a bad change to me

PeterO