@Chris_Kang Is it executed according to the above
Yes, I did it.
In script, āhttps://public.amlogic.binaries.baylibre.com/ci/vendor_packages/20241217/extract-yukawa_devices-20241217.tgz ā should be downloaded. but I could not access it with curl, wget and browser as well. is it my internet or machine problem?
Does the official touch screen TS050 work well in Android mainline?
TS050 panel support code is already in Linux 6.1(common/drivers/gpu/drm/panel/panel-khadas-ts050.c)
I build and load this module, no error return and nothing print in dmesg
Maybe mipi dsi driver and dts is missing
Is any guide for bringup the TS050 touch screen?
AOSP does not support TS050 accessories. Sorry
@xiong.zhang @nadales ,
Can you provide some assistance, how did you fixed this error while flashing AOSP images on device emmc:
Flashing Raw Image
ā¦ wrote 33554432 bytes to āvendor_boot_bā
** Bad device specification mmc init_boot_a_a **
** Bad device specification mmc init_boot_a_a **
Couldnāt find partition mmc init_boot_a_a
WARNING: unknown variable: is-logical
Starting download of 8388608 bytes
ā¦
downloading of 8388608 bytes finished
Flashing Raw Image
ā¦ wrote 8388608 bytes to āinit_boot_aā
** Bad device specification mmc init_boot_b_a **
** Bad device specification mmc init_boot_b_a **
Couldnāt find partition mmc init_boot_b_a
WARNING: unknown variable: is-logical
Starting download of 8388608 bytes
ā¦
downloading of 8388608 bytes finished
Flashing Raw Image
ā¦ wrote 8388608 bytes to āinit_boot_bā
** Bad device specification mmc userdata_a **
** Bad device specification mmc userdata_a **
Couldnāt find partition mmc userdata_a
WARNING: unknown variable: is-logical
Starting download of 2642220 bytes
ā¦
downloading of 2642220 bytes finished
Flashing sparse image at offset 10024448
Flashing Sparse Image
ā¦ wrote 56786944 bytes to āuserdataā
** Bad device specification mmc vbmeta_a_a **
** Bad device specification mmc vbmeta_a_a **
Couldnāt find partition mmc vbmeta_a_a
WARNING: unknown variable: is-logical
Starting download of 8192 bytes
downloading of 8192 bytes finished
It would be of great help. Thanks.
@Puyush_Gupta
Hello, are you using Ubuntu to burn the system?
Yes, my SOC board is connected with Ubuntu machine.
Also, after enabling fastboot in u-boot using āfastboot 0ā,
when I perform āfastboot devicesā or āsudo fastboot devicesā:
I get:
ā??? fastbootā as result.
Do you have fastboot downloaded? You can use the image I uploaded which contains fastboot.
I used these commands to download fastboot:
sudo apt install android-tools-fastboot
sudo apt-get install android-sdk-platform-tools-common
Is the error of BAD DEVICE SPECIFICATION related to fastboot or uart debug serial?
You can try the fastboot I uploaded
Are you pointing at āVIM3 userdebugā tar thing? If yes, how can I generate those other than downloading? Like I want a generic way so that others can also do this similary as I need to document it for general device also. Can you please enlighten me for that.
Thank you.
@Puyush_Gupta Download the latest burning package, there will be relevant files after decompression
@xiong.zhang
Ok. Also, When I run my lunch command to build Android, I got this:
puyush@puyush-HP-Z2-Tower-G9-Workstation-Desktop-PC:~/10_01_00/ti-aosp-15$ lunch j784s4-ap3a-userdebug
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=15
TARGET_PRODUCT=j784s4
TARGET_BUILD_VARIANT=userdebug
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a72
HOST_OS=linux
HOST_OS_EXTRA=Linux-6.8.0-59-generic-x86_64-Ubuntu-22.04.5-LTS
HOST_CROSS_OS=windows
BUILD_ID=AP4A.250105.002.A1
OUT_DIR=out
Here, HOST_CROSS_OS is windows. Is this could be issue if you could suggest?
Hello, HOST_CROSS_OS=windows is printed normally. The log below is the lunch log of AOSP Android 14. Are you using the Android 15 code?
PLATFORM_VERSION_CODENAME=Baklava
PLATFORM_VERSION=Baklava
TARGET_PRODUCT=yukawa
TARGET_BUILD_VARIANT=userdebug
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a53
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.15.0-197-generic-x86_64-Ubuntu-18.04.6-LTS
HOST_CROSS_OS=windows
BUILD_ID=MAIN
OUT_DIR=out
YES Iām using Android 15
Sorry, our AOSP only supports 14, not 15.
our AOSP means? Like in general way or you mean your device donāt support AOSP? I am using some other device J784s4. Will this be applicable for this as well?
Arenāt you using the flash package we uploaded? Our VIM3 only supports Android 14
Initially as I told, I was using fastboot by downloading itās packaging using sudo commands. The package you have uploaded, I was about to try but now as your package only supports Android 14 but Iām working on Android 15.
Can you help me giving me direction what could be the reason for the issue of āBad device specificationsā stuff. Is it error because of fastboot or uart debug serial or is flashing happening in some other partition like there is warning as you can see in log: āWARNING: unknown variable: is-logicalā
Hello, we have not cooperated with Google on Android 15, so we cannot provide you with any guidance. We will cooperate with Google on Android 16 this year, so please follow the follow-up.