Activity
From 02/22/2026 to 03/23/2026
03/23/2026
- JC 01:51 PM Software Development: RE: Uart issue in Am62P
- Thanks for the update. Would you mind sharing what the solution was?
- RD 05:44 AM Software Development: RE: Uart issue in Am62P
- Hi Jonathan,
I was on a long vacation until recently. The issue has now been fixed.
Best regards,
Rajkumar.
03/19/2026
- TT 09:53 PM Software Development: RE: Can't read state of output GPIO pins
- Thank you, that would explain it. We ended up setting the pin regardless of the current state. It was an easier change for us.
Tim
03/16/2026
- JC 06:05 PM Software Development: RE: Can't read state of output GPIO pins
- At least for the AM62x, Pins that need to be read, must be pinmuxed as PIN_INPUT*. The only difference between the PIN_OUTPUT and PIN_INPUT #define is whether the input buffer is enabled.
- Hi,
On an AM62x we have a gpio pin (/dev/gpiochip2, line 10) muxed as an output pin. Our application checks the state of this pin to see if it is in the desired state before setting it if needed. Unfortunately the pin state is always ...
02/25/2026
- JC 05:05 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- Great glad it worked. Hopefully the dtc command examples will be helpful for you and others as well
- BH 04:59 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- I md5sum'ed the SD dtb and the emmc dtb, they were in-fact different. I re-copied the files and now it is working. I guess in some step I mixed up which device I had updated the rootfs on. I think this is solved. Thank you for your help!
- JC 04:24 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- It would also be a good idea to md5sum the emmc and sdcard versions of the tfc dtb to make sure they are infact identical.
- JC 04:23 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- Thanks Ben, I hadn't realized that.
Lets make sure the tfc device tree file contains what you expect it to.
Do you have the "dtc" tool on the filesystem, I think we include it by default?
You can use it to inspect the compiled d... - MW 03:35 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- can you also post the dtb file?
- BH 03:21 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- Sorry, I just posted the u-boot log, it does indeed boot. Per the u-boot log it claims to load my dtb but the differences in the device tree once in linux are not present, here's just one example, if in SD boot I see my device tree refle...
- JC 02:43 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- > Some progress made, it now finds the file but still does not load it.
It looks like it did load it from the eMMC so that is indeed progress
02/24/2026
- BH 11:06 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- Hi Jonathan,
Some progress made, it now finds the file but still does not load it.
Here are the dtbs (the "-tfc" is mine) - JC 10:47 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- Yeah please share the console log during the boot attempt.
To get a bit more debug info, enable xtrace in u-boot before running boot - BH 10:38 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- Hi Jonathan,
Thanks for your reply. Unfortunately, that did not solve the problem. The system fails to find the file and then proceeds to boot with the bootloader image fdt.
I have confirmed the dtb I want is located in the user par... - JC 09:26 PM Software Development: RE: AM62A eMMC Boot - Kernel Device Tree
- Hi Ben,
The device tree file that gets loaded is set in the fdtfile variable. You should be able to update it to match your device tree. - I’m working with the AM62A SoM and a Yocto development environment, switching between the CL devkit and custom hardware.
I am trying to boot the system with a modified device tree. This works fine from SD-cards but when I follow the ...
02/23/2026
- JC 04:01 PM Software Development: RE: Problems writing to MCU_GPIO0_19 and MCU_GPIO0_20
- Glad it worked. Thanks for closing the loop
- PS 10:44 AM Software Development: RE: Problems writing to MCU_GPIO0_19 and MCU_GPIO0_20
- Just a quick note to say thanks to everyone for solving this issue this quickly
We have fitted the pullups to our board and can now see the outputs toggling
Paul