<div dir="ltr"><div class="gmail_quote"><div><span class="gmail_default" style="font-size:small">Hello,</span> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Actually I followed this document<br>
<a href="https://docs.rtems.org/branches/master/user/start/bsp-build.html#quickstartbspbuild-manual" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/start/bsp-build.html#quickstartbspbuild-manual</a><br>
to<br>
build bsp manually<br>
as mentioned in the "GSoc getting started" blog.<br>
<br>
Also yes when I run "./waf" command "Waf: Leaving directory<br>
<span class="gmail_default" style="font-size:small"></span>`/home/rohan/devlopment/src/rtems/build/sparc/erc32'<br>
" this was the final output as you said.<br>
<br>
But I am actually stuck in running Hello world program<br>
<a href="https://docs.rtems.org/branches/master/user/start/gsoc.html#prove-you-can-work-on-rtems" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/start/gsoc.html#prove-you-can-work-on-rtems</a><br>
this<br>
document says to run "make" command but the folder "/build/b-erc32" is<br>
empty. So I was confused about how to run Hello world.<br></blockquote><div><span class="gmail_default" style="font-size:small">The document is incorrect. You have to run ./waf in the RTEMS source directory</span></div><div><span class="gmail_default" style="font-size:small">which should be</span></div><div><span class="gmail_default" style="font-size:small"><span class="gmail_default"></span>`/home/rohan/devlopment/src/rtems'</span></div><div><span class="gmail_default">as per the output from waf.</span></div><div><br></div><div><div class="gmail_default" style="font-size:small">Once that is done you should find your executable in </div><div class="gmail_default" style="font-size:small"><span class="gmail_default"></span>/home/rohan/devlopment/src/rtems/build/sparc/erc32/testsuites/samples</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">PS: I haven't tried these commands, maybe the directories differ but the commands should be</div><div class="gmail_default" style="font-size:small">same.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Thanks,</div><div class="gmail_default" style="font-size:small">Niteesh.</div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On Wed, Feb 3, 2021 at 6:36 PM Joel Sherrill <<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>> wrote:<br>
<br>
><br>
><br>
> On Wed, Feb 3, 2021, 6:43 AM Rohan kumar <<a href="mailto:krohan8870@gmail.com" target="_blank"><span class="gmail_default" style="font-size:small"></span>krohan8870@gmail.com</a>> wrote:<br>
><br>
>> Hello all,<br>
>> I am trying to run Hello World program but when run the command "make" to<br>
>> build, the error came "make: *** No targets specified and no makefile<br>
>> found. Stop". Actually there is nothing in the "/build/b-erc32" folder<br>
>> its just empty and<br>
>><br>
><br>
> I'm not sure what you did. The mention of b-erc32 hints at configure and<br>
> autotools but you mention waf. Waf leaves the results in rtems/build and<br>
> you run waf again.<br>
><br>
> This seems to be mixing the old and new build infrastructure instructions.<br>
><br>
> Is there something that needs more attention in the documentation as we<br>
> move to waf only?<br>
><br>
><br>
><br>
> also there in the step "Test a BSP" I got two failures too.<br>
>><br>
><br>
> These results look pretty good. Minimum probably needs to be addressed<br>
> from a tester perspective and sometimes the DL tests fail as the tools<br>
> update.<br>
><br>
>><br>
>> "<br>
>> Passed: 557<br>
>> Failed: 2<br>
>> User Input: 6<br>
>> Expected Fail: 1<br>
>> Indeterminate: 0<br>
>> Benchmark: 3<br>
>> Timeout: 0<br>
>> Test too long: 0<br>
>> Invalid: 0<br>
>> Wrong Version: 0<br>
>> Wrong Build: 0<br>
>> Wrong Tools: 0<br>
>> ------------------<br>
>> Total: 569<br>
>> Failures:<br>
>> dl06.exe<br>
>> minimum.exe<br>
>> User Input:<br>
>> capture.exe<br>
>> dl10.exe<br>
>> top.exe<br>
>> fileio.exe<br>
>> termios.exe<br>
>> monitor.exe<br>
>> Expected Fail:<br>
>> psxfenv01.exe<br>
>> Benchmark:<br>
>> linpack.exe<br>
>> dhrystone.exe<br>
>> whetstone.exe<br>
>> Average test time: 0:00:00.283888<br>
>> Testing time : 0:02:41.532720<br>
>><br>
>> "<br>
>><br>
>> I am currently working on the master branch and trying to build<br>
>> sparc-erc32. Do I have to run the ./waf again I am not sure any direction<br>
>> will be very helpful.<br>
>><br>
>> _______________________________________________<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><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.rtems.org/pipermail/devel/attachments/20210203/3c6c33e6/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.rtems.org/pipermail/devel/attachments/20210203/3c6c33e6/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 3 Feb 2021 08:31:51 -0600<br>
From: Joel Sherrill <<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>><br>
To: Robin M?ller <<a href="mailto:robin.mueller.m@gmail.com" target="_blank">robin.mueller.m@gmail.com</a>><br>
Cc: "<a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a>" <<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
Subject: Re: [PATCH] Basic lwIP for STM32H7 BSP<br>
Message-ID:<br>
<<a href="mailto:CAF9ehCXZS14RXjjtYH1nUXCY3RNRYr4CSpaNctEGDagivVJgoQ@mail.gmail.com" target="_blank">CAF9ehCXZS14RXjjtYH1nUXCY3RNRYr4CSpaNctEGDagivVJgoQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Wed, Feb 3, 2021, 8:26 AM Robin M?ller <<a href="mailto:robin.mueller.m@gmail.com" target="_blank">robin.mueller.m@gmail.com</a>> wrote:<br>
<br>
> Also, Andrei Chichak provided a very good explanation:<br>
><br>
> The STM32x7 ethernet controllers need their descriptors and data areas to<br>
>> be located on 32-byte boundaries with a combination of cache being turned<br>
>> off and buffering being turned off. This is a side effect of the STM32x7<br>
>> DMA and data caching.<br>
>><br>
>> The examples that ST have for LWiP under FreeRTOS have some issues with<br>
>> the linker file having overlapping sections and the stack (above the ETH<br>
>> data areas) being left with no cache and no buffering. The space above the<br>
>> rx/tx buffers is also less than the stack space minimum specified in the<br>
>> linker file as well. Some rearranging of the ETH descriptors and data<br>
>> areas would be prudent. Like push them to the top of SRAM and locate the<br>
>> stack below.<br>
>><br>
>> To get this all going, they set up the MPU for two overlapping sections,<br>
>> one being the top 16kB of SRAM and the other the 256B that contain the ETH<br>
>> descriptors. I believe the MPU regions can be set in increments of 32Bytes,<br>
>> so setting up the cache and buffering should be do-able without affecting<br>
>> the stack.<br>
>><br>
><br>
Just asking. Can this be a non-cacheable region and the variables not in<br>
special sections? I wonder if changing them to normal pointers to special<br>
memory would ripple. Do they just use the variables for initialization or<br>
reference them a lot?<br>
<br>
I think the standard linkcmds setup allows for nocache areas already.<br>
<br>
--joel<br>
<br>
<br>
> Kind Regards<br>
> Robin M?ller<br>
><br>
> On Wed, 3 Feb 2021 at 14:50, Robin M?ller <<a href="mailto:robin.mueller.m@gmail.com" target="_blank">robin.mueller.m@gmail.com</a>><br>
> wrote:<br>
><br>
>> The following link contains more theoretical information about why these<br>
>> sections were placed at these addresses:<br>
>> <a href="https://community.st.com/s/article/FAQ-DMA-is-not-working-on-STM32H7-devices" rel="noreferrer" target="_blank">https://community.st.com/s/article/FAQ-DMA-is-not-working-on-STM32H7-devices</a><br>
>><br>
>> Kind Regards<br>
>> Robin<br>
>><br>
>> On Wed, 3 Feb 2021 at 14:44, Robin M?ller <<a href="mailto:robin.mueller.m@gmail.com" target="_blank">robin.mueller.m@gmail.com</a>><br>
>> wrote:<br>
>><br>
>>> The DMA descriptors need to be placed at the start of the SRAM3 and need<br>
>>> to be aligned in a certain way. The RX buffer will take up the first<br>
>>> (slightly less than) 16 kB of SRAM3 but needs to be placed<br>
>>> behind the DMA descriptors. It also needs to be placed in a way that the<br>
>>> MPU configuration required for the DMA descriptors will not do something<br>
>>> with the RX buffers.<br>
>>> In the example provided by STM32, the first 256 bytes are configured by<br>
>>> MPU Config.<br>
>>><br>
>>> Kind Regards<br>
>>> Robin<br>
>>><br>
>>><br>
>>><br>
>>> On Wed, 3 Feb 2021 at 13:43, Sebastian Huber <<br>
>>> <a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a>> wrote:<br>
>>><br>
>>>> On 02/02/2021 20:10, Robin Mueller wrote:<br>
>>>><br>
>>>> > + /* Not an ideal solution but required for lwIP on the STM32H7<br>
>>>> BSP.<br>
>>>> > + This places the DMA descriptors for lwIP at the start of SRAM3.<br>
>>>> > + The MPU still needs to be configured for the DMA descriptor<br>
>>>> regions to be<br>
>>>> > + bufferable, non-cacheable, non-shareable (first 256 bytes) */<br>
>>>> > + .lwip_sec_stm32h7 (NOLOAD) : ALIGN_WITH_INPUT {<br>
>>>> > + . = ABSOLUTE(0x30040000);<br>
>>>> > + *(.RxDecripSection)<br>
>>>> > + . = ABSOLUTE(0x30040060);<br>
>>>> > + *(.TxDecripSection)<br>
>>>> > + . = ABSOLUTE(0x30040200);<br>
>>>> > + *(.RxArraySection)<br>
>>>> > + } >SRAM_3 AT> REGION_TEXT_LOAD<br>
>>>> > +<br>
>>>><br>
>>>> This is the wrong linker command file. This stuff should be in<br>
>>>><br>
>>>> spec/build/bsps/arm/stm32h7/linkcmdsmemory.yml<br>
>>>><br>
>>>> with an output section name like ".stm32h7_sram_3" and corresponding<br>
>>>> input section names. Why do you need absolute addresses here?<br>
>>>><br>
>>>> --<br>
>>>> embedded brains GmbH<br>
>>>> Herr Sebastian HUBER<br>
>>>> Dornierstr. 4<br>
>>>> 82178 Puchheim<br>
>>>> Germany<br>
>>>> email: <a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a><br>
>>>> phone: +49-89-18 94 741 - 16<br>
>>>> fax: +49-89-18 94 741 - 08<br>
>>>><br>
>>>> Registergericht: Amtsgericht M?nchen<br>
>>>> Registernummer: HRB 157899<br>
>>>> Vertretungsberechtigte Gesch?ftsf?hrer: Peter Rasmussen, Thomas D?rfler<br>
>>>> Unsere Datenschutzerkl?rung finden Sie hier:<br>
>>>> <a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
>>>><br>
>>>> _______________________________________________<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><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.rtems.org/pipermail/devel/attachments/20210203/776ec7b5/attachment.html" rel="noreferrer" target="_blank">http://lists.rtems.org/pipermail/devel/attachments/20210203/776ec7b5/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<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><br>
<br>
------------------------------<br>
<br>
End of devel Digest, Vol 111, Issue 17<br>
**************************************<br>
</blockquote></div></div>