Re: CAN Options and Licensing, Testing, etc

On Tue, Apr 12, 2022 at 9:32 PM Prashanth S wrote: > Hi Joel, > > Have you determined how you will test CAN on BBB? > > I planned to test the CAN driver with another BBB running linux. And if > CAN analyzer is economical then I would use that. > OK. I assume you have accounted for all the

[PATCH] added print statement to hello world example

--- testsuites/samples/hello/init.c | 1 + 1 file changed, 1 insertion(+) diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/init.c index 83f6342ab3..dde33285ab 100644 --- a/testsuites/samples/hello/init.c +++ b/testsuites/samples/hello/init.c @@ -42,6 +42,7 @@ static

[PATCH v2] wscript: Allow substitution outside values

This expands the ability to substitute variables outside the current limitation of values in options to asflags, cflags, cppflags, cxxflags, ldflags, and includes. It is possible for all of these flags to utilize user-defined information in config.ini, especially for paths to external resources.

Re: [PATCH] added print statement to hello world example

Looks good to me. Got your screenshot privately. Add yourself to the GSOC 2022 proposal tracking table: https://devel.rtems.org/wiki/GSoC/2022 Feel free to ask questions on Discord or here. Good luck. On Wed, Apr 13, 2022 at 3:06 PM Duc Doan wrote: > --- > testsuites/samples/hello/init.c |

Re: libc functions from c++ issues

When you use -std= with gcc, it says to strictly enforce that standard. C++ is NOT POSIX so pthread.h prototypes aren't visible. There are some edge cases where gcc isn't that strict until -pedantic is turned on. Use of long long in C++03 is an example of that. -D_POSIX_C_SOURCE=200809 is

Re: [PATCH v1 1/2] wscript: Allow defines to be used for substitution

On 4/13/2022 13:38, Sebastian Huber wrote: On 13/04/2022 20:06, Kinsey Moore wrote: On 4/13/2022 00:53, Sebastian Huber wrote: On 12/04/2022 20:55, Kinsey Moore wrote: This allows options set as defines to the compiler to be used as targets for substitution using the syntax

Re: [PATCH v1 2/2] wscript: Allow substitution outside values

On 4/13/2022 00:48, Sebastian Huber wrote: On 12/04/2022 20:55, Kinsey Moore wrote: diff --git a/wscript b/wscript index 9de9d67b91..e2fc047ea8 100755 --- a/wscript +++ b/wscript @@ -276,10 +276,10 @@ class Item(object):   if target is None:   target =

Re: [PATCH v1 1/2] wscript: Allow defines to be used for substitution

On 4/13/2022 00:53, Sebastian Huber wrote: On 12/04/2022 20:55, Kinsey Moore wrote: This allows options set as defines to the compiler to be used as targets for substitution using the syntax ${DEFINES:define_target}. These need special handling since they are not in a form that is trivially

Re: [PATCH v1 1/2] wscript: Allow defines to be used for substitution

On 13/04/2022 20:06, Kinsey Moore wrote: On 4/13/2022 00:53, Sebastian Huber wrote: On 12/04/2022 20:55, Kinsey Moore wrote: This allows options set as defines to the compiler to be used as targets for substitution using the syntax ${DEFINES:define_target}. These need special handling since

Re: CAN Options and Licensing, Testing, etc

There's a nice tutorial at https://www.thomas-wedemeyer.de/de/electronic/arm/beaglebone/canbus-python/ to use BBB with CAN on Linux via Python SocketCAN. Here's a parts list for a 2-node CAN bus: Qty 2x, BeagleBone Black Rev C - 4GB, https://www.adafruit.com/product/1996 Qty 2x, USB to TTL

Re: CAN Options and Licensing, Testing, etc

Dear Prashanth, On Wednesday 13 of April 2022 04:32:45 Prashanth S wrote: > Have you determined how you will test CAN on BBB? > > I planned to test the CAN driver with another BBB running linux. And if CAN > analyzer is economical then I would use that. I think that testing against Linux kernel

Re: [PATCH v2] wscript: Allow substitution outside values

On 14/4/2022 7:47 am, Kinsey Moore wrote: > This expands the ability to substitute variables outside the current > limitation of values in options to asflags, cflags, cppflags, cxxflags, > ldflags, and includes. It is possible for all of these flags to utilize > user-defined information in

Re: CAN Options and Licensing, Testing, etc

> > And should be able to demonstrate CAN Linux <-> on the same hardware to > verify your test setup. > Ok, that will be helpful to verify the hardware test setup. Regards, Prashanth S On Thu, 14 Apr 2022 at 00:52, Joel Sherrill wrote: > > > On Tue, Apr 12, 2022 at 9:32 PM Prashanth S >

Re: libc functions from c++ issues

On 14/4/2022 1:51 pm, Joel Sherrill wrote: > On Wed, Apr 13, 2022, 9:14 PM Chris Johns > wrote: > > On 14/4/2022 6:58 am, Joel Sherrill wrote: > > When you use -std= with gcc, it says to strictly enforce that standard. > C++ is > > NOT POSIX so pthread.h

Re: CAN Options and Licensing, Testing, etc

Hi Pavel, But if you would fit with writing/porting driver > for some other CAN interface which is available > under QEMU it would be great. I.e. SJA1000 on PCI/e > on x86 and may be some other target or Zynq UltraScale+ > MPSo on QEMU it would be nice to have ability to test > driver by

Re: libc functions from c++ issues

On 14/4/2022 6:58 am, Joel Sherrill wrote: > When you use -std= with gcc, it says to strictly enforce that standard. C++ is > NOT POSIX so pthread.h prototypes aren't visible.  There are some edge cases > where gcc isn't that strict until -pedantic is turned on. Use of long long in > C++03 is an

Re: libc functions from c++ issues

On Wed, Apr 13, 2022, 9:14 PM Chris Johns wrote: > On 14/4/2022 6:58 am, Joel Sherrill wrote: > > When you use -std= with gcc, it says to strictly enforce that standard. > C++ is > > NOT POSIX so pthread.h prototypes aren't visible. There are some edge > cases > > where gcc isn't that strict