Raspberry Pi Forums

Post the overlay(s) you are trying to use - don't make me guess.

Only BCM2711 can address more than 1GB, and BCM2711 is far from a drop-in replacement for BCM2837.

You have a few options: 1. Simple but ugly on the outside - multiple overlays. 2. Ugly on the inside - use the "__dormant__" feature to hide fragments, and a parameter with the magic "<0>" target to enable and disable fragments. 3. Advanced - use the new "literal assignments" feature to patch the pw...

You've got several questions in here, so I'll try to pull them apart and answer them in order: 1. How do you refer to something added in one overlay from another? In an ideal world you would be able to create a label in one overlay and refer to it from another. This is technically possible - the ove...

You have the option of putting unique MAC addresses in OTP - see https://www.raspberrypi.org/forums/view ... p?t=231700 for details.

"cat /proc/cpuinfo" shows the list of supported "Features:". The complete list of potential features is: static const char *hwcap_str[] = { "swp", "half", "thumb", "26bit", "fastmult", "fpa", "vfp", "edsp", "java", "iwmmxt", "crunch", "thumbee", "neon", "vfpv3", "vfpv3d16", "tls", "vfpv4", "idiva", ...

How to make sure gpio=2,3=ip can no be overwritten by the kernel?

You would need a modified overlay that doesn't claim those pins. Alternatively, don't use the overlay and do it all using gpio declarations in config.txt.

The "<whatever>" is likely to be "/dev/mmblk0" for the whole EMMC.

You wrote: gpio 28 TOUCH SDA gpio 30 TOUCH SCL I'm going to assume this is a typo and that GPIO29 is SCL, since everything else seems to fit. Also, there is no attachment. I'm not a fan of all those gpio declarations in config.txt - they have their place sometimes, but I think you could get rid of m...

Create a new thread for each new issue, please. It makes it easier for us to track open issues, and it avoids spamming anybody who was only interested in the original topic.

Use dd? Something like:

Code: Select all

$ sudo dd if=/dev/whatever of=backup.img bs=128k

The hardware has arrived (I'm assuming it's yours - I'm not expecting anything else) - now we need some instructions on how to reproduce the fault.

Attaching a schematic of your carrier would prevent this thread from turning into a game of Twenty Questions.

We got there in the end, and that's what matters.

The built-in dt-blob for CM3 is identical to the one in the firmware repo. Both show that GPIO47 is used for I2C control of the SMPS. Neither declares the ACT LED to the firmware - it is bcm2710-rpi-cm3.dtb that declares it to Linux as being an active low signal attached to the "virtgpio" interface ...

You need to free up some space, then retry the update.

The canonical published dt-blob.dts is hosted in our firmware repo: https://github.com/raspberrypi/firmware ... t-blob.dts

The Act LED is solid green on the devboard & CM3 when the system is operating with a dt-blob.bin and is working as expected without dt-blob.bin file. That suggests the dt-blob.bin has incorrect content. Where did you get the source for the dt-blob.bin (or the binary if you didn't compile it yoursel...

Multiply mapping alternate functions often fails - output only pins are usually OK, but for input pins it goes horribly wrong. This is important because the firmware has always had mechanisms to enable the correct UART alt function if enable_uart=1, a task which is straightforward until DT overlays ...

Either "sudo vcdbg log msg" or "dmesg -l err" should give a clue.

[ Split off into a separate topic ]

4.19 and 4.14 are virtually identical with regards to the spi-bcm2835 driver. 4.19 has a bug fix for 3-wire mode and supports shared interrupts, but that's it. It's more likely that a change elsewhere in the kernel (interrupt handling, for example) could have caused a regression. One option for you ...

Sometimes when it is powered up or rebooted it seems like the data has corrupted on the EMMC, however other times it boots up perfectly fine. To avoid any confusion, do you always have to fix the corruption before it will boot successfully? In other words, is this occasional corruption caused by a ...

I wrote:

(at the point of probing, which is after the "gpio ..." handling)

Did I understand right, that without a customized dt-blob, (I will not yet go into the experience of compiling a new one yet), the HAT probing will occur anyway? No, not if you have used the gpio directive to change to some pin function other than input. And if you haven't used either a custom dt-b...

Search found 2762 matches

Re: [SOLVED] CM3 Plus and WiFi/BT CYW43455

Re: Compute Module 4

Re: Overlay able to use external pwm channel?

Re: Overlay able to use external pwm channel?

Re: MAC Address of Compute Module

Re: Question regarding the Broadcom BCM2837B0 Cortex A-53 processor instruction set

Re: CM3 and Display Touch I2C Controller

Re: eMMC Backup

Re: CM3 and Display Touch I2C Controller

Re: CM3 Plus and WiFi/BT CYW43455

Re: eMMC Backup

Re: Rare comms failure with enc28j60 and compute module "netdev watchdog: eth0 ("enc28j60"): transmit queue 0 timed out"

Re: Custom CM3 carrier board cannot boot from USB mass storage

Re: CM3 ACT LED no longer blinking with mmc activity?

Re: CM3 ACT LED no longer blinking with mmc activity?

Re: CM3 Plus and WiFi/BT CYW43455

Re: CM3 ACT LED no longer blinking with mmc activity?

Re: CM3 ACT LED no longer blinking with mmc activity?

Re: CM3 Plus and WiFi/BT CYW43455

Re: CM3 Plus and WiFi/BT CYW43455

Re: I2S clock rate question

Re: Rare comms failure with enc28j60 and compute module "netdev watchdog: eth0 ("enc28j60"): transmit queue 0 timed out"

Re: CM3+ EMMC Corruptions?

Re: Pi-4 Activating additional UART ports

Re: Pi-4 Activating additional UART ports