Re: Introducing myself to the community

[Vijay Kumar Banerjee]

Hi Purva,

Congratulations and welcome aboard!

On Fri, May 3, 2024 at 4:10 AM Purva Yeshi  wrote:

> Hello everyone,
> I'm Purva Yeshi, a pre-final year Electronics and Telecommunication
> undergraduate from VJTI, Mumbai. I've decent exposure to working with
> Embedded systems and system software, especially Embedded C.
>
> I'm selected for the "Add BSP for Polarfire-based Beagle" project
> .
> It is a large 350-hour project. Primarily, the project's objective is to
> boot RTEMS on the board and run Hello World and ticker examples on the
> board. This project aims to create a BSP for the BeagleV-Fire board, which
> is based on RISC-V architecture and uses the Polarfire SoC.
>
>
It will be an interesting project and I am excited to see how it turns out.
I got a Beagle-V Fire board and I'll be tagging along with your progress.

During the summer, I hope to accomplish the following:
>
> • Successfully created a BSP for the BeagleV-Fire board, ensuring
> compatibility with the RISC-V architecture and Polarfire SoC.
>
> • Implement support for essential peripherals such as CPU cores,
> interrupt controller, timer, and UART, tailored specifically to the
> characteristics of the MPFS025T SoC.
>
> • Implement support for essential peripherals such as CPU cores,
> interrupt controller, timer, and UART, tailored specifically to the
> characteristics of the MPFS025T SoC.
>
> • Test the BSP thoroughly by running Hello World code and ticker examples
> on the BeagleV-Fire hardware.
>
> • Document the BSP comprehensively, including specifications, supported
> features, known issues, and clear instructions for building, installing,
> and utilizing the BSP.
>

We have discussed these steps before and they look reasonable to me. I
would appreciate any feedback or suggestions from the broader community
about the project.

I am excited to join the RTEMS Community and contribute to it. Grateful for
> the opportunit !
>

Looking forward to a "cool summer".

Best regards,
Vijay
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Networking examples

[Vijay Kumar Banerjee]

On Wed, Aug 16, 2023 at 12:13 PM Brett Sterling
 wrote:
>
> First off, I want to thank everyone for the fast replies.  Second, I want to 
> apologize for the delay responding to the questions - I plan to do better 
> going forward.
>
> Here are the responses to the various questions below.  If you'd rather I 
> interlace them in the responses, I'm glad to do so (but didn't want it to get 
> too messy :-)).
>
> None of the RTEMS tools are in my path - we specify locations when doing 
> builds (i.e. would like to specify this as a parameter to the build)
> My tools (e.g. sparc-rtems6-gcc) are located at: 
> $HOME/src/Toolchains/osr_rtems_6_sparc/bin

You can add the tools path using:

--rtems-tools=$HOME/src/Toolchains/osr_rtems_6_sparc

If that doesn't work, would it be possible to add
"$HOME/src/Toolchains/osr_rtems_6_sparc/bin" into your path using
`export` temporarily just to check if that works?

> My kernel is at: 
> $HOME/src/rtems-development/rtems-hello-world/build/sparc-rtems6-erc32/kernel
> I'm trying to build for sparc on RTEMS 6 (probably obvious from the previous 
> pieces of information)
> I'm building on a linux host (cross-building for sparc)
> I'm using the sparc-rtems6-sis (i.e. the sparc simulator) to test the build
> With the workaround for issue with the 'Quick Start' process, I can run the 
> "Hello World" example (from the "Quick Start").  Is this what was being 
> referred to with the question "Can you run hello world?", or is there another 
> "hello world" that I should try?
Great. The RTEMS tools are correctly built then, the issue seems to be
coming from the command line options.

You can also use the `--help` option to see all the options with a
brief description with sb-set-builder
`../source-builder/sb-set-builder --help`

> Per the question "Can you build the rtems-examples from that repository?", 
> can someone clarify which 'repository' that's referring to?  Regardless, the 
> answer is "I haven't tried, but I'm glad to give it a shot if there is 
> information somewhere about how to do this".
>
`rtems-examples` is a separate repository where we have some example
applications that can be used as a reference or starting point for
user application development. Please refer to the following
repository:
https://git.rtems.org/rtems-examples/


Best regards,
Vijay

> Thanks in advance,
> Brett
>
>
>
>
>
>
> 
> From: Vijay Kumar Banerjee 
> Sent: Tuesday, August 15, 2023 12:53 PM
> To: Joel Sherrill 
> Cc: Brett Sterling ; RTEMS Users RTEMS 
> ; Chris Johns 
> Subject: Re: Networking examples
>
> CAUTION: This email originated from outside of the organization. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe.
>
>
>
> On Tue, Aug 15, 2023, 13:10 Joel Sherrill  wrote:
>
>
>
> On Tue, Aug 15, 2023 at 11:57 AM Brett Sterling 
>  wrote:
>
> Hello all!
>
> To get this out of the way prior to all of the requested debugging 
> information - I don't need the legacy stack, any networking stack will do.  I 
> started with legacy because that was what was shown on the RTEMS 
> documentation pages.  We're trying to integrate RTEMS into our system and I 
> considered adding the networking stack that had some documentation a big 
> enough effort without perhaps trying to integrate another network stack.  But 
> I'm absolutely glad to go with any suggestion.
>
>
> Now, onto the requested build failure information.
>
> Following 
> https://docs.rtems.org/branches/master/legacy-networking/quick_start.html
>
> ../source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build 
> 6/rtems-net-legacy --host=sparc-rtems6 --with-rtems-bsp=sparc
> RTEMS Source Builder - Set Builder, 6 (8e568b2ca348 modified)
> warning: exe: absolute exe found in path: (__cmake) /usr/bin/cmake
> Build Set: 6/rtems-net-legacy
> config: tools/rtems-net-legacy-6.cfg
> error: config error: rtems-bsp.cfg:104: RTEMS tools not found 
> (sparc-rtems6-gcc) found; Please check the --with-tools option or --prefix.
> Build FAILED
> Build Set: Time 0:00:00.012407
> Build FAILED
>
> The error information implies that '--prefix' should specify where the 
> 'sparc-rtems6-gcc' should be located, so I tried something different 
> (specifying where the build tools are located).
>
>
> The prefix is where it will be installed. Normally${prefix}/bin/ will contain 
> your cross tools.
>
> --rtems-tools path : Path to an install RTEMS tool set
>
> And your --with-rtems-bsp is just the architecture. It would need to be 
> something like sparc/leon3.
>
> Have you built the tools? Is sparc

Re: Networking examples

[Vijay Kumar Banerjee]

On Tue, Aug 15, 2023, 13:10 Joel Sherrill  wrote:

>
>
> On Tue, Aug 15, 2023 at 11:57 AM Brett Sterling <
> brett.sterl...@odysseysr.com> wrote:
>
>> Hello all!
>>
>> To get this out of the way prior to all of the requested debugging
>> information - I don't need the legacy stack, any networking stack will do.
>> I started with legacy because that was what was shown on the RTEMS
>> documentation pages.  We're trying to integrate RTEMS into our system and I
>> considered adding the networking stack that had some documentation a big
>> enough effort without perhaps trying to integrate another network stack.
>> But I'm absolutely glad to go with any suggestion.
>>
>>
>> Now, onto the requested build failure information.
>>
>> Following
>> https://docs.rtems.org/branches/master/legacy-networking/quick_start.html
>>
>> ../source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build
>> 6/rtems-net-legacy --host=sparc-rtems6 --with-rtems-bsp=sparc
>> RTEMS Source Builder - Set Builder, 6 (8e568b2ca348 modified)
>> warning: exe: absolute exe found in path: (__cmake) /usr/bin/cmake
>> Build Set: 6/rtems-net-legacy
>> config: tools/rtems-net-legacy-6.cfg
>> error: config error: rtems-bsp.cfg:104: RTEMS tools not found
>> (sparc-rtems6-gcc) found; Please check the --with-tools option or --prefix.
>> Build FAILED
>> Build Set: Time 0:00:00.012407
>> Build FAILED
>>
>> The error information implies that '--prefix' should specify where the
>> 'sparc-rtems6-gcc' should be located, so I tried something different
>> (specifying where the build tools are located).
>>
>
> The prefix is where it will be installed. Normally${prefix}/bin/ will
> contain your cross tools.
>
> --rtems-tools path : Path to an install RTEMS tool set
>
> And your --with-rtems-bsp is just the architecture. It would need to be
> something like sparc/leon3.
>
> Have you built the tools? Is sparc-rtems6-gcc in your $PATH? Can you run
> hello world?
>
> And --host normally denotes the host os where you are building. You
> usually want --target.
>
> @Vijay should be able to confirm that for sure. I don't think I have built
> the legacy stack this way recently.
>

I agree with the suggestions above. I am able to reproduce this error with
wrong prefix. The following command works for me for a different board:

`../source-builder/sb-set-builder --prefix=$PATH_TO_DIR_WITH_BIN
--with-rtems-bsp=powerpc/mvme2700 6/rtems-net-legacy`


I have the rtems toolset installed in this prefix path.


>
>
>> prefix=$HOME/src/Toolchains/osr_rtems_6_sparc 6/rtems-net-legacy
>> --host=sparc-rtems6 --with-rtems-bsp=sparc
>> RTEMS Source Builder - Set Builder, 6 (8e568b2ca348 modified)
>> warning: exe: absolute exe found in path: (__cmake) /usr/bin/cmake
>> Build Set: 6/rtems-net-legacy
>> config: tools/rtems-net-legacy-6.cfg
>> error: config error: rtems-bsp.cfg:131: RTEMS BSP not found
>> (sparc-rtems6-sparc.pc); Please check the --with-rtems option or --prefix.
>>
>>
> You have to build RTEMS and install it.  The dot pc file has a pattern
> like this for the powerpc/psim BSP I had installed
>
>
> /home/joel/rtems-work/tools/6/bsp-install/lib/pkgconfig/powerpc-rtems6-psim.pc
>
> prefix to RTEMS
> configure/install: /home/joel/rtems-work/tools/6/bsp-install/
>
> Note that yours would be something like sparc-rtems6-leon3.pc.
>
>

+1


Build FAILED
>> Build Set: Time 0:00:00.014283
>> Build FAILED
>>
>> What I'm guessing is that the networking build still relies on everything
>> being in the correct location, but the documentation doesn't indicate where
>> the networking repository should be put and how the networking build fits
>> in with the tools build and the application builds.  This is probably the
>> information I'm currently lacking.  Then again, I may be missing something
>> in the documentation that I erroneously overlooked.  If so, just let me
>> know.
>>
>> The "Hello World" failure is documented in this ticket:
>> https://devel.rtems.org/ticket/4927
>>
>
> OK. I dhave added Chris who I think wrote that section.
>
> Can you build the rtems-examples from that repository?
>
> --joel
>
>
>>
>> Thanks again in advance!
>> Brett
>>
>>
>>
>> --
>> *From:* Joel Sherrill 
>> *Sent:* Tuesday, August 15, 2023 9:57 AM
>> *To:* Brett Sterling 
>> *Cc:* users@rtems.org ; Vijay Kumar Banerjee <
>> vi...@rtems.org>
>> *Subject:* Re: Networking examples
>>
>> CAUTION:

Re: libbsd for Beaglebone black

[Vijay Kumar Banerjee]

Hi,

On Fri, Jun 4, 2021 at 1:09 PM Siddons, David  wrote:
>
> Hi, I'm working through the "quick start" document 
> (https://docs.rtems.org/branches/master/user/start/index.html), and have 
> succeeded in bulding and running the paranoia example on the beaglebone. I 
> now want to add the bsd networking library. I followed 
> https://rmeena840.github.io/Fourth-Post/. I successfully configured waf, but 
> in the build operation I got the following error:
>
> ../../rtemsbsd/nfsclient/nfs.c:2279:3: error: 'const struct 
> _rtems_filesystem_operations_table' has no member named 'utimens_h'; did you 
> mean 'utime_h'?
>   .utimens_h = nfs_utimens,
>^
>utime_h
>
Please rebuild the RSB toolchain after pulling from the current master
branch. The newlib version has been updated recently in the RSB and
the updated version is required to build the BSP.

Best regards,
Vijay

> Not sure if I did something wrong, or this is a known problem.
> Pete.
>
>
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Manually building a BSP from branch 5 of git

[Vijay Kumar Banerjee]

Hi all,

On Wed, May 26, 2021 at 6:02 AM Christian MAUDERER
 wrote:
>
> Hello Andrew,
>
> Am 26.05.21 um 08:10 schrieb Johnson, Andrew N.:
> > Hi Vijay,
> >
> > On May 25, 2021, at 8:18 PM, Vijay Kumar Banerjee  > <mailto:vi...@rtems.org>> wrote:
> >>
> >> I found the 5.1 docs version from rtems ftp. This looks like the right
> >> one:
> >> https://ftp.rtems.org/pub/rtems/releases/5/5.1/docs/html/user/start/bsp-build.html#manual-bsp-build
> >> <https://ftp.rtems.org/pub/rtems/releases/5/5.1/docs/html/user/start/bsp-build.html#manual-bsp-build>
> >
> > Excellent, thanks – I would have expected that version of the User
> > Manual to be linked from the Releases table of https://devel.rtems.org/
> > <https://devel.rtems.org/> on the row for branch 5.
> >
> >
> > How do I set BSP options like this flag to RSB?
> >
> >> --with-rtems-bspopts="BSP_CONSOLE_BAUD=9600”
> >
>
> You pass it to the configure line as BSP_CONSOLE_BAUD=9600
>
>
> With the old build system, the steps are basically:
>
> - bootstrap (if you haven't done so) in the rtems source directory:
>
>path/to/rtems-source-builder/source-builder/sb-bootstrap
>
> - create a build directory and call configure:
>
>path/to/rtems-sources/configure \
>  --target=$(MACHINE)-rtems5 \
>  --prefix=$(PREFIX) \
>  --enable-posix \
>  --enable-rtemsbsp=$(BSP) \
>  --enable-maintainer-mode \
>  --disable-networking \
>  --enable-tests=samples \
>  CONSOLE_POLLED=1 \
>  BSP_CONSOLE_BAUD=9600
>
>NOTE: This is copied from one of my older builds. You most likely
> have to adapt some options (like posix or networking).
>
> - make and install the bsp:
>
>make
>make install
>
> >
> > Does the --enable-networking flag to configure do the equivalent of this
> > RSB flag?
> >
> >> --with-rtems-legacy-network
>
> I'm not 100% sure but I would say: Yes, it is.
>
> >
> > If that’s the case would I have to build the libbsd network stack as a
> > separate build?
>
> Be carefull: There is libbsd and there is the legacy stack. If your BSP
> uses the legacy stack that is the one that you enable with the configure
> option. On the 5 branch it is still integrated in RTEMS (I think -
> Vijay: correct me if I'm wrong). If your BSP uses libbsd, that would be
> an extra build.
>
+1
The libbsd needs to be built separately and the RTEMS configure needs
to have --disable-networking option.
You can also build libbsd from RSB with a similar command to the following:


../source-builder/sb-set-builder --prefix=$RTEMS_PREFIX
--host=powerpc-rtems5 --with-rtems-bsp=mvme2100 5/rtems-libbsd


> If you used --with-rtems-legacy-network on the RSB, I think you only
> have to use --enable-networking during configure.
>
Yes.


Best regards,
Vijay

> Best regards
>
> Christian
>
> >
> >
> > Thanks,
> >
> > - Andrew
> >
> >
> >> On Tue, May 25, 2021 at 5:27 PM Johnson, Andrew N.  >> <mailto:a...@anl.gov>> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I’m trying to develop fixes for issues that I’m seeing in some of the
> >>> powerpc/motorola_powerpc BSPs, and I’m working on the 5 branch (it
> >>> doesn’t look like those have been fixed on the master branch yet
> >>> either). I have built the tools and those BSPs before using RSB but
> >>> now I need to build my modified sources, and I think the docs say
> >>> that I have to do that manually. That’s fine, but unfortunately the
> >>> instructions at 2.5.2. Manual BSP Build seem to be for the master
> >>> branch and don’t work for me because there was no waf script present
> >>> on branch 5. Are there any alternative instructions that I can follow
> >>> to do a manual build of this branch?
> >>>
> >>> Thanks,
> >>>
> >>> - Andrew
> >>>
> >>> --
> >>> Complexity comes for free, simplicity you have to work for.
> >>>
> >>> ___
> >>> users mailing list
> >>> users@rtems.org <mailto:users@rtems.org>
> >>> http://lists.rtems.org/mailman/listinfo/users
> >
> > --
> > Complexity comes for free, simplicity you have to work for.
> >
> >
> > ___
> > users mailing list
> > users@rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
> >
>
> --
> 
> embedded brains GmbH
> Herr Christian MAUDERER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: christian.maude...@embedded-brains.de
> phone: +49-89-18 94 741 - 18
> fax:   +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: RTEMS 5 how to run "hello" example

[Vijay Kumar Banerjee]

On Tue, Mar 16, 2021 at 4:07 AM Olga Syrbachova  wrote:
>
> Thank you very much for your reply!
>
> I've added
> includes = 
> '/home/olga/development/rtems/rtems-5/testsuites/support/include/tmacros.h',
>
It takes the relative address to the directory where the header file
is. For example, if you're building from the
"/home/olga/development/rtems" directory the includes argument would
be:

`includes = './rtems-5/testsuites/support/include/'`

BTW, your first email at the start of the thread says that you just
want to run the samples, the samples get built as a part of the rtems
and you'll be able to see the *.exe files in the build directory. Is
there any reason that you're trying to build it in a separate
directory with waf? Experimenting with the build system is a good
reason though, just making sure that we're not pushing you in the
wrong direction and your objective is indeed to try waf on your own
and not just running RTEMS hello app.

Best regards,
Vijay


> it still says "No such file or directory". I'm pretty sure the path is write, 
> though there is now another path to "tmacros.h" (the first one below), it's a 
> folder named "tmacros.h" and it's empty.
> olga@olga-H270M-DS3H:~$ locate tmacros.h
> /home/olga/development/app/ticker/build/sparc-rtems5-erc32/$HOME/developement/rtems/rtems-5/testsuites/support/include/tmacros.h
> /home/olga/development/rtems/rtems-5/testsuites/support/include/tmacros.h
>
>
> On Mon, 15 Mar 2021 at 21:00, Vijay Kumar Banerjee  wrote:
>>
>> On Mon, Mar 15, 2021 at 1:53 PM Olga Syrbachova  
>> wrote:
>> >
>> > Sure! https://github.com/syrba4eva/RTEMS/blob/main/wscript
>>
>> Thanks. In this line: 
>> https://github.com/syrba4eva/RTEMS/blob/main/wscript#L33
>> After cflags parameter, add "includes", for example:
>>
>> bld(features = 'c cprogram',
>>   target = 'ticker.exe',
>>   cflags = '-g -O2',
>>   includes='. .. ./original/path/to/tmacros.h',
>>   source = ['init.c', 'tasks.c'])
>>
>> you don't need to copy tmacros.h or any headers from rtems, just add
>> the path to includes.
>>
>>
>> Best regards,
>> Vijay
>>
>> >
>> > On Mon, 15 Mar 2021 at 20:36, Vijay Kumar Banerjee  wrote:
>> >>
>> >> On Mon, Mar 15, 2021 at 1:30 PM Olga Syrbachova  
>> >> wrote:
>> >> >
>> >> > Thank you very much for your reply!
>> >> > Unfortunately I'm still a bit confused and don't quite understand what 
>> >> > to do. Where do I need to modify the "include" parameter? In the 
>> >> > wscript file from the "hello" example there is no "include" parameter. 
>> >> > I also tried to find a tutorial on how to write a wscript, but didn't 
>> >> > find any (Could you suggest any please?). So I tried to copy the file 
>> >> > "tmacros.h" from testsuites/support/include to app/ticker. Now after 
>> >> > running ./waf I get an error, which tells me that "buffer_test_io.h" 
>> >> > wasn't found. When I copied it to my app/ticker directory it didn't 
>> >> > work and I still have the same error.
>> >> >
>> >> Would it be possible for you to paste your wscript somewhere (like
>> >> gist.github.com) and share it here so that we can have a look and help
>> >> you with that?
>> >>
>> >> Best regards,
>> >> Vijay
>> >>
>> >> > Waf: Entering directory 
>> >> > `/home/olga/development/app/ticker/build/sparc-rtems5-erc32'
>> >> > [1/3] Compiling tasks.c
>> >> > [2/3] Compiling init.c
>> >> > In file included from ../../system.h:17:0,
>> >> >  from ../../init.c:15:
>> >> > ../../tmacros.h:32:10: fatal error: buffer_test_io.h: No such file or 
>> >> > directory
>> >> >  #include 
>> >> >   ^~
>> >> > compilation terminated.
>> >> >
>> >> > In file included from ../../system.h:17:0,
>> >> >  from ../../tasks.c:22:
>> >> > ../../tmacros.h:32:10: fatal error: buffer_test_io.h: No such file or 
>> >> > directory
>> >> >  #include 
>> >> >   ^~
>> >> > compilation terminated.
>> >> >
>> >> > Waf: Leaving directory 
>> >> > `/home/olga/development/app/ticker/build/sparc-rtems5-erc32'
>> >

Re: RTEMS 5 how to run "hello" example

[Vijay Kumar Banerjee]

On Mon, Mar 15, 2021 at 1:53 PM Olga Syrbachova  wrote:
>
> Sure! https://github.com/syrba4eva/RTEMS/blob/main/wscript

Thanks. In this line: https://github.com/syrba4eva/RTEMS/blob/main/wscript#L33
After cflags parameter, add "includes", for example:

bld(features = 'c cprogram',
  target = 'ticker.exe',
  cflags = '-g -O2',
  includes='. .. ./original/path/to/tmacros.h',
  source = ['init.c', 'tasks.c'])

you don't need to copy tmacros.h or any headers from rtems, just add
the path to includes.


Best regards,
Vijay

>
> On Mon, 15 Mar 2021 at 20:36, Vijay Kumar Banerjee  wrote:
>>
>> On Mon, Mar 15, 2021 at 1:30 PM Olga Syrbachova  
>> wrote:
>> >
>> > Thank you very much for your reply!
>> > Unfortunately I'm still a bit confused and don't quite understand what to 
>> > do. Where do I need to modify the "include" parameter? In the wscript file 
>> > from the "hello" example there is no "include" parameter. I also tried to 
>> > find a tutorial on how to write a wscript, but didn't find any (Could you 
>> > suggest any please?). So I tried to copy the file "tmacros.h" from 
>> > testsuites/support/include to app/ticker. Now after running ./waf I get an 
>> > error, which tells me that "buffer_test_io.h" wasn't found. When I copied 
>> > it to my app/ticker directory it didn't work and I still have the same 
>> > error.
>> >
>> Would it be possible for you to paste your wscript somewhere (like
>> gist.github.com) and share it here so that we can have a look and help
>> you with that?
>>
>> Best regards,
>> Vijay
>>
>> > Waf: Entering directory 
>> > `/home/olga/development/app/ticker/build/sparc-rtems5-erc32'
>> > [1/3] Compiling tasks.c
>> > [2/3] Compiling init.c
>> > In file included from ../../system.h:17:0,
>> >  from ../../init.c:15:
>> > ../../tmacros.h:32:10: fatal error: buffer_test_io.h: No such file or 
>> > directory
>> >  #include 
>> >   ^~
>> > compilation terminated.
>> >
>> > In file included from ../../system.h:17:0,
>> >  from ../../tasks.c:22:
>> > ../../tmacros.h:32:10: fatal error: buffer_test_io.h: No such file or 
>> > directory
>> >  #include 
>> >   ^~~~~~
>> > compilation terminated.
>> >
>> > Waf: Leaving directory 
>> > `/home/olga/development/app/ticker/build/sparc-rtems5-erc32'
>> > Build failed
>> >  -> task in 'ticker.exe' failed with exit status 1 (run with -v to display 
>> > more information)
>> >  -> task in 'ticker.exe' failed with exit status 1 (run with -v to display 
>> > more information)
>> >
>> > On Mon, 15 Mar 2021 at 16:21, Vijay Kumar Banerjee  wrote:
>> >>
>> >> Hi Olga,
>> >>
>> >>
>> >> On Mon, Mar 15, 2021 at 8:29 AM Olga Syrbachova  
>> >> wrote:
>> >> >
>> >> > Thank you very much for your reply!
>> >> >
>> >> > I've built the RTEMS Kernel for erc32. Then I followed this tutorial 
>> >> > https://docs.rtems.org/branches/master/user/start/app.html to build a 
>> >> > "Hello World" application and it works just fine. Then I've tried to 
>> >> > create another application following the steps in the tutorial.
>> >> > 1. In $HOME/development/app/ I created a directory "ticker".
>> >> > 2. cd ticker
>> >> > 3. curl https://waf.io/waf-2.0.19 > waf
>> >> > chmod +x waf
>> >> > git init
>> >> > git submodule add git://git.rtems.org/rtems_waf.git rtems_waf
>> >> > 4. I've copied the files "init.c", "tasks.c", "system.h" from 
>> >> > testsuites/samples
>> >> > 5. In the "wscript" I've changed the lines 32 and 34 to target = 
>> >> > 'ticker.exe', source = ['init.c', 'tasks.c']
>> >> > 6. ./waf configure --rtems=$HOME/development/rtems/5 
>> >> > --rtems-bsp=sparc/erc32
>> >> > 7. and running ./waf next, I get an error. It looks like the file 
>> >> > "tmacros.h", which is included in "system.h", cannot be found.
>> >> >
>> >> You have changed the "target" and "source" parameters in your wscript.
>> >> You'd also need to modify the "include" parameter and add relative
>> >> path to tmacros.h. For multiple headers, you'll have to add the paths
>> >> as a string with space-separated values or a list like this:
>> >> `includes='./ ../ ./path/to/include/'`
>> >>
>> >>
>> >> > What am I doing wrong? Is the way to run other examples exactly the 
>> >> > same as to run a "Hello World" example?
>> >> The other examples will also follow a similar wscript structure but
>> >> hello world is the simple one with fewer includes so it's a good place
>> >> to start if you're trying to learn how to make a separate project with
>> >> RTEMS applications using waf.
>> >>
>> >>
>> >> Best regards,
>> >> Vijay
>> >> > ___
>> >> > users mailing list
>> >> > users@rtems.org
>> >> > http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: RTEMS 5 how to run "hello" example

[Vijay Kumar Banerjee]

On Mon, Mar 15, 2021 at 1:30 PM Olga Syrbachova  wrote:
>
> Thank you very much for your reply!
> Unfortunately I'm still a bit confused and don't quite understand what to do. 
> Where do I need to modify the "include" parameter? In the wscript file from 
> the "hello" example there is no "include" parameter. I also tried to find a 
> tutorial on how to write a wscript, but didn't find any (Could you suggest 
> any please?). So I tried to copy the file "tmacros.h" from 
> testsuites/support/include to app/ticker. Now after running ./waf I get an 
> error, which tells me that "buffer_test_io.h" wasn't found. When I copied it 
> to my app/ticker directory it didn't work and I still have the same error.
>
Would it be possible for you to paste your wscript somewhere (like
gist.github.com) and share it here so that we can have a look and help
you with that?

Best regards,
Vijay

> Waf: Entering directory 
> `/home/olga/development/app/ticker/build/sparc-rtems5-erc32'
> [1/3] Compiling tasks.c
> [2/3] Compiling init.c
> In file included from ../../system.h:17:0,
>  from ../../init.c:15:
> ../../tmacros.h:32:10: fatal error: buffer_test_io.h: No such file or 
> directory
>  #include 
>   ^~
> compilation terminated.
>
> In file included from ../../system.h:17:0,
>  from ../../tasks.c:22:
> ../../tmacros.h:32:10: fatal error: buffer_test_io.h: No such file or 
> directory
>  #include 
>   ^~
> compilation terminated.
>
> Waf: Leaving directory 
> `/home/olga/development/app/ticker/build/sparc-rtems5-erc32'
> Build failed
>  -> task in 'ticker.exe' failed with exit status 1 (run with -v to display 
> more information)
>  -> task in 'ticker.exe' failed with exit status 1 (run with -v to display 
> more information)
>
> On Mon, 15 Mar 2021 at 16:21, Vijay Kumar Banerjee  wrote:
>>
>> Hi Olga,
>>
>>
>> On Mon, Mar 15, 2021 at 8:29 AM Olga Syrbachova  
>> wrote:
>> >
>> > Thank you very much for your reply!
>> >
>> > I've built the RTEMS Kernel for erc32. Then I followed this tutorial 
>> > https://docs.rtems.org/branches/master/user/start/app.html to build a 
>> > "Hello World" application and it works just fine. Then I've tried to 
>> > create another application following the steps in the tutorial.
>> > 1. In $HOME/development/app/ I created a directory "ticker".
>> > 2. cd ticker
>> > 3. curl https://waf.io/waf-2.0.19 > waf
>> > chmod +x waf
>> > git init
>> > git submodule add git://git.rtems.org/rtems_waf.git rtems_waf
>> > 4. I've copied the files "init.c", "tasks.c", "system.h" from 
>> > testsuites/samples
>> > 5. In the "wscript" I've changed the lines 32 and 34 to target = 
>> > 'ticker.exe', source = ['init.c', 'tasks.c']
>> > 6. ./waf configure --rtems=$HOME/development/rtems/5 
>> > --rtems-bsp=sparc/erc32
>> > 7. and running ./waf next, I get an error. It looks like the file 
>> > "tmacros.h", which is included in "system.h", cannot be found.
>> >
>> You have changed the "target" and "source" parameters in your wscript.
>> You'd also need to modify the "include" parameter and add relative
>> path to tmacros.h. For multiple headers, you'll have to add the paths
>> as a string with space-separated values or a list like this:
>> `includes='./ ../ ./path/to/include/'`
>>
>>
>> > What am I doing wrong? Is the way to run other examples exactly the same 
>> > as to run a "Hello World" example?
>> The other examples will also follow a similar wscript structure but
>> hello world is the simple one with fewer includes so it's a good place
>> to start if you're trying to learn how to make a separate project with
>> RTEMS applications using waf.
>>
>>
>> Best regards,
>> Vijay
>> > ___
>> > users mailing list
>> > users@rtems.org
>> > http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: RTEMS 5 how to run "hello" example

[Vijay Kumar Banerjee]

Hi Olga,


On Mon, Mar 15, 2021 at 8:29 AM Olga Syrbachova  wrote:
>
> Thank you very much for your reply!
>
> I've built the RTEMS Kernel for erc32. Then I followed this tutorial 
> https://docs.rtems.org/branches/master/user/start/app.html to build a "Hello 
> World" application and it works just fine. Then I've tried to create another 
> application following the steps in the tutorial.
> 1. In $HOME/development/app/ I created a directory "ticker".
> 2. cd ticker
> 3. curl https://waf.io/waf-2.0.19 > waf
> chmod +x waf
> git init
> git submodule add git://git.rtems.org/rtems_waf.git rtems_waf
> 4. I've copied the files "init.c", "tasks.c", "system.h" from 
> testsuites/samples
> 5. In the "wscript" I've changed the lines 32 and 34 to target = 
> 'ticker.exe', source = ['init.c', 'tasks.c']
> 6. ./waf configure --rtems=$HOME/development/rtems/5 --rtems-bsp=sparc/erc32
> 7. and running ./waf next, I get an error. It looks like the file 
> "tmacros.h", which is included in "system.h", cannot be found.
>
You have changed the "target" and "source" parameters in your wscript.
You'd also need to modify the "include" parameter and add relative
path to tmacros.h. For multiple headers, you'll have to add the paths
as a string with space-separated values or a list like this:
`includes='./ ../ ./path/to/include/'`


> What am I doing wrong? Is the way to run other examples exactly the same as 
> to run a "Hello World" example?
The other examples will also follow a similar wscript structure but
hello world is the simple one with fewer includes so it's a good place
to start if you're trying to learn how to make a separate project with
RTEMS applications using waf.


Best regards,
Vijay
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Issues with configuring BSP with waf

[Vijay Kumar Banerjee]

Hello Ida,


On Thu, Mar 11, 2021 at 9:48 AM Ida Delphine  wrote:
>
> Thank you for your response. I am not working on the rtems.git/master branch. 
> I'm not using it because earlier I tried downloading sources with it but I 
> got this error
> error: shell macro failed: 
> /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c gcc  -l 
> : 2: error: no library (-l) provided
> So I decided to use the other alternative(get the sources from releases)
>
> Since I'm a GSoC applicant should I wait till the issue at the master branch 
> is resolved?
>
The wait is over. The issue has been resolved upstream and hopefully,
you'll be able to build it without issue.

Best regards,
Vijay

> Cheers,
> Ida.
>
> On Thu, Mar 11, 2021 at 4:18 PM Gedare Bloom  wrote:
>>
>> On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine  wrote:
>> >
>> > Hello everyone,
>> > Was following the quick build documentation and had issues around where I 
>> > have to do a manual BSP build.  In the last step of configuring the BSP, I 
>> > ran this command:
>> >
>> > ./waf configure --prefix=$HOME/quick-start/rtems/5
>> >
>> Are you working on rtems.git/master branch or /5 branch? Note that you
>> need to be sure to use a consistent compiler toolchain based on the
>> version of RTEMS that you use.
>>
>> In rtems/5 branch we don't have waf support integrated yet. The
>> upgrade to waf is happening currently on the master branch, which will
>> eventually become the RTEMS version 6 release.
>>
>> For GSoC students we expect development to happen on the development
>> head and not a release, so please make sure that you have the
>> toolchain built from rtems-source-builder.git/master and the rtems
>> source tree from rtems.git/master.
>>
>> > It didn't produce the expected output. I instead got:
>> > bash: ./waf: No such file or directory
>> > As a result I downloaded it with the command:
>> > curl https://waf.io/waf-2.0.19 > waf
>>
>> https://git.rtems.org/rtems/tree/waf
>>
>> Currently, the waf-based build of rtems only supports "in tree"
>> builds, which means you need to run waf from within the rtems.git/
>> root of your source. This is a limitation of the waf build.
>>
>> FWIW, waf build improvements could also fall under GSoC effort,
>> although no one has written it up as a task yet. It would be mostly
>> Python.
>>
>> > I ran  the last command to configure the BSP again but still did not get 
>> > the expected  output. I got this rather:
>> > Waf: Run from a folder containing a 'wscript' file (or try -h for the 
>> > generic options)
>> > Please how do I fix this? What am I missing?
>> > I have tried looking for solutions but to no avail.
>> >
>> Sometimes the solutions only exist inside other people's heads, so
>> asking questions is encouraged.
>>
>> > Thanks,
>> > Ida.
>> > ___
>> > users mailing list
>> > users@rtems.org
>> > http://lists.rtems.org/mailman/listinfo/users
>
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: ANN: RTEMS libnetworking relocation

[Vijay Kumar Banerjee]

On Wed, Mar 3, 2021 at 5:03 PM Chris Johns  wrote:
>
> On 4/3/21 9:24 am, Gedare Bloom wrote:
> > We have had third-party validation on hardware tests (Thanks to Heinz
> > Junkes!) that ironed out a few minor issues. The network stack update
> > will be pushed tomorrow. *Fingers crossed* everything just works as
> > usual for rtems6 for anyone who isn't using libnetworking.
>
> Congratulations.
>
> Vijay, awesome work, a really great contribution. Thank you.
>
Thank you!

Also thanks for reviewing and providing suggestions. :)

Best regards,
Vijay
> Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: mmap on /dev/fd0 on pc686 BSP not working at all.

[Vijay Kumar Banerjee]

Hello Karel, Gedare

Reading the post by Pavel in the other thread, I think the pc386
shouldn't be using the libbsd framebuffer. To be able to use the
driver in pc386, you'll have to disable the drivers from
rtems-littevgl. Please use `--no-drivers` option with ./waf configure
in rtems-littlevgl and remove the "fbdev_init" from the hello app. The
initialization of the fb is supposed to be handled by the drivers in
the BSP.

Best regards,
Vijay

On Mon, Sep 21, 2020 at 9:47 PM Gedare Bloom  wrote:
>
> Hi Karel,
>
> I don't know if I can provide any answers, but I can provide some
> guidance maybe. I implemented mmap() in rtems to provide portability
> and compliance for mmap applications that use MAP_SHARED with fixed
> addresses. We don't do any real mapping or translating of memory since
> there is no virtual memory support in rtems. Kevin Kirsepl
> extended/fixed the file handler part of that implementation
>
> There is an mmap helper implemented in libbsd: rtems-libbsd.git:
> /rtemsbsd/sys/fs/devfs/devfs_devs.c:391 devfs_imfs_mmap()
> Vijay implemented that as part of the BBB framebuffer work. I haven't
> studied it closely enough to give any advice on how to replicate/use
> that in another FB. Hopefully he may be able to chime in, as he also
> did a lot of the work with lvgl porting.
>
> The pc386 FB was written by one of Pavel Pisa's students, Jan Dolezal.
> I had hopes we could generalize the code to other targets because it
> is relatively simple compared to other framebuffers. I think someone
> tried with raspberry pi. But that effort hasn't really moved in a few
> years.
>
> My guess is that the pc386 fb needs to have something like devfs_imfs_mmap().
>
> Gedare
>
> On Sun, Sep 20, 2020 at 2:43 PM Karel Gardas  wrote:
> >
> >
> > Hello,
> >
> > I'm attempting to get rtems-example/lvgl/hello working on pc686 BSP. I'm
> > using VESA framebuffer which is default on pc686, although I needed to
> > do few fixes here and there to ensure littlevgl library compiles well.
> > All patches here
> > https://lists.rtems.org/pipermail/devel/2020-September/062186.html
> >
> > Now, everthing is compiled and VESA fb is well initialized -- or seems
> > so. Now, vgl library tries to use that fb (/dev/fb0) and basically tries
> > to mmap it for its own use. The code looks:
> >
> > void fbdev_init(void)
> > {
> > // Open the file for reading and writing
> > fbfd = open(FBDEV_PATH, O_RDWR);
> > if(fbfd == -1) {
> > perror("Error: cannot open framebuffer device");
> > return;
> > }
> > printf("The framebuffer device was opened successfully.\n");
> > [...]
> > // Map the device to memory
> > fbp = (char *)mmap(0, screensize, PROT_READ | PROT_WRITE,
> > MAP_SHARED, fbfd, 0);
> > if((intptr_t)fbp == -1) {
> > perror("Error: failed to map framebuffer device to memory");
> > return;
> > }
> > memset(fbp, 0, screensize);
> >
> > printf("The framebuffer device was mapped to memory successfully.\n");
> >
> >
> > The mmap above fails. Screensize is realistic and good looking number.
> >
> > While debugging this mmap I see it fails on the call to function on line
> > 280:
> >
> > err = (*iop->pathinfo.handlers->mmap_h)(
> > iop, >addr, len, prot, off );
> >
> > it returns -1 and hence mmap failure since code below looks:
> >
> > if ( err != 0 ) {
> >   mmap_mappings_lock_release( );
> >   free( mapping );
> >   return MAP_FAILED;
> > }
> >
> > when I try to step into the problematic function above, I end up  in
> > default_mmap.c:31 on:
> >
> > rtems_set_errno_and_return_minus_one( ENOTSUP );
> >
> > and as the function claims it really returns -1 to me.
> >
> > Now, my obvious question is: how to make VESA fb mmappable? It looks
> > like the same library is working fine on BBB while using FreeBSD BBB
> > framebuffer driver, so there is probably some way how to convince RTEMS
> > mmap to work with fb0.
> >
> > Any idea how to proceed with this is highly appreciated.
> >
> > Thanks,
> > Karel
> >
> >
> > ___
> > users mailing list
> > users@rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: users Digest, Vol 167, Issue 8

[Vijay Kumar Banerjee]

On Tue, Aug 11, 2020 at 7:14 AM Zacchaeus Liang  wrote:
>
> Do i add it as an argument and what is the argument name (didn't reply all 
> sorry?
>
You don't need a separate option just add the location with the
command line you're using. Something like this:

rtems-test \
--rtems-tools=$HOME/development/rtems/5 \
--rtems-bsp=lpc-qemu \
$HOME/development/rtems/kernel/pc386/i386-rtems5/c/pc386/testsuites/samples

> Thanks
> zack
>
> Il giorno lun 10 ago 2020 alle ore 21:31 Vijay Kumar Banerjee 
>  ha scritto:
>>
>> On Tue, Aug 11, 2020 at 6:57 AM Zacchaeus Liang  wrote:
>> >
>> > It says that there is not supplied executable
>> Looks like you're in the right direction.
>>
>> Add the location to the samples directory to the command line and
>> it'll work. The location will be in the bsp build location.
>> something like pc-386/i386-rtems5/c/pc386/testsuites/samples
>>
>>
>> Best regards,
>> Vijay
>> > zack
>> >
>> > Il giorno lun 10 ago 2020 alle ore 21:10 Vijay Kumar Banerjee 
>> >  ha scritto:
>> >>
>> >> Hi Zack,
>> >>
>> >> I have posted a comment below...
>> >>
>> >> On Tue, Aug 11, 2020 at 5:54 AM Zacchaeus Liang  
>> >> wrote:
>> >> >
>> >> > I tried to add the prefix and i had the prefix  with this
>> >> > rtems-test --rtems-bsp=i386-rtems5 
>> >> > --rtems-tools=$HOME/development/rtems/5 
>> >> > --rtems-prefix=$HOME/development/rtems/5
>> >> > i get the same error. Was the prefix correct based on the instructions?
>> >> >
>> >> > Thanks
>> >> > zack
>> >> >
>> >> > Il giorno lun 10 ago 2020 alle ore 00:31 Niteesh G. S. 
>> >> >  ha scritto:
>> >> >>
>> >> >> Hello,
>> >> >>
>> >> >>>
>> >> >>> Hello,
>> >> >>>
>> >> >>> I'm Zack and I'm currently finishing up my university degree in comp 
>> >> >>> sci.
>> >> >>> I'm really interested in aviation and aerospace systems. I want to 
>> >> >>> get into
>> >> >>> rtems to learn more about rtos and contribute to rtems !
>> >> >>>
>> >> >>> Currently I'm trying to build rtems and test and bsp. Hoping to then
>> >> >>> contribute. I followed one of you GSOC student's tutorials and tried 
>> >> >>> to go
>> >> >>> ahead. I'm trying to build the test the bsp right now.
>> >> >>> here is his blog post
>> >> >>> https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
>> >> >>> I tried to run the bsp testing like this and it says the ini file is 
>> >> >>> not
>> >> >>> found.  Is this the right bsp argument?  After this i'm going to try 
>> >> >>> to
>> >> >>> build an application and would like to know the right path to install 
>> >> >>> it.
>> >> >>> Any tips on looking for easy things to learn to patch? Thanks in 
>> >> >>> advance i
>> >> >>> know it's a handful for questions!
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> zakonrockets@zakonrockets-Inspiron-15-7000-Gaming:~/development/rtems/kernels-5/pcp-386$
>> >> >>> rtems-test --rtems-bsp=i386-rtems5
>> >> >>> --rtems-tools=$HOME/development/rtems/5
>> >> >>> RTEMS Testing - Tester, 5.0.not_released
>> >> >>>  Command Line: /home/zakonrockets/development/rtems/5/bin/rtems-test
>> >> >>> --rtems-bsp=i386-rtems5
>> >>
>> >> --rtems-bsp option should have the bsp and not the architecture.
>> >> Please try --rtems-bsp=pc-qemu
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: users Digest, Vol 167, Issue 8

[Vijay Kumar Banerjee]

On Tue, Aug 11, 2020 at 6:57 AM Zacchaeus Liang  wrote:
>
> It says that there is not supplied executable
Looks like you're in the right direction.

Add the location to the samples directory to the command line and
it'll work. The location will be in the bsp build location.
something like pc-386/i386-rtems5/c/pc386/testsuites/samples


Best regards,
Vijay
> zack
>
> Il giorno lun 10 ago 2020 alle ore 21:10 Vijay Kumar Banerjee 
>  ha scritto:
>>
>> Hi Zack,
>>
>> I have posted a comment below...
>>
>> On Tue, Aug 11, 2020 at 5:54 AM Zacchaeus Liang  wrote:
>> >
>> > I tried to add the prefix and i had the prefix  with this
>> > rtems-test --rtems-bsp=i386-rtems5 --rtems-tools=$HOME/development/rtems/5 
>> > --rtems-prefix=$HOME/development/rtems/5
>> > i get the same error. Was the prefix correct based on the instructions?
>> >
>> > Thanks
>> > zack
>> >
>> > Il giorno lun 10 ago 2020 alle ore 00:31 Niteesh G. S. 
>> >  ha scritto:
>> >>
>> >> Hello,
>> >>
>> >>>
>> >>> Hello,
>> >>>
>> >>> I'm Zack and I'm currently finishing up my university degree in comp sci.
>> >>> I'm really interested in aviation and aerospace systems. I want to get 
>> >>> into
>> >>> rtems to learn more about rtos and contribute to rtems !
>> >>>
>> >>> Currently I'm trying to build rtems and test and bsp. Hoping to then
>> >>> contribute. I followed one of you GSOC student's tutorials and tried to 
>> >>> go
>> >>> ahead. I'm trying to build the test the bsp right now.
>> >>> here is his blog post
>> >>> https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
>> >>> I tried to run the bsp testing like this and it says the ini file is not
>> >>> found.  Is this the right bsp argument?  After this i'm going to try to
>> >>> build an application and would like to know the right path to install it.
>> >>> Any tips on looking for easy things to learn to patch? Thanks in advance 
>> >>> i
>> >>> know it's a handful for questions!
>> >>>
>> >>>
>> >>>
>> >>> zakonrockets@zakonrockets-Inspiron-15-7000-Gaming:~/development/rtems/kernels-5/pcp-386$
>> >>> rtems-test --rtems-bsp=i386-rtems5
>> >>> --rtems-tools=$HOME/development/rtems/5
>> >>> RTEMS Testing - Tester, 5.0.not_released
>> >>>  Command Line: /home/zakonrockets/development/rtems/5/bin/rtems-test
>> >>> --rtems-bsp=i386-rtems5
>>
>> --rtems-bsp option should have the bsp and not the architecture.
>> Please try --rtems-bsp=pc-qemu
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: users Digest, Vol 167, Issue 8

[Vijay Kumar Banerjee]

Hi Zack,

I have posted a comment below...

On Tue, Aug 11, 2020 at 5:54 AM Zacchaeus Liang  wrote:
>
> I tried to add the prefix and i had the prefix  with this
> rtems-test --rtems-bsp=i386-rtems5 --rtems-tools=$HOME/development/rtems/5 
> --rtems-prefix=$HOME/development/rtems/5
> i get the same error. Was the prefix correct based on the instructions?
>
> Thanks
> zack
>
> Il giorno lun 10 ago 2020 alle ore 00:31 Niteesh G. S.  
> ha scritto:
>>
>> Hello,
>>
>>>
>>> Hello,
>>>
>>> I'm Zack and I'm currently finishing up my university degree in comp sci.
>>> I'm really interested in aviation and aerospace systems. I want to get into
>>> rtems to learn more about rtos and contribute to rtems !
>>>
>>> Currently I'm trying to build rtems and test and bsp. Hoping to then
>>> contribute. I followed one of you GSOC student's tutorials and tried to go
>>> ahead. I'm trying to build the test the bsp right now.
>>> here is his blog post
>>> https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
>>> I tried to run the bsp testing like this and it says the ini file is not
>>> found.  Is this the right bsp argument?  After this i'm going to try to
>>> build an application and would like to know the right path to install it.
>>> Any tips on looking for easy things to learn to patch? Thanks in advance i
>>> know it's a handful for questions!
>>>
>>>
>>>
>>> zakonrockets@zakonrockets-Inspiron-15-7000-Gaming:~/development/rtems/kernels-5/pcp-386$
>>> rtems-test --rtems-bsp=i386-rtems5
>>> --rtems-tools=$HOME/development/rtems/5
>>> RTEMS Testing - Tester, 5.0.not_released
>>>  Command Line: /home/zakonrockets/development/rtems/5/bin/rtems-test
>>> --rtems-bsp=i386-rtems5

--rtems-bsp option should have the bsp and not the architecture.
Please try --rtems-bsp=pc-qemu
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Help RTEMS 5

[Vijay Kumar Banerjee]

Hi Daniela

On Tue, May 12, 2020 at 7:24 PM Daniela Oliveira  wrote:
>
> >Hi,
>
> > I'm installing rtems 5 and came across the following error: checking for 
> > sparc-rtems 5-strip ... no
There is a space in "sparc-rtems 5-strip" if this is not a typo that
seeped in while pasting here, then
this might be the source of the error. If that's not the case then
please check that you have
sparc-rtems5-strip in your PATH.
>
> > when I create the makefile.
>
> > I saw some reports of this same error and I couldn't find the solution.
>
Did the sparc-rtems5 toolchain build complete successfully?
> > I would appreciate a help, as this is the first time I install rtems.
>
> >Tks
>
> >Daniela
>
>
>
>
>
> Enviado do Email para Windows 10
>
>
>
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Interested in contributing to Beaglebone BSP

[Vijay Kumar Banerjee]

On Sun, May 3, 2020 at 8:12 PM Christian Mauderer  wrote:

> Hello James and Vijay,
>
> On 03/05/2020 14:33, Vijay Kumar Banerjee wrote:
> > Hi James
> >
> > On Sun, May 3, 2020 at 4:30 PM James Fitzsimons
> > mailto:james.fitzsim...@gmail.com>> wrote:
> >
> > Hi Christian,
> >
> > I tried to make a start this evening but I hate to say I ran into
> > trouble getting my rtems environment setup, and after attempting to
> > debug this for a couple of hours I thought I might see if you (or
> > anyone else on the list) had some ideas.
> >
> > I started by forking
> > your https://gitlab.com/c-mauderer/rtems-bbb gitlab repo and running
> > make setup.
>
> Note that the repo works only most of the time. It's more of a test repo
> for me that just collects the necessary commands and repositories so I
> don't have to type everything manually.
>
> The dtc that I build there currently doesn't work. I removed the step
> from the makefile so that the host dtc is used again.
>
> >
> > Everything progresses fine up until the "dtb" step in the makefile.
> > At that point I get the following error:
> >
> > make -C /home/james/Documents/rtems/rtems-bbb//devicetree
> > MACHINE=arm install
> > make[1]: Entering directory
> > '/home/james/Documents/rtems/rtems-bbb/devicetree'
> > /home/james/Documents/rtems/rtems-bbb//install/rtems/5/bin/dtc -@ -o
> >
>  
> /home/james/Documents/rtems/rtems-bbb//install/rtems/5/fdt/am335x-i2c-overlay.dtbo
> >
>  /home/james/Documents/rtems/rtems-bbb/devicetree//am335x-i2c-overlay.dtso
> > /home/james/Documents/rtems/rtems-bbb//install/rtems/5/bin/dtc:
> > invalid option -- '@'
> > Usage: dtc [options] 
> >
> > A bit of googling turned up some information that the -@ option is
> > deprecated, and sure enough running ./install/rtems/5/bin/dtc --help
> > shows that the version of dtc built (Version: DTC 1.4.1-gf2f0fdf1)
> > does not have the @ option. I tried modifying the makefile in the
> > devicetree directory so the last two lines look like this:
> >
> > The -@ option is required to generate the symbols without which there
> > will be errors in applying the overlay. The -@ option is not present in
> > version 1.4.1, you can build 1.4.6 from the source. I recently added the
> > rsb recipe for 1.4.6 but there's no bset present and the devel/dtc
> > builds the 1.4.1 .
>
> That's correct. The -@ or --symbols is only there in newer dtc versions.
> Out of interest: Where did you find that the option is deprecated? It is
> still there in 1.6.0.
>
> Firstly, sorry for the typo. I mistakenly wrote 1.4.6 instead of 1.6.
To make it clear: The option IS present in 1.6.0

> >
> > Christian: Can we make a bset for dtc-1.4.6 which can be separately
> > build like build/dtc-1.4.6.bset ?
>
> I don't think that would be a good idea before the release. After the
> release we should work on a 1.6 build set. The 1.6 only needs libyaml
> (or libjson?) which is no default package on FreeBSD. So we need a
> solution for that on FreeBSD hosts.
>
> I didn't test it with FreeBSD. Yes, after the release we can make a best
for 1.6.0 and mention libjson/libyaml as a dependency. We'll just have
to figure out a way to check from RSB if the package is present, I hope
we'll find some example in the repo already.

> >
> > $(TARGETDIR)/%.dtbo: $(MAKEFILE_DIR)/%.dtso
> >
> > $(PREFIX)/bin/dtc -o $@ $<
> >
> >
> > Now running $make dtb gives the following output:
> >
> > make[1]: Entering directory
> > '/home/james/Documents/rtems/rtems-bbb/devicetree'
> > /home/james/Documents/rtems/rtems-bbb//install/rtems/5/bin/dtc -o
> >
>  
> /home/james/Documents/rtems/rtems-bbb//install/rtems/5/fdt/am335x-i2c-overlay.dtbo
> >
>  /home/james/Documents/rtems/rtems-bbb/devicetree//am335x-i2c-overlay.dtso
> > Error:
> >
>  
> /home/james/Documents/rtems/rtems-bbb/devicetree//am335x-i2c-overlay.dtso:2.2-8
> > syntax error
> > FATAL ERROR: Unable to parse input tree
> > Makefile:24: recipe for target
> >
>  
> '/home/james/Documents/rtems/rtems-bbb//install/rtems/5/fdt/am335x-i2c-overlay.dtbo'
> > failed
> > make[1]: ***
> >
>  
> [/home/james/Documents/rtems/rtems-bbb//install/rtems/5/fdt/am335x-i2c-overlay.dtbo]
> > Error 1
> > make[1]: Leaving directory
> > '/home/james/Documents/rtems/rtems-bbb/devicetree'
> > Makefile:96: recipe f

Re: Interested in contributing to Beaglebone BSP

[Vijay Kumar Banerjee]

Hi James

On Sun, May 3, 2020 at 4:30 PM James Fitzsimons 
wrote:

> Hi Christian,
>
> I tried to make a start this evening but I hate to say I ran into trouble
> getting my rtems environment setup, and after attempting to debug this for
> a couple of hours I thought I might see if you (or anyone else on the list)
> had some ideas.
>
> I started by forking your https://gitlab.com/c-mauderer/rtems-bbb gitlab
> repo and running make setup.
>
> Everything progresses fine up until the "dtb" step in the makefile. At
> that point I get the following error:
>
> make -C /home/james/Documents/rtems/rtems-bbb//devicetree MACHINE=arm
> install
> make[1]: Entering directory
> '/home/james/Documents/rtems/rtems-bbb/devicetree'
> /home/james/Documents/rtems/rtems-bbb//install/rtems/5/bin/dtc -@ -o
> /home/james/Documents/rtems/rtems-bbb//install/rtems/5/fdt/am335x-i2c-overlay.dtbo
> /home/james/Documents/rtems/rtems-bbb/devicetree//am335x-i2c-overlay.dtso
> /home/james/Documents/rtems/rtems-bbb//install/rtems/5/bin/dtc: invalid
> option -- '@'
> Usage: dtc [options] 
>
> A bit of googling turned up some information that the -@ option is
> deprecated, and sure enough running ./install/rtems/5/bin/dtc --help shows
> that the version of dtc built (Version: DTC 1.4.1-gf2f0fdf1) does not have
> the @ option. I tried modifying the makefile in the devicetree directory so
> the last two lines look like this:
>
> The -@ option is required to generate the symbols without which there will
be errors in applying the overlay. The -@ option is not present in version
1.4.1, you can build 1.4.6 from the source. I recently added the rsb recipe
for 1.4.6 but there's no bset present and the devel/dtc builds the 1.4.1 .

Christian: Can we make a bset for dtc-1.4.6 which can be separately build
like build/dtc-1.4.6.bset ?

$(TARGETDIR)/%.dtbo: $(MAKEFILE_DIR)/%.dtso
>
> $(PREFIX)/bin/dtc -o $@ $<
>
>
> Now running $make dtb gives the following output:
>
> make[1]: Entering directory
> '/home/james/Documents/rtems/rtems-bbb/devicetree'
> /home/james/Documents/rtems/rtems-bbb//install/rtems/5/bin/dtc -o
> /home/james/Documents/rtems/rtems-bbb//install/rtems/5/fdt/am335x-i2c-overlay.dtbo
> /home/james/Documents/rtems/rtems-bbb/devicetree//am335x-i2c-overlay.dtso
> Error:
> /home/james/Documents/rtems/rtems-bbb/devicetree//am335x-i2c-overlay.dtso:2.2-8
> syntax error
> FATAL ERROR: Unable to parse input tree
> Makefile:24: recipe for target
> '/home/james/Documents/rtems/rtems-bbb//install/rtems/5/fdt/am335x-i2c-overlay.dtbo'
> failed
> make[1]: ***
> [/home/james/Documents/rtems/rtems-bbb//install/rtems/5/fdt/am335x-i2c-overlay.dtbo]
> Error 1
> make[1]: Leaving directory
> '/home/james/Documents/rtems/rtems-bbb/devicetree'
> Makefile:96: recipe for target 'dtb' failed
> make: *** [dtb] Error 2
> james@opportunity:~/Documents/rtems/rtems-bbb$
>
> I'm not quite sure where to go from here though.
>
> If I then run the following steps in the makefile manually, bootstrap and
> bsp complete, but libbsd fails with the following error:
>
> [1497/2193] Compiling freebsd/sys/netpfil/pf/pf_lb.c
> ../../freebsd/sys/arm/freescale/imx/imx6_ccm.c:54:10: fatal error:
> arm/freescale/imx/imx_ccmvar.h: No such file or directory
>  #include 
>   ^~~~
> compilation terminated.
>

This bug was recently fixed in the rtems-libbsd ( for both master and
5-freebsd-12 branches), if you update to recent HEAD of the libbsd, then
this error will hopefully not be there.

Best regards,
Vijay

>
> Thanks for any advice you can provide.
>
> Regards,
> James Fitzsimons
>
>
>
>
>
>
> On Mon, 27 Apr 2020 at 00:25, Christian Mauderer 
> wrote:
>
>> Hello James,
>>
>> On 26/04/2020 12:05, James Fitzsimons wrote:
>> > Hi Christian,
>> >
>> > Thanks for your reply.
>> >
>> > On Wed, 22 Apr 2020 at 23:29, Christian Mauderer
>> > > > > wrote:
>> >
>> > Hello James,
>> >
>> > On 20/04/2020 13:13, James Fitzsimons wrote:
>> > > I am interested in adding support for the eQEP (Enhanced
>> Quadrature
>> > > Encoder Pulse Module) which I am using to decode the quadrature
>> > encoders
>> > > on my motors.
>> >
>> > That one isn't implemented yet and I don't know of any current work
>> on
>> > it. So feel free to go ahead.
>> >
>> >
>> > Thanks for the encouragement - I will start with the eQEP drivers.
>> >
>> >
>> > > I will eventually also need support for the ADC, PRU (I see some
>> work
>> > > has already been done on that by a GSoC project),
>> >
>> > There has been some work on PRU. I'm not entirely sure about ADC.
>> >
>> > > and ideally the TI
>> > > WiLink 8 WL1835MOD wireless chipset - although I realise that
>> might be
>> > > extremely difficult.
>> >
>> > That depends: What kind of interface is used for that? And is the
>> chip
>> > already supported in FreeBSD?
>> >
>> >
>> > I have done a bit of research and can't find any FreeBSD 

Re: Touchscreen Input Device with RTEMS (evdev)

[Vijay Kumar Banerjee]

On Mon, Apr 6, 2020 at 9:15 PM furkan bodur  wrote:

> Firstly thanks for replies,
>
> As I said there is no input folder in /dev path here is the output,
>
> SHLL [/] # ls -las /dev/input
>
> /dev/input: No such file or directory
>
> Here is what I did for use libbsd and evdev,
> I builded rtems-freebsd with this,
> $ ./waf configure --prefix="$HOME/development/rtems/5"
> --rtems-bsps=arm/beagleboneblack
> --buildset=buildset/default.ini
> $ ./waf
> $ ./waf install
>
> Commands are correct.

> Even so, when I realize that there is no input.h or evdev.h file in rtems
> includes , I changed some values in the libbsd.py file. Here the things I
> changed,
> I added 'freebsd/sys/dev' and 'freebsd/sys/dev/evdev' paths to
> include-paths.
>
evdev is already included in EVDEV section in libbsd.py, I don't think
it'll be required to add it here.

> I added 'freebsd/sys/dev/evdev' path to header-paths.
>
Yes, if evdev.h is used in the application, this is the right place to add
it.
Can you please send a patch for this? :)

>
> After that, I did waf again and here is the outputs;
>
> $ ./waf
> ...
> [1519/1939] Compiling freebsd/sys/dev/evdev/evdev.c
> ...
>
> ./waf install
> ...
> + install
> /home/furkan/development/rtems/5/arm-rtems5/beagleboneblack/lib/include/dev/evdev/evdev.h
> (from freebsd/sys/dev/evdev/evdev.h)
> + install
> /home/furkan/development/rtems/5/arm-rtems5/beagleboneblack/lib/include/dev/evdev/input-event-codes.h
> (from freebsd/sys/dev/evdev/input-event-codes.h)
> + install
> /home/furkan/development/rtems/5/arm-rtems5/beagleboneblack/lib/include/dev/evdev/input.h
> (from freebsd/sys/dev/evdev/input.h)
> ...
>
> I'm not sure if this is the right way to use evdev. This is how my
> application compiles without errors but still there is no /dev/input file.
>
> As mentioned above, the steps are right and they need to be pushed to
rtems-libbsd, please send
a patch for review.

There are a few more steps to get your app running. In rtems-littlevgl:
1. In lvgl.py add this after line 43:
mk_files.append('lv_drivers/display/display.mk')
2. In lv_drivers/indev/evdev.c:
Change the included headers to match the freebsd headers. Like,
linux/input.h to evdev/input.h and try
to build it. If it builds fine, please test it with your app and see if
it's working.

Best regards,
Vijay

> Vijay Kumar Banerjee , 6 Nis 2020 Pzt, 09:43 tarihinde
> şunu yazdı:
>
>>
>>
>> On Mon, Apr 6, 2020 at 5:00 AM Chris Johns  wrote:
>>
>>> On 2020-04-06 06:17, furkan bodur wrote:
>>> > Hello everyone,
>>> > I am trying to make an simple HMI system . I am using LittlevGL with
>>> BSD
>>> > framebuffer. Thanks to Vijay, I made a lot of progress, but I can't
>>> > figure it out how to use touchscreen or any input devices. I followed
>>> > LVGL docs and tried to work with evdev drivers but it doesn't work.
>>> >
>>> > I used input.h and other necessary headers from rtems-libbsd and my
>>> app
>>> > successfully compiled but when I run it on the Beagle Black, I am
>>> > getting "unable open evdev interface:: No such file or directory"
>>> error
>>> > in serial screen.
>>> >
>>> > I checked the files in Serial screen and noticed that there is no
>>> input
>>> > folder in the /dev directory, as in Linux systems. I think that's the
>>> > reason of the error, but I don't know where I made the mistake.
>>> >
>>> > Any suggestions for me to use evdev properly?
>>>
>>> I can see there is evdev code in libbsd so at least it is present. Are
>>> you able to confirm the evdev code is being built and linked into your
>>> application?
>>>
>>> On FreeBSD I have ...
>>>
>>> $ ls -las /dev/input
>>> total 1
>>> 1 dr-xr-xr-x   2 root  wheel   512 Mar 21 08:22 .
>>> 1 dr-xr-xr-x  11 root  wheel   512 Mar 21 08:22 ..
>>> 0 crw---   1 root  wheel   0xc Mar 21 08:22 event0
>>> 0 crw---   1 root  wheel  0x29 Mar 21 08:22 event1
>>> 0 crw---   1 root  wheel  0x8f Mar 22 13:42 event2
>>> 0 crw---   1 root  wheel  0xa3 Mar 21 08:23 event4
>>>
>>> but I am not sure how they were created.
>>>
>>>
>> Hi Furkan,
>>
>> Thanks for posting about your project in the list, good to know that you
>> made progress with it.
>>  Please check the command that Chris mentioned. There's evdev code in
>> libbsd and is enabled
>> in the default build as well,  so it's supposed to be there. If we're
>> lucky, the only thing that needs
>> to be done in order to run lvgl input is to port lv_drivers input to BSD.
>> Currently, it uses Linux
>> headers and codes. I think we'll just have to change the header includes
>> in lv_drivers/indev/evdev.c
>> and if we're lucky, it'll work.
>>
>> Best regards,
>> Vijay
>>
>>> Chris
>>> ___
>>> users mailing list
>>> users@rtems.org
>>> http://lists.rtems.org/mailman/listinfo/users
>>>
>>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Touchscreen Input Device with RTEMS (evdev)

[Vijay Kumar Banerjee]

On Mon, Apr 6, 2020 at 5:00 AM Chris Johns  wrote:

> On 2020-04-06 06:17, furkan bodur wrote:
> > Hello everyone,
> > I am trying to make an simple HMI system . I am using LittlevGL with BSD
> > framebuffer. Thanks to Vijay, I made a lot of progress, but I can't
> > figure it out how to use touchscreen or any input devices. I followed
> > LVGL docs and tried to work with evdev drivers but it doesn't work.
> >
> > I used input.h and other necessary headers from rtems-libbsd and my app
> > successfully compiled but when I run it on the Beagle Black, I am
> > getting "unable open evdev interface:: No such file or directory" error
> > in serial screen.
> >
> > I checked the files in Serial screen and noticed that there is no input
> > folder in the /dev directory, as in Linux systems. I think that's the
> > reason of the error, but I don't know where I made the mistake.
> >
> > Any suggestions for me to use evdev properly?
>
> I can see there is evdev code in libbsd so at least it is present. Are
> you able to confirm the evdev code is being built and linked into your
> application?
>
> On FreeBSD I have ...
>
> $ ls -las /dev/input
> total 1
> 1 dr-xr-xr-x   2 root  wheel   512 Mar 21 08:22 .
> 1 dr-xr-xr-x  11 root  wheel   512 Mar 21 08:22 ..
> 0 crw---   1 root  wheel   0xc Mar 21 08:22 event0
> 0 crw---   1 root  wheel  0x29 Mar 21 08:22 event1
> 0 crw---   1 root  wheel  0x8f Mar 22 13:42 event2
> 0 crw---   1 root  wheel  0xa3 Mar 21 08:23 event4
>
> but I am not sure how they were created.
>
>
Hi Furkan,

Thanks for posting about your project in the list, good to know that you
made progress with it.
 Please check the command that Chris mentioned. There's evdev code in
libbsd and is enabled
in the default build as well,  so it's supposed to be there. If we're
lucky, the only thing that needs
to be done in order to run lvgl input is to port lv_drivers input to BSD.
Currently, it uses Linux
headers and codes. I think we'll just have to change the header includes in
lv_drivers/indev/evdev.c
and if we're lucky, it'll work.

Best regards,
Vijay

> Chris
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Contributing to the BSP of beaglebone

[Vijay Kumar Banerjee]

On Tue, Nov 12, 2019 at 9:03 AM Utkarsh Rai  wrote:

> Hello everyone,
>
Hello Utkarsh!

> Through your assistance, I have been able to get RTEMS up and running on
> the BeagleBone Black.
>
Awesome!

> I am interested in contributing to the BegleBone BSPs , it would be very
> kind of you if I could get a few indicators on the features of the BSP that
> need developing/improvement.
>
> This ticket:
https://devel.rtems.org/ticket/3784

This is an interesting project and we would really like to see this happen.
The ticket has a very nice description and also notes the requirements at
the
bottom.

If you want to do relatively smaller projects: There had been some
interesting
work in Framebuffer and PRU drivers, you can add to them if that interests
you.
The PRU driver has not been merged I guess and would involve some testing
and debugging to get it merged, you can help with that :). For Framebuffer,
you can add/work on adding a console, mouse, cursor...

PRU ticket: https://devel.rtems.org/ticket/3730
Framebuffer doesn't have a separate ticket now and it's totally supported
in BBB through libbsd, so if you want to add some feature, we can create
a ticket for that.

You can pick up an area of your interest and start by asking about it in
de...@rtems.org. Hope this helps!

Best Regards,
Vijay

> Thank You. Regards.
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: [EXTERNAL] Re: BeagleBone Black Networking (wifi and/or wired)

[Vijay Kumar Banerjee]

On Sun, Jun 9, 2019 at 6:22 AM Chris Johns  wrote:

>
>
> On 8/6/19 5:58 pm, Christian Mauderer wrote:
> > - Ursprüngliche Mail -
> >> Von: "Oyake, Amalaye (386M)" 
> >> An: "Chris Johns" , "Vijay Kumar Banerjee" <
> vijaykumar9...@gmail.com>, "Christian Mauderer"
> >> 
> >> CC: "RTEMS Users" 
> >> Gesendet: Samstag, 8. Juni 2019 04:57:02
> >> Betreff: Re: [EXTERNAL] Re: BeagleBone Black Networking (wifi and/or
> wired)
> >
> >> Device Tree overays are a method used to update the Device Tree. Given
> a device
> >> tree that describes all the devices, let's say you add a new SPI
> device, you
> >> can update the device tree with a (blob) device tree overlay.
> >>
> >> I should ask (without Googling), What is the Device Tree Overlay
> mechanism in
> >> RTEMS?
> >
> >
> > Hello Amalaye,
> >
> > as far as I know, the device tree overlay mechanism in RTEMS is not
> implemented. There is the prototype of fdt_overlay_apply() in libfdt.h but
> there is no implementation. So there are two methods:
> >
> > 1. Applying the overlay on a build machine. Vijay did that during his
> tests.
>
> How do you do this?
>
> I used `fdtoverlay` from libfdt on linux host.

> > 2. Use the U-Boot mechanism to apply overlays before booting RTEMS. That
> should most likely work too. But I didn't test it yet.
>
> OK
>
> >> On 6/7/19, 6:17 PM, "users on behalf of Chris Johns" <
> users-boun...@rtems.org on
> >> behalf of chr...@rtems.org> wrote:
> >>
> >>On 8/6/19 1:53 am, Vijay Kumar Banerjee wrote:
> >>>
> >>> I would like to add that in two projects of this year( I2C and
> PRU-ICSS drivers)
> >>> we
> >>> are using our own device tree overlays that make our drivers work.
> Where to add
> >>> the device
> >>> tree related stuff seems like an important question.
> >>
> >>What are device tree overlays?
> >
> > Like Oyake already said: They are some small pices of device trees that
> are just added to the base tree in it's binary form. Linux (and most likely
> FreeBSD too) supports that even after boot. If you add an overlay it
> re-parses the device tree, updates GPIO settings and loads new drivers. The
> alternative is to let the boot loader apply them during boot.
>
> What is needed to do this? Maybe I can add it to rtems-boot-image as a way
> to
> handle this at the u-boot version.
>
> I have also tried to automate it by adding it in uEnv.txt as a script, it
worked nicely to apply
the overlay on the blob, I haven't tested it with any app though, but the
overlay applied
successfully. Here's what the test uEnv.txt looks like.
```
setenv bootdelay 5
uenvcmd=run overlay_cmd boot
overlay_cmd=fatload mmc 0 0x8080 rtems-app.img; fatload mmc 0
0x8800 am335x-boneblack.dtb; fatload mmc 0 0x8810
am335x-rtems.dtbo; fdt addr 0x8800; fdt resize 0x1000; fdt apply
0x8810;
boot=bootm 0x8080 - 0x8800;
```

You can add something like this to the uEnv.txt in SD card image. In the
above script
the am335x-boneblack.dtb is the one from linux and am335x-rtems.dtbo is
generated
with dtc from the overlay written by me.

> A practical example would be adding a I2C device like a DS1338 RTC to the
> extension connector of the Beagle:
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-I2C2-RTC-DS1338.dts
>
> I see the need for this.
>
> > I suggested them for Vijays GSoC project to be able to add an I2C
> adaption layer so that libbsd uses the RTEMS i2c drivers. That's necessary
> so that RTEMS applications can still use the RTEMS i2c interface but at the
> same time the FreeBSD drivers (in that case for some chip related to HDMI)
> can use the BSD interface.
>
> OK.
>
> Chris
>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: BeagleBone Black Networking (wifi and/or wired)

[Vijay Kumar Banerjee]

On Fri, Jun 7, 2019 at 9:15 PM Christian Mauderer <
christian.maude...@embedded-brains.de> wrote:

>
>
> - Ursprüngliche Mail -
> > Von: "Chris Johns" 
> > An: "Christian Mauderer" ,
> "RTEMS Users" 
> > Gesendet: Freitag, 7. Juni 2019 14:23:51
> > Betreff: Re: BeagleBone Black Networking (wifi and/or wired)
>
> > On 7/6/19 7:41 pm, Christian Mauderer wrote:
> >> On 07/06/2019 11:19, Chris Johns wrote:
> >>> On 7/6/19 7:18 pm, Christian Mauderer wrote:
> >>>
> >>> Which FDT blob do I need to load?
> >>>
> >>
> >> I usually use the one from either the official Linux or the one from
> >> FreeBSD. Alternatively you can build your own from
> >>
> >>git://xenbits.xen.org/people/ianc/device-tree-rebasing.git
> >>
> >
> > Thanks. I have found them and I can build the default one on FreeBSD. It
> does
> > not build on MacOS, the `cpp` from clang does not like command line.
> >
> > I wonder if we should include the dts source from FreeBSD in
> rtems-libbsp and
> > maybe some blobs. This stuff is pretty nerdy and makes libbsd awkward to
> use.
> > Crashing if not present is not friendly.
> >
> > Chris
>
> Note that basically all device tree files that I have found yet are forked
> from the Linux ones. They are all GPL. I think it was Sichen Zhao during
> 2017 GSoC who wanted to add some to the RTEMS repository and it has been
> rejected due to the license. I don't really object to adding them
> somewhere. But we should think exactly about where we want that stuff.
>
> I would like to add that in two projects of this year( I2C and PRU-ICSS
drivers) we
are using our own device tree overlays that make our drivers work. Where to
add the device
tree related stuff seems like an important question.


> Regards
>
> Christian
> --
> 
> embedded brains GmbH
> Christian Mauderer
> Dornierstr. 4
> D-82178 Puchheim
> Germany
> email: christian.maude...@embedded-brains.de
> Phone: +49-89-18 94 741 - 18
> Fax:   +49-89-18 94 741 - 08
> PGP: Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: BeagleBone Black Networking (wifi and/or wired)

[Vijay Kumar Banerjee]

On Fri, Jun 7, 2019 at 6:09 PM Chris Johns  wrote:

> On 7/6/19 10:32 pm, Sebastian Huber wrote:
> > On 07/06/2019 14:23, Chris Johns wrote:
> >> On 7/6/19 7:41 pm, Christian Mauderer wrote:
> >>> On 07/06/2019 11:19, Chris Johns wrote:
>  On 7/6/19 7:18 pm, Christian Mauderer wrote:
> 
>  Which FDT blob do I need to load?
> 
> >>>
> >>> I usually use the one from either the official Linux or the one from
> >>> FreeBSD. Alternatively you can build your own from
> >>>
> >>> git://xenbits.xen.org/people/ianc/device-tree-rebasing.git
> >>>
> >>
> >> Thanks. I have found them and I can build the default one on FreeBSD.
> It does
> >> not build on MacOS, the `cpp` from clang does not like command line.
> >>
> >> I wonder if we should include the dts source from FreeBSD in
> rtems-libbsp and
> >> maybe some blobs. This stuff is pretty nerdy and makes libbsd awkward
> to use.
> >> Crashing if not present is not friendly.
> >
> > For a start some documentation would be helpful too:
> >
> > https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#beagle
> >
>
> I agree, I saw this after checking there first. Once I figure out what I am
> doing I will add some. I am still assembling all the pieces.
>
> Hello Chris,

I recently wrote a blog post about running RTEMS on BBB:
https://blog.thelunatic.dev/getting-started-bbb-2/

Some of it can be a part of the documentation I think. I would like to
help with the documentation on Beagle BSP. :-)

Thanks

> Chris
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: GSoC Hello World

[Vijay Kumar Banerjee]

On Mon, 4 Mar 2019 at 17:34, Omar Shafik  wrote:

> I would like to know how to submit the proof.
> Thanks,
> Omar Shafik.
>

Hi Omar,

To submit the proof, take a screenshot of the working modified hello world
and send it along with a patch to j...@rtems.org or ged...@rtems.org

Regards,
Vijay

> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users