Raspberry Pi Forums

Yes - it will go into rpi-4.4.y, which will be released as BRANCH=next initially. I'm not anticipating any observable change for users who don't try the dtoverlay command. The switch to 4.4 for all users will happen shortly afterwards, assuming no problems - again, I'm not expecting any.

Consider this advance warning of some upcoming changes to Device Tree usage on Raspberry Pi: 1) The use of whitespace as a delimiter in dtoverlay and dtparam lines is deprecated and will cease to work shortly - stick to commas; the utility of being able to put whitespace in a parameter value outweig...

Change the serial1 in cmdline.txt to serial0. (That use of serial1 was a short-lived special needed when the miniuart overlay was first added - with the latest firmware it is no longer necessary, and serial0 is always the non-BT uart).

Good for you. Come back here with questions - that's what this forum is for.

Yes, in a sense that property is useless in the base .dts files, but I think it helps the reader to know which model the file is intended for, plus it matches other architectures which don't have the same involvement of the firmware.

No, I really mean the firmware. The VPU (also known as the GPU) boots first, loads the .dtb, applies any overlays and parameters and some other settings - including the model string - then boots the kernel. This means that any model string you provide will be completely overwritten, so don't bother ...

The firmware overwrites the Model string to include the board revision number. You can see the entire Device Tree at /proc/device-tree, which may help to remove doubt about what is happening. You can also see if the firmware encountered any problems with the DT using sudo vcdbg log msg |& grep -v -E...

Alternatively you might be able to target the "act" label and just overwrite the gpios property. This should allow the existing dtparams to continue to work, but I'm not in a position to try it right now.

Have you read through this thread?: viewtopic.php?f=66&t=122207

Try with ":0.0" - period, not comma.

This is the wrong thread for an intermittent WiFi problem - this one was permanent.

We observed a potential, intermittent problem with the firmware release, only on one Pi so far, but we're taking the time to understand it before pushing out the full Raspbian release.

Ah, I see. Although present in the Pi1 and Pi2 DTBs, those options were missed out of the Pi3 DTB. I've pushed patches to add them, and both rpi-update and apt-get upgrade releases will be made today. In the meantime you can use the sdtweak overlay here . Use it like the old sdhost overlay: dtoverla...

You still haven't addressed point 2, and I think making the rpi-update + serial0 optional without any indication why is confusing, but it is your blog and I will say no more.

Another few corrections: 1) There's a stray space in sudo nano /boot/ cmdline.txt 2) If you want Bluetooth to work then don't disable the hciuart service - just edit hciuart.service as you describe. If you don't want Bluetooth then don't edit the service, just disable it. Pick one. 3) Although I am ...

That's absolutely fine. I have a small correction though - please don't include the "-overlay" in the dtoverlay directive. It isn't guaranteed to work in the future.

I've pushed the overlay (pi3-miniuart-bt) to the source trees. It will appear in the next release, or you can download prebuilt one here . The commit message says: Switch Pi3 Bluetooth function to use the mini-UART (ttyS0) and restore UART0/ttyAMA0 over GPIOs 14 & 15. Note that this may reduce the m...

I'm guessing that you are using the sdhost overlay? That's probably not what you want on a Pi3 because it will also disable the mmc interface which is now used for SDIO. Instead, the new base DTBs have an sd_overclock parameter which does the same thing as the overclock_50 parameter of the sdhost ov...

The mini UART (ttyS0) does not support parity. I will create an overlay that uses ttyS0 for the BT modem, which may work for low baud rates and data volumes. Using it will also require the systemd script (/lib/systemd/system/hciuart.service) to be edited.

So what happens when you follow the rest of the tutorial? If you don't tell me, I can't help you.

That all looks fine - is it working now? If not, please make clear the difference between what you expect and what you observe.

I didn't see that you had edited your previous post - it doesn't help that it is now on the previous page. In general editing is a bad idea because people don't receive notifications. /etc/modules contains the names of modules that the user wants the kernel to load, but there are other reasons that ...

spi-bcm2835 selects the upstream SPI driver. I'm not saying there is anything wrong with it, but everybody else is using the downstream driver. It looks like the action of an advanced user, and you don't strike me as one. As I said it works perfectly on wheezy 2015-05. Perhaps that's because the spi...

What's wrong with

Code: Select all

 sudo ifconfig eth0 down

?

1) Don't grep for spi - either grep for dt or include the whole log.

2) Why are you loading spi-bcm2835?

3) Don't include the -overlay in the overlay name - that is implicit.

Search found 2762 matches

Re: Upcoming Device Tree changes

Upcoming Device Tree changes

Re: Raspberry Pi 3 - Bluetooth PL011 UART (9bit on mini-UART

Re: study on device tree on raspberry pi 2

Re: study on device tree on raspberry pi 2

Re: study on device tree on raspberry pi 2

Re: study on device tree on raspberry pi 2

Re: Redirecting the ACT LED on a RPi3

Re: rc.local after upgrade to jessie does not work

Re: Remote display not working

Re: [RESOLVED] Pi3 WiFi stopped working

Re: [RESOLVED] Pi3 WiFi stopped working

Re: Pi3 WiFi stopped working

Re: Overlay to remap Pi 3 UART

Re: Overlay to remap Pi 3 UART

Re: Overlay to remap Pi 3 UART

Re: Overlay to remap Pi 3 UART

Re: Pi3 WiFi stopped working

Re: Overlay to remap Pi 3 UART

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Re: enable/disable ethernet card on RPi3

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.