<br><br><div class="gmail_quote">On Wed, Aug 22, 2012 at 9:10 AM, Henrik Nordström <span dir="ltr"><<a href="mailto:henrik@henriknordstrom.net" target="_blank">henrik@henriknordstrom.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
tis 2012-08-21 klockan 15:58 +0800 skrev Piyush Verma:<br>
<div class="im"><br>
> According to my experience script.bin have no effect.<br>
<br>
</div>u-boot mmc by default loads script.bin, nothing else.<br></blockquote><div><br>got it. So it's loaded and used by u-boot.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I have not looked into the script used for creating sd cards, but maybe<br>
it is leaving an old environment of yours on the card? If there is a<br>
saved environment on the card then this overrides the default built in<br>
environment completely.<br></blockquote><div><br>Right currently that was the situation.<br>After clean flashing i can see fatload mmc 0 0x43000000 script.bin;<br>So based on current situation what I learn that kernel reads script.bin (Configuration File) from 0x43000000 fix address and act.<br>
<br>I have also replaced evb.bin from script.bin.<br>But still after success boot and success driver load HDMI not working on MELE100.<br>Where without any physical changes If I insert working sd card then HDMI working.<br>
<br>Is it something with driver load sequence ?<br><br>Any clear process that follow step 1 2 3 4 and it works?<br><br>Recently any body have tested nightly build image with HDMI ?<br><br></div></div><br>-- <br>Thanks & Regards<br>
<br>Piyush Verma<br><br><br>