If you don't answer my questions this is going to take a very long time. I think the problem is with the codec. Is the codec device driver module loaded? I suspect it isn't. Please upload the .dts file and the parts of the codec driver that refer to the compatible string. Search /lib/modules/<versio...
It's telling you that the codec is not registered. This suggests that the codec driver has not loaded. Have you read the troubleshooting section of the documentation? Is the driver loaded? Does it have MODULE_DEVICE_TABLE(of, ...) ?
Cool. For future reference, you could have managed without the 'soc' patches because I also implemented "target-path" - an alternative to "target" that takes a full path string instead of a reference to a label - but I'm happy to add it for completeness.
I'm not a pinctrl expert, but my understanding is this: pinctrl manages groups of pins, allowing the user to specify a number of states (these would normally correspond to activities) and then ask for the pins to be put into those states. In this case there is only one state - "default" - and that i...
1. Read the documentation. 2. Start with one of the existing overlays - look at arch/arm/boot/dts/*-overlay.dts 3. Make sure you can compile it without errors. You may need a new dtc (see documentation). 4. Change as little as possible. 5. If you get errors, upload it here along with the exact comma...
`intc` is not found because although it is a label in the base .dts file, it is not an alias - an oversight. The version of `dtc` supplied in the kernel tree does not support unsolved references or generate the `__symbols__` node, and that is the one used to build the base DTBs. That's the reason th...
@notro: I think the warning is caused by the fact that the when eepflash.sh is used to read the eeprom, it copies the whole device, not just the content you programmed into it. Comparing the two files (as I'm sure you have) shows that the file read back is padded with 0xff's up to the full 4K limit....
@notro Can you attach or PM me the .eep file? base64 it if you need to. I'll try to work out why you are getting the warning, but I'm happy it seems to be working for you.
@DougieLawson Hmm, that's disappointing. I don't think we have one of those in Pi Towers, and anyway I'm out now until the New Year, but if you're still having problems then I'll see what I can do. In the meantime you could try dropping FreedomBen a line.
@notro That was quick work. Thank you for the feedback. :D Yes, you can load multiple overlays. If you are using overlay parameters, you need to apply them before loading the next overlay, and an overlay from the HAT EEPROM is current at the start of config.txt. Otherwise there are no restrictions (...
I notice that FreedomBen has a repo that contains many RealTek drivers, including one for the RTL8188cu, that he claims work on 3.18.y. It might be worth taking a look.
@vvn2023, I suggest you start by reading the source to the existing overlays - you will find them all in arch/arm/boot/dts, named "*-overlay.dts". Also look at the minor changes to the drivers that happened at the same time - commit cee7c800c812cab928de37e82b229644f7f16b05 on branch rpi-3.18.y is wh...
Have you looked at the output from sudo vcdbg log msg ? While hardly copious, it should help to either reassure you or help to show what is going wrong. Remember that all of the device tree processing happens before the ARM executes a single instruction, so dmesg output is not straightforward. Varia...
As promised, there is now a better way to enable the optional interfaces (i2c, i2s, spi) - device tree parameters. The latest BRANCH=next firmware release includes support for patching certain parts of the device tree at boot time, all controlled from config,txt. There will be a more comprehensive d...
They should have never been there in the first place. Even with extensive use of 'rebase', I can't rewrite history, just improve the future. i2c-1 i2c-0 spi If you've been following this thread you should now have (i2c-0 + i2c-1 + spi) and (i2c-1 + spi). You should also have the tools to construct ...
Dougie, Sorry about the lack of response - I didn't receive a notification about your posts. I need to check my settings. I'm happy that SPI is working for you now. The camera still functioned for me with DT, admittedly using a B+. So I started experimenting with overlays to enable the I2C ports, wi...
P.S. Anybody following this on a clean, updated system and wondering why the /dev entries haven't appeared, you need to empty/comment out the contents of /etc/modprobe.d/raspi-blacklist.conf This will allow the i2c and spi modules to be loaded at the next boot, and will cause the /dev/spidev0.0 and ...