AM625: How to control brightness of display using pwm in Android on custom AM625 SOM, using RGB display.

Aditya Tandulwadkar

Part Number: AM625

Tool/software:

Hello Ti experts,
Currently I've successfully booted Android on custom AM625 SOM with RGB display and capacitive touchscreen. But now I need to control the brightness of display, which is to be controlled by using pwm.
Can you please help me to get pwm on E18 processor pin, with mux mode set to 6.
I'm able to control brightness on Linux on same hardware and same processor pin, but cant do it for android. Please guide me.

Also I'm not able to use the custom bootanimation.zip, In this when I try to copy the custom bootanimation.zip file at /system/media location. But there's no such a directory named "media" under the "system" directory of Android, and when I'm trying to create the directory, then it says "Read-only filesystem : Permission denied". Now how to change the bootanimation.zip?

Best Regards,
Aditya T

27 days ago

0 Mattijs Korpershoek 27 days ago

TI__Intellectual 1435 points

Hi,

Can you please detail how you control the brightness in linux?
Besides changing the pinmuxing in the device-tree, anything else is needed?
Do you use a sysfs for controlling the brightness ?

For custom bootanimation.zip, as it's a seperate issue, please open a separate e2e thread.

Thanks
Mattijs

0 Aditya Tandulwadkar 27 days ago in reply to Mattijs Korpershoek

Intellectual 470 points

Hello,

Mattijs Korpershoek said:
Can you please detail how you control the brightness in linux?
Besides changing the pinmuxing in the device-tree, anything else is needed?
Do you use a sysfs for controlling the brightness ?

In linux I'm doing it using the commands provided here: Link
Yes I'm using sysfs for controlling brightness in Linux.

Mattijs Korpershoek said:
For custom bootanimation.zip, as it's a seperate issue, please open a separate e2e thread.

Okay, I'll create a seperate thread for this.

Kind Regards,
Aditya T

0 Mattijs Korpershoek 27 days ago in reply to Aditya Tandulwadkar

TI__Intellectual 1435 points

Hello,

Thank you for the details.

I'd like to understand now where you are stuck in Android.

Can you confirm that using the same commands as in linux, it does not work in Android?

What is the output of:

ls /sys/class/pwm/

On your system?

0 Aditya Tandulwadkar 22 days ago in reply to Mattijs Korpershoek

Intellectual 470 points

Hello,

Mattijs Korpershoek said:
Can you confirm that using the same commands as in linux, it does not work in Android?

Yes, I'm able to control the brightness of display using pin E18 with mux mode 6 in Linux, and by same commands.

Mattijs Korpershoek said:
What is the output of:
ls /sys/class/pwm/
On your system?

am62x:/ # ls /sys/class/pwm/                                                                                                                                                            
pwmchip0  pwmchip1
am62x:/ # cat /sys/kernel/debug/pwm                                                                                                                                                     
platform/23010000.pwm, 2 PWM devices
 pwm-0   ((null)              ): period: 0 ns duty: 0 ns polarity: normal
 pwm-1   ((null)              ): period: 0 ns duty: 0 ns polarity: normal

platform/dmtimer-main-pwm-7, 1 PWM device
 pwm-0   (led-0               ): requested period: 7812500 ns duty: 0 ns polarity: normal
am62x:/ # cd /sys/class/pwm/pwmchip1/                                                                                                                                                   
am62x:/sys/class/pwm/pwmchip1 # echo 1 > export                                                                                                                                         
am62x:/sys/class/pwm/pwmchip1 # cd pwm1/                                                                                                                                                
am62x:/sys/class/pwm/pwmchip1/pwm1 # echo 40000 > period                                                                                                                                
am62x:/sys/class/pwm/pwmchip1/pwm1 # echo 10000 > duty_cycle                                                                                                                            
am62x:/sys/class/pwm/pwmchip1/pwm1 # echo 1 > enable                                                                                                                                    
am62x:/sys/class/pwm/pwmchip1/pwm1 #

I've given these commands, but it doesn't changed the brightness of my display.

Best Regards,
Aditya T

0 Mattijs Korpershoek 21 days ago in reply to Aditya Tandulwadkar

TI__Intellectual 1435 points

Hi Aditya,

Ok, so if I understand correctly from the debugfs we have:

/sys/class/pwm/pwmchip0: 23010000.pwm
/sys/class/pwm/pwmchip1: dmtimer-main-pwm-7

We want to control pwm-0 (led-0) from /sys/class/pwm/pwmchip1.

In that case, shouldn't we export pwm-0 and not pwm-1 for pwmchip 1?
I think the commands should be:

am62x:/ # cd /sys/class/pwm/pwmchip1/                                                                                                                                                   
am62x:/sys/class/pwm/pwmchip1 # echo 0 > export                                                                                                                                         
am62x:/sys/class/pwm/pwmchip1 # cd pwm0/                                                                                                                                                
am62x:/sys/class/pwm/pwmchip1/pwm1 # echo 40000 > period                                                                                                                                
am62x:/sys/class/pwm/pwmchip1/pwm1 # echo 10000 > duty_cycle                                                                                                                            
am62x:/sys/class/pwm/pwmchip1/pwm1 # echo 1 > enable                                                                                                                                    
am62x:/sys/class/pwm/pwmchip1/pwm1 #

According to https://docs.kernel.org/driver-api/pwm.html#using-pwms-with-the-sysfs-interface

0 Aditya Tandulwadkar 21 days ago in reply to Mattijs Korpershoek

Intellectual 470 points

Hello,

Mattijs Korpershoek said:
Ok, so if I understand correctly from the debugfs we have:

/sys/class/pwm/pwmchip0: 23010000.pwm

/sys/class/pwm/pwmchip1: dmtimer-main-pwm-7

No, you are getting it wrong. pwmchip0 is of dmtimer-main-pwm-7 and pwmchip1 is of 23010000.pwm I got to know this after performing this.

am62x:/sys/class/pwm # ls -l
total 0
lrwxrwxrwx 1 root root 0 2024-11-12 05:23 pwmchip0 -> ../../devices/platform/dmtimer-main-pwm-7/pwm/pwmchip0
lrwxrwxrwx 1 root root 0 2024-11-12 05:23 pwmchip1 -> ../../mailto:devices/platform/bus@f0000/23010000.pwm/pwm/pwmchip1
am62x:/sys/class/pwm #

Also on pwmchip1, I've tried for both pwm0 and pwm1.

Additionally I want to tell you that in Linux when I was generating pwm on an ehrpwm pin, it was generating 2 pwm devices on same chip. Like on pwmchip1 there are 2 devices pwm0 and pwm1. So I think you got confused here.
The pwm with dmtimer is on another chip, we don't need to see it i.e. pwmchip0 is none of our use while performing the brightness control for display.

Best Regards,
Aditya T

0 Mattijs Korpershoek 20 days ago in reply to Aditya Tandulwadkar

TI__Intellectual 1435 points

Hello,

Thank you for the clarifications.

Since we can't reproduce your setup because you have a custom board and you have a working set up on linux, can you please provide as much information as possible on both working (linux) and failing (android) cases.

At least the output of ls -l in /sys/class/pwm for both linux and android

Maybe some kernel modules are missings. On Android most drivers are modules (not the case on linux)

0 Aditya Tandulwadkar 19 days ago in reply to Mattijs Korpershoek

Intellectual 470 points

Hello,

Mattijs Korpershoek said:
Since we can't reproduce your setup because you have a custom board and you have a working set up on linux

No, you can try to generate pwm on the same processor pin, on which I'm trying to generate. Its because the processor pin E18 is actually connected to pin 33 of "40 pins J3 header".

Mattijs Korpershoek said:
can you please provide as much information as possible on both working (linux) and failing (android) cases.

At least the output of ls -l in /sys/class/pwm for both linux and android

Okay, I've attached the output for both below:
1. Linux:

root@am62xx-evm:~# ls -l /sys/class/pwm
total 0
lrwxrwxrwx 1 root root 0 2024-11-12 05:23 pwmchip0 -> ../../devices/platform/bus@f0000/23010000.pwm/pwm/pwmchip1
root@am62xx-evm:~#

2. Android:

am62x:/sys/class/pwm # ls -l
total 0
lrwxrwxrwx 1 root root 0 2024-11-12 05:23 pwmchip0 -> ../../devices/platform/dmtimer-main-pwm-7/pwm/pwmchip0
lrwxrwxrwx 1 root root 0 2024-11-12 05:23 pwmchip1 -> ../../devices/platform/bus@f0000/23010000.pwm/pwm/pwmchip1
am62x:/sys/class/pwm #

Mattijs Korpershoek said:
Maybe some kernel modules are missings. On Android most drivers are modules (not the case on linux)

As per my understanding their's no difference or any changes in drivers required for PWM because I've checked all the included drivers in kernel for Android as well as Linux. Both are the same.

Best Regards,
Aditya T

0 Aditya Tandulwadkar 13 days ago in reply to Mattijs Korpershoek

Intellectual 470 points

Hello Mattijs,
I'm still having this issue, kindly update me once you've got something on this.

Best Regards,
Aditya T

0 Mattijs Korpershoek 9 days ago in reply to Aditya Tandulwadkar

TI__Intellectual 1435 points

Hi,

Sorry for the delay, we are working on it and keep you posted.

0 Aditya Tandulwadkar 8 days ago in reply to Mattijs Korpershoek

Intellectual 470 points

Hello,

Please update me as soon as you get any solution.

Kind Regards,
Aditya T

0 Mattijs Korpershoek 8 days ago in reply to Aditya Tandulwadkar

TI__Intellectual 1435 points

Will do. I ordered a logic analyzer so that I can debug this. I receive it this week so I'll keep you updated this week/early next week.

0 Aditya Tandulwadkar 8 days ago in reply to Mattijs Korpershoek

Intellectual 470 points

Sure.
Thanks & Regards,
Aditya T

0 Mattijs Korpershoek 5 days ago in reply to Aditya Tandulwadkar

TI__Intellectual 1435 points

Hi Aditya,

As a first step, I tried to reproduce your issue using the upcoming 10.1 SDK release (not yet released) with a 6.6 kernel.

Here are some details on what I've done:

1. Patch the kernel in order to ship the device tree overlay that enables the PWM:

commit 62b61d99b0ca5c3631a07d88210f520f5a3326fd (HEAD -> mkorpershoek/enable-display-pwm)
Author: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Date:   Mon Nov 25 18:10:55 2024 +0100

    TI: ANDROID: Add k3-am625-sk-rpi-hdr-ehrpwm.dtbo to build

    Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>

diff --git a/BUILD.bazel b/BUILD.bazel
index b1d8d54788cc..dcce3f316d54 100644
--- a/BUILD.bazel
+++ b/BUILD.bazel
@@ -908,6 +908,7 @@ kernel_build(
         "k3-am62x-sk-hdmi-audio.dtbo",
         "k3-am62x-sk-lpm-wkup-sources.dtbo",
         "k3-am625-sk-wl1837.dtbo",
+        "k3-am625-sk-rpi-hdr-ehrpwm.dtbo",
         "modules.builtin",
         "modules.builtin.modinfo",
         "vmlinux",
@@ -940,7 +941,7 @@ kernel_build(
         "ti/k3-am62p5-sk-mcan.dtbo",
         "ti/k3-am62p5-sk-microtips-mf101hie-panel.dtbo",
         "ti/k3-am625-sk-wl1837.dtbo",
-
+        "ti/k3-am625-sk-rpi-hdr-ehrpwm.dtbo",
     ],
     module_outs = get_gki_modules_list("arm64") + get_kunit_modules_list("arm64") + _TI_MODULE_OUTS + _TI_WATCHDOG_MODULE_OUTS,
     strip_modules = True,
@@ -961,6 +962,7 @@ kernel_images(
         ":ti/k3-am62x-sk-csi2-tevi-ov5640.dtbo",
         ":ti/k3-am625-sk-microtips-mf101hie-panel.dtbo",
         ":ti/k3-am62x-sk-lpm-wkup-sources.dtbo",
+        ":ti/k3-am625-sk-rpi-hdr-ehrpwm.dtbo",
         ":ti/k3-am62-lp-sk-microtips-mf101hie-panel.dtbo",
         ":ti/k3-am625-beagleplay-csi2-ov5640.dtbo",
         ":ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo",

2. Rebuild the kernel:

tools/bazel run --config=release //common:ti_dist -- --dist_dir=/mnt/work/ti//ti-android-15/device/ti/am62x-kernel/kernel/6.6

3. Rebuild the Android images:

source build/envsetup.sh
lunch am62x-ap3a-userdebug
m

4. Reflash all the images using the flashall.sh script.

5. In U-Boot halt at the prompt and configure our new overlay:

=> setenv adtbo_idx 5
=> saveenv

6. Boot android:

=> run bootcmd

7. In Android, enable PWM via sysfs:

console:/sys/class/pwm # ls -l
total 0
lrwxrwxrwx 1 root root 0 2024-11-25 14:59 pwmchip0 -> ../../devices/platform/bus@f0000/23000000.pwm/pwm/pwmchip0
lrwxrwxrwx 1 root root 0 2024-11-25 14:59 pwmchip2 -> ../../devices/platform/bus@f0000/23010000.pwm/pwm/pwmchip2

console:/sys/class/pwm # cd pwmchip2/
console:/sys/class/pwm/pwmchip2 # echo 1 > export
console:/sys/class/pwm/pwmchip2 # cd pwm1/
console:/sys/class/pwm/pwmchip2/pwm1 # echo 40000 > period    
console:/sys/class/pwm/pwmchip2/pwm1 # echo 10000 > duty_cycle 
console:/sys/class/pwm/pwmchip2/pwm1 # echo 1 > enable

And on the logic analyzer, I see:

This is using PIN 33 (EXP_EHRPWM1_B) on the 40 header expansion.
So it seems to work with the new kernel/upcoming release.

I will try the same with SDK 10.0 release using the 6.1 kernel. Can you confirm that is the baseline you are using, please?

0 Aditya Tandulwadkar 5 days ago in reply to Mattijs Korpershoek

Intellectual 470 points

Yes, I'm doing all the steps which you've mentioned above.
Also I'm using Android SDK 8.6

0 Mattijs Korpershoek 5 days ago in reply to Aditya Tandulwadkar

TI__Intellectual 1435 points

I just tried to reproduce on the Android SDK 10.0 with the standard kernel (6.1) and bootloaders (2023.04) and I don't reproduce the issue either:

Aditya, can you please confirm that with the Linux SDK 8.6 is does work for, just not with the Android SDK 8.6 ?

0 Aditya Tandulwadkar 5 days ago in reply to Mattijs Korpershoek

Intellectual 470 points

Yes, I've confirmed for the Linux OS using SDK8.6 but it doesn't works on same version of Android SDK

0 Mattijs Korpershoek 2 days ago in reply to Aditya Tandulwadkar

TI__Intellectual 1435 points

Hi Aditya,

Unfortunately we don't actively support older SDKs such as Android SDK 8.6.

Please consider upgrading

0 Aditya Tandulwadkar 1 day ago in reply to Mattijs Korpershoek

Intellectual 470 points

[deleted]

0 Aditya Tandulwadkar 1 day ago in reply to Aditya Tandulwadkar

Intellectual 470 points

Hello,
Now, I'm having one more issue i.e. I cant flash my newly built Android on AM625 SOM.
Below are the logs of Host PC and UART of AM625
HOST PC Logs:

repl@android:~/boot$ sudo dfu-util -R -a bootloader -D tiboot3.bin -d 0451:6165
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6165
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 512
Copying data from PC to DFU device
Download	[=========================] 100%       330574 bytes
Download done.
state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
dfu-util: unable to read DFU status after completion
dfu-util: can't detach
Resetting USB to switch back to runtime mode
repl@android:~/boot$ sudo dfu-util -R -a tispl.bin -D tispl.bin -d 0451:6165
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6165
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download	[=========================] 100%      1194588 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
Resetting USB to switch back to runtime mode
repl@android:~/boot$ sudo dfu-util -R -a u-boot.img -D u-boot.img -d 0451:6165
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6165
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #1 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download	[=========================] 100%       895548 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
Resetting USB to switch back to runtime mode
repl@android:~/boot$ 
repl@android:~/boot$ 
repl@android:~/boot$ cd ~/08_06_00/ti-aosp-12/out/target/product/am62x/
repl@android:~/08_06_00/ti-aosp-12/out/target/product/am62x$ sudo ./flashall.sh 
8+0 records in
8+0 records out
8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.0131636 s, 637 MB/s
mkfs.fat 4.2 (2021-01-31)
Fastboot: /usr/bin/fastboot
Image location: ./

Fastboot - device detected: 0000000000000000

Create GPT partition table
                                                   OKAY [  0.020s]
Finished. Total time: 0.020s
Flashing tiboot3.....
   tiboot3bin:     ./tiboot3.bin
Sending 'tiboot3' (324 KB)                         OKAY [  0.039s]
Writing 'tiboot3'                                  OKAY [  0.029s]
Finished. Total time: 0.126s
   bootloader:  ./bootloader.img
Sending 'bootloader' (8192 KB)                     OKAY [  0.370s]
Writing 'bootloader'                               OKAY [  0.152s]
Finished. Total time: 0.583s
Flash android partitions
Sending sparse 'super' 1/2 (746234 KB)             OKAY [ 33.705s]
Writing 'super'                                    OKAY [ 17.833s]
Sending sparse 'super' 2/2 (611129 KB)             OKAY [ 27.391s]
Writing 'super'                                    OKAY [ 12.933s]
Finished. Total time: 91.955s
Flashing Boot Image
Sending 'boot_a' (40960 KB)                        OKAY [  1.669s]
Writing 'boot_a'                                   OKAY [  0.721s]
Finished. Total time: 2.466s
Sending 'boot_b' (40960 KB)                        OKAY [  1.905s]
Writing 'boot_b'                                   OKAY [  0.733s]
Finished. Total time: 2.719s
Flashing userdata Image
Sending 'userdata' (2560 KB)                       OKAY [  0.148s]
Writing 'userdata'                                 OKAY [  1.070s]
Finished. Total time: 1.295s
Flashing vbmeta Image
Sending 'vbmeta_a' (4 KB)                          OKAY [  0.024s]
Writing 'vbmeta_a'                                 OKAY [  0.032s]
Finished. Total time: 0.124s
Sending 'vbmeta_b' (4 KB)                          OKAY [  0.024s]
Writing 'vbmeta_b'                                 OKAY [  0.035s]
Finished. Total time: 0.129s
Flashing DTBO Image
Sending 'dtbo_a' (8192 KB)                         OKAY [  0.405s]
Writing 'dtbo_a'                                   OKAY [  0.172s]
Finished. Total time: 0.648s
Sending 'dtbo_b' (8192 KB)                         OKAY [  0.414s]
Writing 'dtbo_b'                                   OKAY [  0.163s]
Finished. Total time: 0.649s
Flashing persist partition
Sending 'persist' (32768 KB)                       OKAY [  1.562s]
Writing 'persist'                                  OKAY [  0.583s]
Finished. Total time: 2.233s
Erasing misc partitions
Erasing 'misc'                                     OKAY [  0.025s]
Finished. Total time: 0.089s
Formatting metadata partition
FAILED (remote: 'failed to set partition')
fastboot: error: Command failed
formating failed
Erasing 'metadata'                                 OKAY [  0.102s]
Finished. Total time: 0.195s
repl@android:~/08_06_00/ti-aosp-12/out/target/product/am62x$

UART Logs:

U-Boot SPL 2021.01 (Jun 19 2023 - 18:39:28 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from DFU
###########################################################DOWNLOAD ... OK
Ctrl+C to exit ...
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from MMC... MMC Device 0 not found
*** Warning - No MMC card found, using default environment

init_env from device 10 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3a6
NOTICE:  BL31: Built : 10:35:32, Feb 28 2023
I/TC: 
I/TC: OP-TEE version: 08.06.00.007-android (gcc version 10.3.1 20210621 (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29))) #1 Tue Feb 28 09:35:41 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
I/TC: HUK Initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2021.01-00427-g2ee8efd65436 (Feb 28 2023 - 10:35:44 +0100)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from DFU
####DOWNLOAD ... OK
Ctrl+C to exit ...


U-Boot 2021.01 (Mar 01 2023 - 19:44:05 +0100)

SoC:   AM62X SR1.0 GP
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -1
DRAM:  2 GiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -1
Net:   Could not get PHY for ethernet@8000000port@1: addr 0
am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed
No ethernet found.

Hit any key to stop autoboot:  0 
=> env default -f -a
## Resetting to default environment
=> run set_android_boot 
Saving Environment to MMC... Writing to MMC(0)... OK
=> 
U-Boot SPL 2021.01 (Jun 19 2023 - 18:39:28 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from DFU
###########################################################DOWNLOAD ... OK
Ctrl+C to exit ...
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from MMC... MMC Device 0 not found
*** Warning - No MMC card found, using default environment

init_env from device 10 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3a6
NOTICE:  BL31: Built : 10:35:32, Feb 28 2023
I/TC: 
I/TC: OP-TEE version: 08.06.00.007-android (gcc version 10.3.1 20210621 (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29))) #1 Tue Feb 28 09:35:41 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
I/TC: HUK Initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2021.01-00427-g2ee8efd65436 (Feb 28 2023 - 10:35:44 +0100)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from DFU
####DOWNLOAD ... OK
Ctrl+C to exit ...


U-Boot 2021.01 (Mar 01 2023 - 19:44:05 +0100)

SoC:   AM62X SR1.0 GP
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -1
DRAM:  2 GiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -1
Net:   Could not get PHY for ethernet@8000000port@1: addr 0
am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed
No ethernet found.

Hit any key to stop autoboot:  0 
=> fastboot 0
Writing GPT: success!
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 332089 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
..
downloading of 332089 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing Raw Image
........ wrote 332288 bytes to 'tiboot3'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 8388608 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
................................................................
downloading of 8388608 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing Raw Image
........ wrote 8388608 bytes to 'bootloader'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 764144344 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
.........................................................
downloading of 764144344 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing sparse image at offset 225536
Flashing Sparse Image
........ wrote 770875392 bytes to 'super'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 625796124 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
......................................
downloading of 625796124 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing sparse image at offset 225536
Flashing Sparse Image
........ wrote 635482112 bytes to 'super'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 41943040 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
..........................................................................
..........................................................................
..........................................................................
..........................................................................
........................
downloading of 41943040 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing Raw Image
........ wrote 41943040 bytes to 'boot_a'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 41943040 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
..........................................................................
..........................................................................
..........................................................................
..........................................................................
........................
downloading of 41943040 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing Raw Image
........ wrote 41943040 bytes to 'boot_b'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 2621716 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
....................
downloading of 2621716 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing sparse image at offset 9761024
Flashing Sparse Image
........ wrote 56762368 bytes to 'userdata'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 4096 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk

downloading of 4096 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing Raw Image
........ wrote 4096 bytes to 'vbmeta_a'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 4096 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk

downloading of 4096 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing Raw Image
........ wrote 4096 bytes to 'vbmeta_b'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 8388608 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
................................................................
downloading of 8388608 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing Raw Image
........ wrote 8388608 bytes to 'dtbo_a'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 8388608 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
................................................................
downloading of 8388608 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing Raw Image
........ wrote 8388608 bytes to 'dtbo_b'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Starting download of 33554432 bytes
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
..........................................................................
..........................................................................
..........................................................................
..................................
downloading of 33554432 bytes finished
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Flashing Raw Image
........ wrote 33554432 bytes to 'persist'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
** Unrecognized filesystem type **
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Erasing blocks 27648 to 28672 due to alignment
........ erased 524288 bytes from 'misc'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
** Unrecognized filesystem type **
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
** Unrecognized filesystem type **
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk
Erasing blocks 9663488 to 9695232 due to alignment
........ erased 16252928 bytes from 'metadata'
dwc3-generic-peripheral usb@31000000: request 00000000f7f06f00 was not queued to ep1in-bulk

Kindly help me to solve this issue other than any other, because due to this issue I can't even boot my device.

Best Regards,
Aditya T

0 Mattijs Korpershoek 1 day ago in reply to Aditya Tandulwadkar

TI__Intellectual 1435 points

Hello Aditya,

This is a new issue. Please open another ticket for this issue.

0 Aditya Tandulwadkar 1 day ago in reply to Mattijs Korpershoek

Intellectual 470 points

I've created the new thread just now, please help me to resolve this issue asap
Post link: Link

Best Regards,
Aditya T

Processors

Processors forum

AM625: How to control brightness of display using pwm in Android on custom AM625 SOM, using RGB display.