<div dir="ltr"><div dir="ltr"><br><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 27, 2019 at 4:00 PM Nils Hölscher <<a href="mailto:nilhoel1@gmail.com">nilhoel1@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi Vijay,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 27 May 2019 at 12:15, Vijay Kumar Banerjee <<a href="mailto:vijaykumar9597@gmail.com" target="_blank">vijaykumar9597@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 27, 2019 at 1:24 PM Nils Hölscher <<a href="mailto:nilhoel1@gmail.com" target="_blank">nilhoel1@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I tried to rout the PRUs pins via device tree overlay this week.</div><div>Sadly I wasn't able to produce results on linux with this method.</div><div>Please check my blog post concerning this issue.</div><div><a href="https://nilshoel.home.blog/2019/05/27/setting-up-prus-pins-via-device-tree-files/" target="_blank">https://nilshoel.home.blog/2019/05/27/setting-up-prus-pins-via-device-tree-files/</a><br></div><div><br></div><div>It would be great if someone having experience with device tree overlay could get me some feed back.</div><div>I will now move on to setting up RTEMS and porting the drivers.</div><div><br></div></div></blockquote><div>Hello Nils,</div><div><br></div><div>I read your blog and had a look at the overlay. From first look at the</div><div>overlay I noted that you're using `target-path`. I think target-path holds</div><div>a path string like "/path" instead of a reference to your pruss. Maybe</div><div>there should be a `target` field and you'll have to seth the target path</div><div>manually or just remove it if you're not using it. </div><div><br></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div></div><div>A few pointers that helped me in general, to get an overlay working :</div><div> * always check for the -@ option while compiling with dtc</div></div></div></blockquote><div>I am compiling on the bone with: dtc -O dtb -I dts -o /lib/firmware/PRU-GPIO-EXAMPLE-00A0.dtbo -b 0 -@ PRU-GPIO-EXAMPLE-00A0.dts </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div> * before applying using a bootscript in u-boot, it might be a good</div><div> idea to use the fdtoverlay tool ( in linux host) and apply it on your</div><div> host system. </div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div> * If it applies well, then just decompile the dtb with the </div><div> dtc and have a look at the device you were targeting, if your changes</div><div> look nice and so far you didn't get any error during the building, open</div><div> u-boot and manually apply overlay using `fdt apply`.</div><div><br></div><div>With a quick look these pointers might be helpful. I'm working on porting</div><div>the i2c stack from FreeBSD to RTEMS and have used an overlay for the</div><div>path and compatibility. Hope these pointers were of some help.</div><div>I can explain any of the points above if they're not clear and you can post</div><div>the error log here as well ( if you luckily get proper error messages ;-) )</div><div><br></div></div></div></blockquote><div>Thank you for these helpful notes.</div><div>I will try them this week and report back. </div><div>It would be nice if you could tell me the command you use for decompiling the files.</div><div><br></div></div></div></blockquote><div>Just reverse the options in dtc something like :<br>`dtc -I dtb -O dts -o REV_PRU-GPIO-EXAMPLE-00A0.dts PRU-GPIO-EXAMPLE-00A0.dtb`<br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div></div><div>Best,</div><div>Nils</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div></div><div>Regards,</div><div>Vijay</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div>Best regards,</div><div>Nils Hölscher</div></div>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></blockquote></div></div>
</blockquote></div></div>
</blockquote></div></div>