PROCESSOR-SDK-AM62X: Timetamp isnot changing for kernel Image ,fitimage and customised dts file

Naresh Nakka said:

those image timestamp is not generating

Which exact/specific timestamp are you referring to?

Regards, Andreas

Hi Andreas,

After compiling the yocto build , it shows correct timestamp .

test@test-ThinkCentre-neo-50t-Gen-3:~/yocto/tisdk/build/arago-tmp-default-glibc/deploy/images/am62xx-evm$ ls -l Image*
lrwxrwxrwx 2 test test 96 Jan 22 23:59 Image -> Image--6.1.33+git0+40c32565ca-r0b.arago5_edgeai_0_edgeai_1.psdk3.1-am62xx-evm-20240122182550.bin
-rw-r--r-- 2 test test 21275136 Jan 22 23:59 Image--6.1.33+git0+40c32565ca-r0b.arago5_edgeai_0_edgeai_1.psdk3.1-am62xx-evm-20240122182550.bin
lrwxrwxrwx 2 test test 96 Jan 22 23:59 Image-am62xx-evm.bin -> Image--6.1.33+git0+40c32565ca-r0b.arago5_edgeai_0_edgeai_1.psdk3.1-am62xx-evm-20240122182550.bin

but after flashed the images on the board checked the kernel images which  shows other date

root@am62xx-evm:/home# uname -ar
Linux am62xx-evm 6.1.33-g40c32565ca #1 SMP PREEMPT Thu Jul 6 14:17:24 UTC 2023 aarch64 GNU/Linux
root@am62xx-evm:/home#

Thanks,

Naresh

Naresh Nakka said:

Linux am62xx-evm 6.1.33-g40c32565ca #1 SMP PREEMPT Thu Jul 6 14:17:24 UTC 2023 aarch64 GNU/Linux

The Kernel timestamp isn't changing due to a feature called "reproducible build" enabled by default in all newer Yocto versions. You can learn more about this here: https://www.google.com/search?q=yocto+reproducible+build

Try adding the below to your conf/local.conf file, and see if this solves your concern:

# https://docs.yoctoproject.org/ref-manual/variables.html#term-KERNEL_DEBUG_TIMESTAMPS
KERNEL_DEBUG_TIMESTAMPS = "1"

Regards, Andreas

Hi Andreas,

 Thanks for your quick response.

actually after compiled yocto build. i got the images form this path : ~/yocto/tisdk/build/arago-tmp-default-glibc/deploy/images/am62xx-evm

removed existed images in boot folder of rootfs and copied the below images from this path (~/yocto/tisdk/build/arago-tmp-default-glibc/deploy/images/am62xx-evm) to boot folder.

• Image -> Image--6.1.33+git0+40c32565ca-r0b.arago5_edgeai_0_edgeai_1.psdk3.1-am62xx-evm-20240122182550.bin
• Image--6.1.33+git0+40c32565ca-r0b.arago5_edgeai_0_edgeai_1.psdk3.1-am62xx-evm-20240122182550.bin
•  Image-am62xx-evm.bin 
• fitImage
• fitImage--6.1.33+git0+40c32565ca-r0b.arago5_edgeai_0_edgeai_1.psdk3.1-am62xx-evm-20240122182550.bin
• fitImage-linux.bin--6.1.33+git0+40c32565ca-r0b.arago5_edgeai_0_edgeai_1.psdk3.1-am62xx-evm-20240122182550.bin

with above image device is not booting 

but if i keep "Image-6.1.33-g40c32565ca" this images coming with tisdk-base-image , then its bootig (from where i can get this image form yocto ),

this image (Image-6.1.33-g40c32565ca) is not present in this path ~/yocto/tisdk/build/arago-tmp-default-glibc/deploy/images/am62xx-evm.

whats differnece between  " Image-6.1.33-g40c32565ca " and Image (link) ,  Image-am62xx-evm.bin (link) and Image--6.1.33+git0+40c32565ca-r0b.arago5_edgeai_0_edgeai_1.psdk3.1-am62xx-evm-20240122182550.bin.

from which path of yocto buils  should i take kernel images to boot ?

should also i need to copy fitImage & fitImage..*.bin to boot folder of rootfs ?

could you please explain me .

Thanks,

Naresh

Naresh Nakka said:

from which path of yocto buils  should i take kernel images to boot ?

should also i need to copy fitImage & fitImage..*.bin to boot folder of rootfs ?

You shouldn't manually take things from the build folders. Why don't you re-build your final image and use that?

Regards, Andreas