![]() ![]() In it, there were some specific packages that must be installed suchĪs (at the time of writing): alsa-firmware 1.2.4-2 arm_64bit=1įrom there, another thread entitled alsa - device not Some of the posted code may not apply to the particular model, butĪs the author clearly specified, many of these settings might differĬonsiderably from one’s setup. Installing another kernel tailored to this particular sound problem. Which as one might guessed by going over it, it deals with Re: fresh rpi4b install with linux-raspberrypi Some of the back then outstanding issues with the rpi4 model b. Therein, another specific thread dealing with this issue was openedįor example, specifically opened to collect more information about That different from mine, and yet the issue was not resolved. Rpi4 as it has been outlined on many of the threads, are not quite The configuration files and particular model and versions for the ![]() In the case of ArchlinuxArm this has been an outstanding issue Whether it has been casued for some given reason or another, Other distros have dealt successfully with this issue before. Solutions/recommendations/suggestions haven’t resolved the problem. I’ve usually read a great many threadsĭealing with this issue before. Under Arch Linux with the sound output from the headphones Rpi4 has had trouble for a while now, especially running ![]() This will allow us to gain some memory/room for our changes.Rpi4 on Arch Linux Arm No Audio Headphones resolved with snd_bcm2835_enable_headphones=1 May 22, 2022Īccording to the recommendations the block of code should be in one Note: about the “fdt resize” command (excerpt from u-boot’s help): fdt resize - Resize fdt to size + padding to 4k addr Libretech_cc# fdt mknode fdt set compatible "maxim,ds3231" Libretech_cc# fdt set pinctrl-names "default" Libretech_cc# fdt addr 0x02f00000 fdt resize On the u-boot command line, this translate into (alias not handled here, not the main aim of the change): libretech_cc# ext4load mmc 0:1 0x02f00000 /meson-gxl-s905x-libretech-cc.dtb I’ll choose 0x100 as number because there are very few chances of collisions. The quick and dirty solution I’m using is to add manually the new phandle. The first one is a label, so all is needed is to replace it with the corresponding node path : second is called a phandle (see the elinux wiki for instance) and when compiled, the device tree binaries are only keeping the ones used and thus, unfortunately for us, the phandle is removed. Unfortunately, there are some small challenges: &i2c_AO and are some kind of references. Looking at the changes done in the device tree, it seems easy. This means that all the changes done in the device tree must be written in terms of u-boot commands. Given that our board is new enough to have a u-boot with device tree support, the new solution coming at hands is to modify the device tree from it. Having to patch the dts and then build the dtb every new kernel update (as long as there are changes in the device tree).The first approach is simple but has some small problems like (the list is not complete and subjective) : So, if the new dts is compiled, and the kernel booted, we can check everything is fine: # ls #size-cells clocks compatible interrupts linux,phandle name phandle pinctrl-0 pinctrl-names reg statusġ-0068 delete_device device name new_device of_node power subsystem uevent This roughly translate into adding the following code to the kernel device-tree. Configure the pinctrl for the pins 3 and 5,.Add an alias to the I2C bus, so that it becomes I2C bus 1.First approach: Modifying the kernel device treeĪccording to the schematics found on Libretech documentation, the I2C bus available on the 1/3/5/7 pins of the 7J1 connector is the I2C connected on the AO bus (AO stands for Always On). Due to cut&pasting, there may also be some spacing issue on the command output and file content. The different commands are done on a Debian sid and on the board serial port (connector 2J1) for commands run on the board. I will even skip some details, like how to patch, configure or build a kernel or u-boot. This post will be more or less an elaborate backup of my notes, which means that some basic knowledge of kernel, kernel build, devicetree and u-boot is needed. Moreover, there’s a temperature sensor on it, even if it’s no really precise (+/- 3☌). They’re quite easy to find and can be used on every board with a raspberry-pi-like 40-pin header. This is kind of annoying so I tend to have a bunch of DS3231 module, which have a battery. As often with this kind of boards, there’s no battery powered RTC on it. ![]() Thanks to the nice guys from Baylibre, I got a Potato board from Libretech. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |