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.

EZSDK 5_04_00_11 u-boot

Hi,

Our customer would like to display some characters(message, revision info. etc) on LCD screen while u-boot. Customer uses DM814x/AM387x EVM.

But customer can't display characters correctly on LCD screen while u-boot by Hsync and Vsync synchronous issue.

 

Customer uses the below firmware as the M3 firmware.

ti-ezsdk_dm814x-evm_5_04_00_11\board-support\u-boot-2010.06-psp04.04.00.01\include\ti81xx_vpdma_firmware.h

Customer tried to display characters on LCD using u-boot software while u-boot. The horizental position was shifted 8pixels to the right on LCD. And also characters scrolled to the up, those are never stopped scrolling. So customer modified the data size on descriptor. But it was no effect.

Next, customer compared u-boot descreptor with linux descreptor. There is only the data transfer function in u-boot  descreptor. But there is the interrupt function (Sync on Client, Send Interrupt) in linux  descreptor. So customer added the interrupt function to u-boot descreptor. The result is no characters on LCD. The display was black.

Then customer tried to use linux M3 firmware. But they can't use it by different file format.

What is the wrong for displayin characters on LCD while u-boot? Please advise me.

Best regards,

Michi

 

  • Michi-san,

    The the characters are scrolling up, mostly it might be because of in-correct VPDMA configuration. We've seen this issue before in u-boot. I don't remember the exact solution of this as it was done almost an year before. 

    Interrupt support is not really required to support this. It all depends on your VPDMA list configuration. Display will turn black, if the handler doesn't take care of the VPDMA list properly. 

  • Dear Renjith-san,

    Thank you for your information.

    Does anyone know more information regarding this issue? I would like to know the cause and solution.

    Please advise me.

    Best regards,

    Michi

     

  • Dear Michi-san,

    One of my team member has done boot logo in u-boot almost one year back. I don't have the exact details with me. Can you share the code where it the logo or characters is scrolling to renjith.thomas@pathpartnertech.com? I don't need the code with interrupt support. 

    Is it enough if we solve the scrolling issue? Also please send couple of snapshots, when this issue occurs.

  • Hi, Renjith.

    I am also interested in a boot logo on lcd in u-boot in dm8148. Can you give some help? Can you confirm, that M3 firmware in uboot is capable to show logo on dvo2 (lcd) and it only needs some modifications in uboot?

    Best regards,

    Alexander Vasiljev.

  • Hi Alexander,

    We have done the same thing before. By M3 firmware are you referring to VPDMA firmware or M3 binary running in M3 core. 

    If it is M3 binary, then you don't need M3 binary to be running from M3 core, instead you can configure the HDVPSS subsystem from A8 in u-boot itself. Basically you've to migrate the code from M3 to A8. This is a good amount of work.

    Is this your custom platform or EVM?

  • Hi Renjith.

    I talked about firmware in "ti-ezsdk_dm814x-evm_5_04_00_11\board-support\u-boot-2010.06-psp04.04.00.01\include\ti81xx_vpdma_firmware.h". I was sure that is M3 firmware. Currently i am still waiting for documentation, which is spread under NDA, so i don't have exact notion about how HDVPSS system works. Now i want to know should i ask TI for source code of the firware, which is currently used to show boot logo on hdmi, or can i use it as is.

    My board is custom, but it is almost as EVM.

    Best regards,

    Alexander Vasiljev.

  • The firmware inside vpdma_firmware.h is not M3 side binary. This is a firmware required by VPDMA a list manager. This is a small firmware, whereas the binaries for M3 subs-system has a size of around 4+ MB and comes with an extension of .xem3 (typically)

    If you are particular about boot logo from u-boot, we can help you out. Please do mail me, and we can have the discussion offline.

  • Hi TI friend,

        Now I meet the Similar problem: I can show logo from uboot start up both on the lcd and hdmi by using the DM814x EZSDK 5_05_02_00 on dm8148 platform. However, in the uboot, it loads M3 firmware and uses vpdma to show the logo, it can't show the logo always, just limited by setting time. And I don't have any document about vpdma.

        Could you give me a kind of help to tell me what can I do to show the logo always not limited by setting time?

        Could you share the relevant register information?

    Thanks!

  • Harry,

    There is a problem if you extend the logo further. The M3 firmware load fails as it gets stuck after seeing the list manager seems to be busy. There is modification required from M3 driver to enable logo continuously.

  • Hi Renjith,

    Thank you for your reply.

    I want to show the logo continuously as you said, but how can I do to attain it. I use vpdmaFirmware_1AD to load to M3, however I don't have the source codes of vpdmaFirmware_1AD.

    These days I made various attempts to solve it, but I failed.

    Could you please give me a kind of hand? It is really very important to me, and I must to solve the issue.

    Maybe you can give me a vpdma firmware instead of  vpdmaFirmware_1AD with the modification, could you please?

    Looking forward to your reply.

    Thank you!

  • Harry,

    Its not easy to solve it. You'll have to license the HDVPSS firmware code from TI and then modify it. There is good amount of effort in solving this. 

    Regards,
    Renjith 

  • Hi Renjith,

    We have EZSDK and DVR RDK, if we want to achieve it in uboot, could you please show the way and share some useful information? Whether I need to load M3 in uboot? But how I can?  Please forgive my confused!

    Thank you!

  • Harry,

    You'll need to license the HDVPSS source code from TI. Then you'll have to debug and resolve the issue there and use the updated binary. You'll have to talk to your TI FAE to get the source package. You'll have to go through the licensing formalities.