[ADV8005] OSD fails to show on TV

We port ADV8005_VSP_1.81RC1 to an MCU. To replace BF524 on EVAL-AD8005-SMZ board (printed on the silk screen: A0416-2013 REV 0.2, ADV8003 ADVANTIV VIDEO EVALUATION BOARD, the board is equiped with adv7625, adv7842, adv8005.),

1. i2c, spi, and control(reset and others) signals were cut apart from BF524 and connected to the MCU.

2. disconnect IR receiver from BF524 and connect to the MCU so that we can take advantage of SONY remote control, the one shiped in the evaluation kit.

We target at using adv7842 to capture and adv8005 to output. The preliminary tests seem working fine: adv7842 is able to capture video via HDMI and adv8005 is able to get EDID from the screen, do whatever necessary, and output to the TV via HDMI. (Thus, i2c, spi, control signals should be proved OK.)

However, pressing "MENU" key on SONY remote control can't draw OSD on the screen.

In the SPI flash attached to adv8005, we burnt a binary file generated by Blimp 3.6 out of ADV800X OSD\SampleProject\AVR_OSD_DEMO.

We feel clueless because there exist no major errors in the log. Could anybody read my log and suggest directions to debug?

  • 0
    •  Analog Employees 
    on Nov 8, 2014 10:39 AM

    Hi Joel Ding,

    The first four bytes values are the binary identifier value that we set it in project settings.  The last four bytes will give the version

    Best Regards,


  • Hi Jeyasudha.M,

    Exactly! We traced the 1.81RC1 source code and learned that the first 4 bytes must be "00 00 00 01". Otherwise, self-checking would fail.

    However, Blimp version 3.5 generates ddr2_dump.bin with "00 00 00 00" as the beginning 4 bytes. Besides that, what looks meaningful resides right next to the beginning. However, peeking into ddr2_dump.bin, generated with Blimp 3.7 Exp7, packed in the 1.81RC1 source release, it starts with "00 00 00 01" and contains lots of 00 for the first tens of bytes. The difference is obvious.

    What Blimp generates can be used instantly without any post-produce step, right? Post-produce steps can add signatures and reloc sectors. But it is not the case here.

    That's why we suspect a source release must go with a certain Blimp release.

  • 0
    •  Analog Employees 
    on Nov 11, 2014 4:08 PM

    Hi Joel ding,

    After discussion with software team we found that in 1.81RC1 source code,the splash page support updates are added in driver side. so we can not use this code with the blimp 3.5rel, since the driver code will call the splash page api's and those won't be present in the blimp 3.5 code.

    So please use the latest blimp 3.7 version.


    Best Regards,