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.

RTOS/TDA2PXEVM: Flashing Vision SDK images using DFU utility.

Part Number: TDA2PXEVM
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

Hi All,

I went through a training slide training.ti.com/am57x-dra7x-dfu-boot-mode-with-linux-host for flashing images using DFU utility.We have the following queries regarding flashing of images:

1)As per our current project requirement, we need to flash TI's Vision SDK images MLO and Appimage through DFU utility.
Is this feasible?If this is feasible can anyone let me know what changes will be required in omapboot utility.

2)Can we flash QSPI using SD Card interface.With this there is also a requirement to change the memory map of QSPI as we need more than one partition in QSPI to keep the redundant images and some config parameters.

Can anyone please help me regarding the above queries?

Regards,
Deepika

  • Hi,

    Please go through section 3.6 of below userguide
    vision_sdk\docs\UserGuides\VisionSDK_UserGuide_TDA2px.pdf

    Regards,
    Anuj
  • Hi Anuj,

    Thanks for your reply.
    The section 3.6 of VisionSDK_UserGuide_TDA2px.pdf relates to QSPI flash. My query is that, if we keep redundant images in another partition,how to make sure that with which partition we need to boot. Also how to access another QSPI partition for saving configuration data.

    I had one more query regarding using DFU using USB utility for flashing Sysbios images. Can anyone please explain me if this is feasible.

    Regards,
    Deepika
  • Hi Deepika,

    What you mean by the QSPI partition? QSPI memory is accessed as a flat memory.
    For VSDK images, MLO and the App images are placed at a fixed offsets in the QSPI flash memory.
    MLO starting from offset 0, Application Image starting from offset 0x80000.

    If you want to read any region of the QSPI memory, you can do so in the memory mapped mode of QSPI,
    and access the memory content by CPU read of address from 0x5c000000 to 0x5FFF FFFF (64 MB region).
    provided the QSPI is configured memory mapped mode properly.

    To write you need to use one of the flash writer application and write at specific offset in the QSPI memory.

    Regards,
    Prasad
  • Hi Prasad ,

    Thanks for your reply.
    Can we keep another set of Appimage and MLO(for redundant images) in QSPI memory at specific offset,and copy them at address 0 and 0x80000 using QSPI application and not by CCS( using flash writer application)

    Regards,
    Deepika
  • Hi Deepika,

    Yes, you can do that. But note that to write to the flash memory you need to first erase the block/sector and write them using the flash write commands one page at a time.
    Check the implementation inside the flash writer, and you can add these changes in your application and update the flash content from your application.

    Regards,
    Prasad

  • Hi Prasad,

    I have still one query regarding the flashing of data using DFU as it is available for Linux images but we need it for VSDK images(Appimage and MLO) as mentioned in this link training.ti.com/am57x-dra7x-dfu-boot-mode-with-linux-host
    Can anyone please help me on this.

    Regards,
    Deepika
  • Deepika,

    The SBL in the VSDK does not support the usb boot mode.

    Regards,
    Prasad