• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 459 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.

Original question:

Linux/DRA77P: Fastboot not achieved

PROCESSOR-SDK-DRA7X: How to obtain the readproc tool source code?

lijie yang
Prodigy 45 points

Part Number: PROCESSOR-SDK-DRA7X

Hi Ti Expert：

    The readproc tool can convert units into milliseconds，Some operating systems do not have readproc tools，Can you send the readproc tool source code to me?

Or, how can I compile the readproc tool?

    Thanks！

  • 0 in reply to Karthik Ramanan
    Prodigy 45 points

    Thank you very much for your reply. I'll check it out. If I have any questions, I'll consult you again.

  • 0 in reply to Karthik Ramanan
    Prodigy 45 points

    Hi Expert：

    I have a few questions. Please help me explain it：

    1. 1. Why does the rom_handoff_time variable need to be initialized with __attribute__ ((section(".data"))) ? Why can't it be the same as u32 mmc_init_dur = 0? I don't understand here.

    u32 rom_handoff_time __attribute__ ((section(".data"))) = 1;
    u32 heap_init_dur __attribute__ ((section(".data"))) = 1;

    2. On dra7xx SOC platform, 0x4AE04030 is a 32KHZ counter. If I use TDA4 platform or other platforms, how can I determine the register address of the counter?

    #define COUNTER32K_CR 0x4AE04030

    3. If the system needs to use uboot during startup, how should we pass the measured time to the kernel?（Not  single stage boot）

    Thanks a lot！

  • 0 in reply to lijie yang
    TI__Guru** 113810 points

    Hi,

    lijie yang said:

    1. 1. Why does the rom_handoff_time variable need to be initialized with __attribute__ ((section(".data"))) ? Why can't it be the same as u32 mmc_init_dur = 0? I don't understand here.

    u32 rom_handoff_time __attribute__ ((section(".data"))) = 1;
    u32 heap_init_dur __attribute__ ((section(".data"))) = 1;

    Can you please provide where you are looking at for this code?

    lijie yang said:
    2. On dra7xx SOC platform, 0x4AE04030 is a 32KHZ counter. If I use TDA4 platform or other platforms, how can I determine the register address of the counter?

    There is no equivalent counter that runs from SoC power on in the TDA4 platform. You will need to initialize your our TIMER in the bootloader but this will not include the ROM code execution time or until this timer has started.

  • 0 in reply to Karthik Ramanan
    Prodigy 45 points

    Hi Expert:

    Thanks very much for your reply.

    1. Can you please provide where you are looking at for this code?

    --> I found it in this link : http://review.omapzoom.org/#/c/38260/5/common/spl/spl.c   

    2. There is no equivalent counter that runs from SoC power on in the TDA4 platform. You will need to initialize your our TIMER in the bootloader but this will not include the ROM code execution time or until this timer has started.

    -->I want to measure the startup time on tda4; (from power-on to kernel startup), how should I measure? Do you have any good suggestions?