We use cookies to provide our visitors with an optimal site experience. View our privacy notice and cookie notice to learn more about how we use cookies and how to manage your settings. By proceeding on our website you consent to the use of cookies.
I have migrated to kernel 5.10.131 as per your suggestions. I could port UART dts files successfully according to 5.10.131 kernel. But dts BB-I2C1-RTC-PCF8563 is not getting loaded. I am seeing below errors,
[ 59.499172] rtc-pcf8563 1-0051: pcf8563_write_block_data: err=-16 addr=0e, data=03
[ 59.499190] rtc-pcf8563 1-0051: pcf8563_probe: write error
[ 59.499428] rtc-pcf8563: probe of 1-0051 failed with error -5
[ 59.499525] i2c i2c-1: new_device: Instantiated device pcf8563 at 0x51
Thanks for your reply.
Could you please provide the rtc/ i2c dtbs for enabling the same?
Also I was doing memory profiling with kernel 5.10.131 I have observed that free memory is dying over the time when I am running qt UI-based applications with xorg and Xserver changes. And also parallely verifying the x11vnc functionality.
I would like to know the changes/fixes made in 5.10.131 kernel compared to 5.10.87 kernel. Do you support any memory profiling tool for BB kernel to debug the memory usage at kernel/ application level?
Thanks for your quick reply. I will verify and let you know the feedback of rtc working.
As I am monitoring the memory usage in kernel 5.10.87 and 5.10.131, I observed that free memory is dying over time. I could not see any memory usage improvements across the kernel versions. Earlier with kernel version 4.4.27 on ubuntu 16.04 observed that the memory usage is not that much compared to 5.10. It would be helpful to debug and finalize the kernel versions for production. Please share the memory optimization debugging methods for kernel/ user applications.
Appreciate your input.
I verified the new dts file and seems like rtc is registered. But write to pcf registers failed
[ 2.421020] rtc-pcf8563 1-0051: registered as rtc1
[ 60.014794] i2c i2c-1: Failed to register i2c client pcf8563 at 0x51 (-16)
[ 229.454408] i2c i2c-1: Failed to register i2c client pcf8563 at 0x51 (-16)
[ 231.261926] i2c i2c-1: Failed to register i2c client pcf8563 at 0x51 (-16)
I am trying to write pcf using below command
sh -c “echo ‘pcf8563 0x51’ > /sys/class/i2c-adapter/i2c-1/new_device”
I am getting below errors though i2c-1 in /sys/class/i2c-adapter is availble
[ 60.014794] i2c i2c-1: Failed to register i2c client pcf8563 at 0x51 (-16)
ls /sys/class/i2c-adapter/i2c-1/
1-0051 device name of_node subsystem
delete_device i2c-dev new_device power uevent
Again the schematic is not available with me.
The dtbs used to work properly on ubuntu 16.04 with kernel version 4.4.27. Here is the log from kernel 4.4.27
[ 36.823375] rtc-pcf8563 1-0051: chip found, driver version 0.4.4
[ 36.842474] rtc-pcf8563 1-0051: rtc core: registered rtc-pcf8563 as rtc1
[ 36.845150] i2c i2c-1: new_device: Instantiated device pcf8563 at 0x51
Ubuntu is not supported in omap-image-builder, it’s only enabled as a reference config. Currently 5.10 is the main target we are developing for Debian 11.x Bullseye…
We have cycle for upgrading all devices in production. Mostly after every 5-6 years we upgrade the devices complete software package including bootloader, kernel, filesystem and other software packages. So as a part of that activity we have migrated the complete software.
What would be the correct time frame to get the stable version of kernel and rootfs? I would like to know your views/ suggestions on this upgrade.
The BeagleBoard.org “community” does not operate that way… There is no direct Engineering Team, it’s all community run…
Today there are ‘2’ “Snapshots” updated once a month for Debian 10.x (Buster) ~ mostly stable, and Debian 11.x (Bullseye) ~ mostly fixes and improvements.
As a community, our goal is that anything that works in the Buster 4.19.x-ti kernel should work in the Bullseye 5.10.x-ti kernel…
Due to this thread, you’ve now helped us fix the BB-I2C1-RTC-PCF8563.dts overlay
Now that i see your not using the overlay and instead doing…
sh -c “echo ‘pcf8563 0x51’ > /sys/class/i2c-adapter/i2c-1/new_device”