• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 2 answers
  • Subscribers 100 subscribers
  • Views 830 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Compiler/TDA2SX: Follow VSDK guide reduce Yocto file system size but can not reach about 60MB.

Tao Han
Expert 6415 points
Part Number: TDA2SX

Tool/software: TI C/C++ Compiler

Hi Team:

Customer develop their TDA2Sx system. file system base on website latest 6.00.00.03 (https://processors.wiki.ti.com/index.php?title=Category:Processor_SDK_Linux_Automotive)

VSDK use linux version 3.6 release. 

Develop system is Ubuntu 14.04

first time build total Yocto default J6x filesystem is size is ~1GB. Based on our user guide description use small size file system script build file system tar package about ~150MB.

Could you please share small size of 60MB file system with us or help us double check the file system we generate is wrong or not?

I upload the file system to TI internal BOX. you can download it.

Best Regards!

han tao

  • 0
    TI__Guru** 113810 points

    Hi Tao,

    I remember that the size of this binary was about 60 MB with Vision SDK 3.04 which used PSDKLA 3.04.

    Will try to replicate the instructions with the Vision SDK 3.6 release and the 6.00.00.03 Linux SDK and get back to you. You can expect to hear from me by Tuesday.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    TI__Expert 6415 points

    Hi Karthik:

    Thanks a lot for help us double check this problem.

    Has share you the file system we generate from 6.00.00.03. Please help us co-check with your side.

    Best Regards!

    Han Tao

  • 0 in reply to Tao Han
    TI__Mastermind 30480 points

    Hi Tao,

    VisionSDK 3.02 to 3.07 were based on PSDKLA3.0x(kernel 4.4 and u-boot 2016.05).

    VisionSDK 3.08 is based on PSDKLA6.00(Kernel 4.19 and u-boot 2019.01).

    VisionSDK3.7 has filesystem size of ~90MB always and not ~60MB.

    http://software-dl.ti.com/processor-sdk-vision/esd/TDAx/vision-sdk/03_07_00_00/index_FDS.html

    VisionSDK3.08 filesystem is ~120MB

    http://software-dl.ti.com/processor-sdk-vision/esd/TDAx/vision-sdk/latest/index_FDS.html

    We have disabled exactly same recipes here but size is not coming down too 90MB.

    Can you let us know your usecase, we can disable few more recipes based on your usecase. 

    For example, if gstreamer is not required, we can disable all gstreamer recipes and it will further reduce the filesystem size.

    Thanks

    RamPrasad

  • 0 in reply to Ramprasad
    Expert 1805 points

    Hi RamPrasad,

           Thanks for your help. Now I have used the tisdk-rootfs-image-dra7xx-evm_vsdk_3_7.tar.xz for testing.The file system has met our size requirements, but the kernel startup time is too slow, espectially when it printfs "Started tiipclad-daemon.service.", after 6s, it shows the logo"Arago Project", I don't know what happen,  how I save the time?As follows:

    20200225_11:39:33Welcome to Arago 2016.12!
    20200225_11:39:33
    20200225_11:39:34[ SKIP ] Ordering cycle found, skipping alignment.service
    20200225_11:39:34[ OK ] Started Forward Password Requests to Wall Directory Watch.
    20200225_11:39:34[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
    20200225_11:39:34[ OK ] Listening on Syslog Socket.
    20200225_11:39:34[ OK ] Listening on udev Control Socket.
    20200225_11:39:34[ OK ] Listening on Journal Socket (/dev/log).
    20200225_11:39:34[ OK ] Listening on udev Kernel Socket.
    20200225_11:39:34[ OK ] Listening on Journal Socket.
    20200225_11:39:34[ OK ] Reached target Swap.
    20200225_11:39:34[ OK ] Started Dispatch Password Requests to Console Directory Watch.
    20200225_11:39:34[ OK ] Reached target Paths.
    20200225_11:39:34[ OK ] Reached target Remote File Systems.
    20200225_11:39:34[ OK ] Created slice User and Session Slice.
    20200225_11:39:34[ OK ] Created slice System Slice.
    20200225_11:39:34 Mounting Temporary Directory...
    20200225_11:39:34 Starting Setup Virtual Console...
    20200225_11:39:34 Starting Load Kernel Modules...
    20200225_11:39:34 Starting Create Static Device Nodes in /dev...
    20200225_11:39:34[ OK ] Created slice system-serial\x2dgetty.slice.
    20200225_11:39:34[ OK ] Created slice system-getty.slice.
    20200225_11:39:34 Starting Remount Root and Kernel File Systems...
    20200225_11:39:34 Starting Journal Service...
    20200225_11:39:34[ OK ] Reached target Slices.
    20200225_11:39:34[ OK ] Listening on Network Service Netlink Socket.
    20200225_11:39:34[ OK ] Mounted Temporary Directory.
    20200225_11:39:34[ OK ] Started Journal Service.
    20200225_11:39:34[ OK ] Started Setup Virtual Console.
    20200225_11:39:34[FAILED] Failed to start Load Kernel Modules.
    20200225_11:39:34See 'systemctl status systemd-modules-load.service' for details.
    20200225_11:39:34[ OK ] Started Create Static Device Nodes in /dev.
    20200225_11:39:34[ OK ] Started Remount Root and Kernel File Systems.
    20200225_11:39:35 Starting udev Coldplug all Devices...
    20200225_11:39:35 Starting udev Kernel Device Manager...
    20200225_11:39:35[ OK ] Reached target Local File Systems (Pre).
    20200225_11:39:35 Mounting /var/volatile...
    20200225_11:39:35 Mounting /media/ram...
    20200225_11:39:35 Starting Apply Kernel Variables...
    20200225_11:39:35 Starting Flush Journal to Persistent Storage...
    20200225_11:39:35[ OK ] Mounted /var/volatile.
    20200225_11:39:35[ OK ] Mounted /media/ram.
    20200225_11:39:35[ OK ] Started udev Kernel Device Manager.
    20200225_11:39:35[ OK ] Started Apply Kernel Variables.
    20200225_11:39:35[ OK ] Started Flush Journal to Persistent Storage.
    20200225_11:39:35 Starting Load/Save Random Seed...
    20200225_11:39:35[ OK ] Reached target Local File Systems.
    20200225_11:39:35 Starting Create Volatile Files and Directories...
    20200225_11:39:35[ OK ] Started Load/Save Random Seed.
    20200225_11:39:35[ OK ] Started Create Volatile Files and Directories.
    20200225_11:39:36[ OK ] Found device /dev/ttyS0.
    20200225_11:39:36[ OK ] Started udev Coldplug all Devices.
    20200225_11:39:36 Starting Update UTMP about System Boot/Shutdown...
    20200225_11:39:36 Starting Network Time Synchronization...
    20200225_11:39:36[ OK ] Started Network Time Synchronization.
    20200225_11:39:36[ OK ] Started Update UTMP about System Boot/Shutdown.
    20200225_11:39:36 Starting Synchronize System and HW clocks...
    20200225_11:39:36[ OK ] Reached target System Time Synchronized.
    20200225_11:39:37[FAILED] Failed to start Synchronize System and HW clocks.
    20200225_11:39:37See 'systemctl status sync-clocks.service' for details.
    20200225_11:39:37[ OK ] Reached target System Initialization.
    20200225_11:39:37[ OK ] Started Daily Cleanup of Temporary Directories.
    20200225_11:39:37[ OK ] Reached target Timers.
    20200225_11:39:37[ OK ] Listening on dropbear.socket.
    20200225_11:39:37[ OK ] Listening on D-Bus System Message Bus Socket.
    20200225_11:39:37[ OK ] Reached target Sockets.
    20200225_11:39:37[ OK ] Reached target Basic System.
    20200225_11:39:37[ OK ] Started D-Bus System Message Bus.
    20200225_11:39:37[ OK ] Started System Logging Service.
    20200225_11:39:37 Starting Login Service...
    20200225_11:39:37 Starting rc.pvr.service...
    20200225_11:39:37 Starting Network Service...
    20200225_11:39:37 Starting Permit User Sessions...
    20200225_11:39:37[ OK ] Started Kernel Logging Service.
    20200225_11:39:37[ OK ] Started Network Service.
    20200225_11:39:37[ OK ] Started rc.pvr.service.
    20200225_11:39:37[ OK ] Started Permit User Sessions.
    20200225_11:39:38[ OK ] Started Serial Getty on ttyS0.
    20200225_11:39:38[ OK ] Started Getty on tty1.
    20200225_11:39:38 Starting weston.service...
    20200225_11:39:38[ OK ] Reached target Network.
    20200225_11:39:38 Starting Network Name Resolution...
    20200225_11:39:38[ OK ] Started weston.service.
    20200225_11:39:38[ OK ] Started Login Service.
    20200225_11:39:38[ OK ] Started Network Name Resolution.
    20200225_11:39:38 Starting telnetd.service...
    20200225_11:39:38 Starting tiipclad-daemon.service...
    20200225_11:39:38[ OK ] Started telnetd.service.
    20200225_11:39:38[ OK ] Started tiipclad-daemon.service.
    20200225_11:39:44
    20200225_11:39:44 _____ _____ _ _
    20200225_11:39:44| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
    20200225_11:39:44| | _| .'| . | . | | __| _| . | | | -_| _| _|
    20200225_11:39:44|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
    20200225_11:39:44 |___| |___|
    20200225_11:39:44
    20200225_11:39:44Arago Project http://arago-project.org dra7xx-evm ttyS0
    20200225_11:39:44
    20200225_11:39:44Arago 2016.12 dra7xx-evm ttyS0
    20200225_11:39:44

  • 0 in reply to user6229311
    TI__Guru** 113810 points

    Hi,

    The question regarding the overall boot time needs to be looked into closely and you can determine the systemd services that are running by default and then optimize/reorder the services based on your requirement.

    And, also, the original question has been answered by the previous response from TI, and I would like to request you to analyze the start time and then submit a different ticket with additional details.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 1805 points

    Hi Karthik, 

            I post the question at this https://e2e.ti.com/support/processors/f/791/t/883278, please help me to analysis it, thank you very much.

  • 0 in reply to user6229311
    TI__Expert 6415 points

    Hi Karthik:

    Has download you provided new version of VSDK filesystem. customer can run their application at new filesystem now.

    Best Regards!

    Han Tao

  • 0 in reply to Karthik Ramanan
    Expert 1805 points

    Hi Karthik,

           I use what you supply about the targetfs3.7, when I do earlyboot, the IPC run error, as follows:

    root@dra7xx-evm:/opt/vision_sdk# ./apps.out;
    [HOST] OSA: MEM: 0: Mapped 0xa0100000 to 0xb6958000 of size 0x00100000
    [HOST] OSA: MEM: 1: Mapped 0x84203000 to 0xa1c58000 of size 0x14d00000
    [HOST] OSA: MEM: 2: Mapped 0xb0000000 to 0x91c58000 of size 0x10000000
    [HOST] OSA: MEM: 3: Mapped 0xa0200000 to 0x91b98000 of size 0x00040000
    [HOST] OSA: MEM: 4: Mapped 0xa02c0000 to 0x91bd8000 of size 0x00080000
    [HOST] OSA: MEM: 5: Mapped 0x00000000 to 0x00000000 of size 0x00000000
    [HOST] OSA: HOST Remote Log Shared Memory @ 0xa024f140
    [HOST] OSA: DSP1 Remote Log Shared Memory @ 0xa02769e0
    [HOST] OSA: DSP2 Remote Log Shared Memory @ 0xa029e280
    [HOST] OSA: EVE1 Remote Log Shared Memory @ 0xa02c5b20
    [HOST] OSA: EVE2 Remote Log Shared Memory @ 0xa02ed3c0
    [HOST] OSA: EVE3 Remote Log Shared Memory @ 0xa0314c60
    [HOST] OSA: EVE4 Remote Log Shared Memory @ 0xa033c500
    [HOST] OSA: IPU2 Remote Log Shared Memory @ 0xa0363da0
    ASSERT (system_ipc.c|System_ipcInit|119)
    [HOST] [HOST ] 15.599158 s: SYSTEM: System A15 Init in progress !!!
    [HOST] [HOST ] 15.599249 s: SYSTEM: IPC: Init in progress !!!
    [HOST] [HOST ] 15.599249 s: SYSTEM: IPC: Notify init in progress !!!
    [HOST] [HOST ] 15.599310 s: SYSTEM: IPC: [IPU2] socket bind failed (Invalid argument, 22) !!!
    [HOST] [HOST ] 15.599310 s: SYSTEM: IPC: [IPU2] Notify RX channel create failed (endpoint = 81) !!!
    [HOST] [DSP1 ] 1.017476 s: ***** DSP1 Firmware build time 18:45:17 Mar 18 2020
    [HOST] [DSP1 ] 1.017537 s: *** SYSTEM: CPU Frequency <ORG = 600000000 Hz>, <NEW = 600000000 Hz>
    [HOST] [DSP1 ] 1.017812 s: SYSTEM: System Common Init in progress !!!

    the log file here:/cfs-file/__key/communityserver-discussions-components-files/791/Serial_2D00_ttyUSB3_2D00_03_2D00_18_2D00_19_2D00_55_2D00_09.log

    It seems the targets missed some lib files, when I use tisdk-rootfs-image-dra7xx-evm_vsdk_3_6.tar.xz, it's OK.

    Could you help me ?

    Regards,

    Jason

  • 0 in reply to user6229311
    TI__Mastermind 30480 points

    Hi Jason,

    Please file a new thread for this issue since the original issue of filesystem reduction is already resolved.

    Thanks

    RamPrasad