• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 194 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.

EZSDK 5.03.01.15 U-Boot and VPSS errors

David Paden
Expert 1925 points

So, I am currently using the stock u-boot.bin that shipped on the DM8148 Eval Kit SD Card, but using the HDVPSS pre-built binary images from the EZSDK.  Everything works fine. 

However, I want to switch to the quick_mmc version of u-boot.  When I rebuild u-boot from the EZSDK sources and boot, I get the below errors after the HDVPSS firmware is loaded and the VPSS module tries to load:

notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0

(repeated many times)

I see a lot of posts regarding these errors for the DM8148, but none of the "solutions" are clear to me and many issues are not resolved.  There is much talk about modifying the memory maps for various board revisions...but I don't want to modify the memory maps...they are working fine with the original u-boot.bin image.  So the problem must be relative to the EZSDK version of u-boot.

So, what must I change in the u-boot sources to fix this problem?  How can I make the u-boot binary setup everything like the original SD Card?  What is the difference between the SD Card version and the EZSDK version?

I am still using the stock SD boot.scr (notifyk.vpssm3_sva=0xBF900000)

I have already tried changing the LISA settings from:

#define PG2_1_DMM_LISA_MAP__0        0x0
#define PG2_1_DMM_LISA_MAP__1        0x0
#define PG2_1_DMM_LISA_MAP__2        0x0
#define PG2_1_DMM_LISA_MAP__3        0x80640300

to:

#define PG2_1_DMM_LISA_MAP__0        0x0
#define PG2_1_DMM_LISA_MAP__1        0x0
#define PG2_1_DMM_LISA_MAP__2        0x80540300
#define PG2_1_DMM_LISA_MAP__3        0xA0540300

but this doesn't resolve the problem.  I also tried separately changing the boot.scr to use notifyk.vpssm3_sva=0xBF900000, but my understanding is that this is not required in the EZSDK version of the firmware images.

  • 0
    TI__Expert 4245 points

    Hi,

    David Paden said:

    So, I am currently using the stock u-boot.bin that shipped on the DM8148 Eval Kit SD Card, but using the HDVPSS pre-built binary images from the EZSDK.  Everything works fine. 

    However, I want to switch to the quick_mmc version of u-boot.  When I rebuild u-boot from the EZSDK sources and boot, I get the below errors after the HDVPSS firmware is loaded and the VPSS module tries to load:

    notify_shm_drv_sendevent failed! status = 0xfffffff0
    notify_send_event failed! status = 0xfffffff0

    (repeated many times)

    I see a lot of posts regarding these errors for the DM8148, but none of the "solutions" are clear to me and many issues are not resolved.  There is much talk about modifying the memory maps for various board revisions...but I don't want to modify the memory maps...they are working fine with the original u-boot.bin image.  So the problem must be relative to the EZSDK version of u-boot.

    The quick_mmc version of boot assumes a memory map that's different from the one that the EZSDK uses. In addition, the quick_mmc configuration has not been tested with a full video pipeline but only verified with a vanilla PSP kernel.

    I'm sure that's why you would have been given the suggestion to look at the memory map. The reason for the difference is that the PSP (Uboot and Kernel only) are components that go into the EZSDK, which includes several other software components. In order to integrate them into a single package the memory map is tuned at the EZSDK. The only way I can see for using quick_mmc is to set the HDVPSS address in the u-boot configuration itself.