GSoC-2022 Hello-World Project for BeagleBone Black

Hi All, This is to send the Hello-World Project for BeagleBone Black BSP. I am Prashanth S a working professional with experience of 3 years and 6 months. I wanted to be part of open source community especially contributing RTOS, by taking GSoC-2022 as an opportunity I like to contribute

Re: CAN Options and Licensing, Testing, etc

Hi All, This is to ask for suggestions on implementing the CAN driver for BBB. Can I proceed with defining driver specific structures for the CAN driver or go with adding a generic API layer for ADC and GPIO. Regards Prashanth S On Tue, 12 Apr 2022 at 19:14, Joel Sherrill wrote: > Hi &g

CAN driver message structure

ependent CAN message structure or use one of the existing ones. Ideally, I think a generic (driver independent) CAN message structure will help applications to be portable. Regards Prashanth S ___ devel mailing list devel@rtems.org http://lists.rtems

Re: CAN Options and Licensing, Testing, etc

f I am wrong with my understanding. Regards Prashanth S On Thu, 14 Apr 2022 at 18:33, Joel Sherrill wrote: > > > On Wed, Apr 13, 2022, 10:46 PM Prashanth S > wrote: > >> Hi Pavel, >> >> But if you would fit with writing/porting driver >>> for some oth

Re: CAN Options and Licensing, Testing, etc

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. Regards Prashanth S On Wed, 13 Apr 2022 at 00:38, Joel Sherrill wrote: > > > On Tue, Apr 12, 2022 at

Updated CAN message structure.

data[64]; // For supporting data transfer up to 64 bytes. }; Regards Prashanth S On Tue, 21 Jun 2022 at 14:43, Oliver Hartkopp wrote: > Hi Christian, > > I'm not subscribed to the RTEMS ML so my mail has not been forwarded. > > I'm with you about the 16 bit length info

Request for feedback for CAN message structure

on the suggestions in the mail chain and looking through other CAN solutions (Nuttx, GRCAN, LinCAN). Regards Prashanth S ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] cpukit/dev/can: Added CAN support

t does match the needs of all drivers / > applications? Based on the suggestions, need to decide a suitable count. > What's the advantage of implementing two types of semaphores depending > on the _POSIX_SEM_ macro instead of just using only one RTEMS-native type? That I used for debu

Re: GSoC 2022:

Hi Christian, I created a patch (attached in the mail) for review, which has CAN support. Shall I send the patch for review to @rtems-de...@rtems.org ? Regards Prashanth S On Mon, 11 Jul 2022 at 10:03, Prashanth S wrote: > Hi Christian, > > This is to update the status. > > Ye

[PATCH] cpukit/dev/can: Added CAN support

--- cpukit/dev/can/can-queue.c| 112 +++ cpukit/dev/can/can.c | 480 ++ cpukit/include/dev/can/can.h | 115 +++ spec/build/cpukit/librtemscpu.yml | 5 + 4 files changed, 712 insertions(+) create mode 100644

Review Request for CAN patch for tx path and minimal rx support

This is a review request for the CAN patch with tx and minimal rx support. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

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,

Re: CAN Options and Licensing, Testing, etc

B CAn controller support > for QEMU, but I think that it would be too much load. > I think QEMU does not have Am335x support ( https://wiki.qemu.org/Documentation/Platforms/ARM). Regards Prashanth S On Thu, 14 Apr 2022 at 00:29, Pavel Pisa wrote: > Dear Prashanth, > > On Wednesda

Re: devel Digest, Vol 129, Issue 37

; Normally I strongly suggest to disable digest and let the list send > individual messages instead. Use a mail filter (ideally server side) to > move them into one folder so that they don't spam your inbox. Ok. I will address the review comments and upload the changes. Regards Prashanth S On

Re: devel Digest, Vol 129, Issue 37

Hi All, This is a review request for DCAN and CAN support. The review comments would be very helpful for stabilizing the source files. https://gitlab.com/slpp95prashanth/gsoc-2022/-/tree/can-review-latest-squash-02-squash/ Regards Prashanth S On Mon, 15 Aug 2022 at 11:57, Prashanth S wrote

Review Request for DCAN patches

Hi All, This is a review request for the DCAN patch, I have updated the files based on review comments. Attaching the patch as a zip file. Regards Prashanth S DCAN.tar.lzma Description: application/lzma ___ devel mailing list devel@rtems.org http

Re: Review Request for DCAN patches

Hi Christian, I squashed the commits and pushed to the same branch. https://gitlab.com/slpp95prashanth/gsoc-2022/-/tree/can-dev-squashed1 Regards Prashanth S On Wed, 26 Oct, 2022, 10:56 pm , wrote: > Hello Prashanth, > > from my point of view the patches look good and I think you

Review request for DCAN support

Hi All, This is a review request for DCAN and CAN support (merge patch). Attaching compressed file for DCAN patch, as file size exceeds 256KB. Regards Prashanth S DCAN.tar.lzma Description: application/lzma ___ devel mailing list devel@rtems.org

[PATCH v5 1/2] cpukit/dev/can: Added CAN support

+ * + * @brief Controller Area Network (CAN) Bus Implementation + * + */ + +/* + * Copyright (C) 2022 Prashanth S + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source

[PATCH v4] cpukit/dev/can: Added CAN support

+ * + * @brief Controller Area Network (CAN) Bus Implementation + * + */ + +/* + * Copyright (C) 2022 Prashanth S + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source

Re: [PATCH] cpukit/dev/can: Added CAN support

later merge-ready patch. Yes, these sleeps will be removed. > Do these really have to be in a header that you (most likely) will later > install? With that they are public visible API. On Tue, 2 Aug 2022 at 23:19, wrote: > Hello Duc, > > general note:

Re: devel Digest, Vol 129, Issue 37

Hi All, This is a review request for DCAN (Work in Progress) support. As the patch size exceeds the mail limit, I am attaching the patch in compressed format. Regards Prashanth S Prashanth S On Sun, 14 Aug 2022 at 13:56, wrote: > > Send devel mailing list submissions to >

[PATCH v4] cpukit/dev/can: Added CAN support

00..02377a9098 --- /dev/null +++ b/cpukit/dev/can/can.c @@ -0,0 +1,521 @@ +/* SPDX-License-Identifier: BSD-2-Clause */ + +/** + * @file + * + * @ingroup CANBus + * + * @brief Controller Area Network (CAN) Bus Implementation + * + */ + +/* + * Copyright (C) 2022 Prashanth S (fishesprasha

[PATCH] cpukit/dev/can: Added CAN support

..8feec8800b --- /dev/null +++ b/cpukit/dev/can/can.c @@ -0,0 +1,514 @@ +/* SPDX-License-Identifier: BSD-2-Clause */ + +/** + * @file + * + * @ingroup CANBus + * + * @brief Controller Area Network (CAN) Bus Implementation + * + */ + +/* + * Copyright (C) 2022 Prashanth S (fishesprasha...@gmail.com

[PATCH] cpukit/dev/can: Added CAN support (Prashanth S)

Hi All, This is a review request for CAN support. I have addressed the review comments. The files are work in progress, I need to add few more comments in the include (*.h) files. Regards Prashanth S On Sun, 31 Jul 2022 at 17:24, wrote: > Send devel mailing list submissi

Re: [PATCH] cpukit/dev/can: Added CAN support

Hi Christian, Oops, I apologize. I think I used gmail style quotes that might have added html. I will not use it. Regards Prashanth S On Mon, 8 Aug 2022 at 05:31, Chris Johns wrote: > Hi > > Could you please configure your email client to not send HTML emails to > the list? > &

Re: [PATCH 1/4] cpukit/include/dev/can: Added debug print configuration under RTEMS_CAN_DEBUG macro.

Hi All, This is a reminder for review requests for the patches to CAN Framework changes based on review comments. Regards Prashanth S On Fri, 16 Dec 2022 at 18:58, Prashanth S wrote: > --- > cpukit/include/dev/can/can.h | 27 +-- > 1 file changed, 21 inserti

[PATCH 1/2] testsuites/libtests/can01: Serialize CAN write and read messages among the tasks

The CAN framework has minimal Rx implementation, so to test loopback driver the test application is modified to write and read atomically --- testsuites/libtests/can01/init.c | 71 ++-- 1 file changed, 31 insertions(+), 40 deletions(-) diff --git

[PATCH 2/2] cpukit/dev/can: Fix 64 bit build compilation warnings

--- cpukit/dev/can/can.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cpukit/dev/can/can.c b/cpukit/dev/can/can.c index 7098ce16c2..2462df7e25 100644 --- a/cpukit/dev/can/can.c +++ b/cpukit/dev/can/can.c @@ -204,7 +204,7 @@ static ssize_t can_bus_read(rtems_libio_t *iop,

[PATCH 2/4] cpukit/dev/can: Removed extra debug prints in CAN Framework

--- cpukit/dev/can/can.c | 20 1 file changed, 20 deletions(-) diff --git a/cpukit/dev/can/can.c b/cpukit/dev/can/can.c index 2e6d5df65b..7098ce16c2 100644 --- a/cpukit/dev/can/can.c +++ b/cpukit/dev/can/can.c @@ -73,19 +73,14 @@ static int try_sem(struct can_bus *); static

[PATCH 1/4] cpukit/include/dev/can: Added debug print configuration under RTEMS_CAN_DEBUG macro.

--- cpukit/include/dev/can/can.h | 27 +-- 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/cpukit/include/dev/can/can.h b/cpukit/include/dev/can/can.h index 9e55395039..4ee51ebc9d 100644 --- a/cpukit/include/dev/can/can.h +++ b/cpukit/include/dev/can/can.h

[PATCH 4/4] cpukit/dev/can: Fix 64 bit build compilation warnings

--- cpukit/dev/can/can.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cpukit/dev/can/can.c b/cpukit/dev/can/can.c index 7098ce16c2..ca855951d5 100644 --- a/cpukit/dev/can/can.c +++ b/cpukit/dev/can/can.c @@ -203,7 +203,7 @@ static ssize_t can_bus_read(rtems_libio_t *iop,

[PATCH 1/4] cpukit/include/dev/can: Added debug print configuration under RTEMS_CAN_DEBUG macro.

--- cpukit/include/dev/can/can.h | 27 +-- 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/cpukit/include/dev/can/can.h b/cpukit/include/dev/can/can.h index 9e55395039..4ee51ebc9d 100644 --- a/cpukit/include/dev/can/can.h +++ b/cpukit/include/dev/can/can.h

[PATCH 3/4] testsuites/libtests/can01: Serialize CAN write and read messages among the tasks

The CAN framework has minimal Rx implementation, so to test loopback driver the test application is modified to write and read atomically --- testsuites/libtests/can01/init.c | 69 ++-- 1 file changed, 30 insertions(+), 39 deletions(-) diff --git

[PATCH 2/4] cpukit/dev/can: Removed extra debug prints in CAN Framework

--- cpukit/dev/can/can.c | 20 1 file changed, 20 deletions(-) diff --git a/cpukit/dev/can/can.c b/cpukit/dev/can/can.c index 2e6d5df65b..7098ce16c2 100644 --- a/cpukit/dev/can/can.c +++ b/cpukit/dev/can/can.c @@ -73,19 +73,14 @@ static int try_sem(struct can_bus *); static

Re: [PATCH 1/2] testsuites/libtests/can01: Serialize CAN write and read messages among the tasks

hread id and error message. Can we have this information printed by expanded macro or change to printf? On Thu, 15 Dec 2022 at 02:57, Gedare Bloom wrote: > On Sat, Dec 3, 2022 at 2:02 AM Prashanth S > wrote: > > > > The CAN framework has minimal Rx impleme

Re: [PATCH 1/4] cpukit/include/dev/can: Added debug print configuration under RTEMS_CAN_DEBUG macro.

Gedare Bloom wrote: > How does this debugging get turned on/off? > > > On Sat, Dec 3, 2022 at 2:00 AM Prashanth S > wrote: > > > > --- > > cpukit/include/dev/can/can.h | 27 +-- > > 1 file changed, 21 insertions(+), 6 deletions(-)

Re: [PATCH 1/2] testsuites/libtests/can01: Serialize CAN write and read messages among the tasks

gt; Can we have this information printed by expanded macro or change to >> printf? > >The RTEMS Test Framework does all this. Why do we have to implement >things specifically for this test? Ok, updating CAN_ERR to printf. Regards Prashanth S ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: CAN Framework Docs for RTEMS-DOCS

Hi All, This is a review request for CAN Framework docs. I pasted the link to gitlab, as the patch size exceeds the mailing list limit. https://gitlab.com/slpp95prashanth/gsoc-2022/-/commit/869438a9da4a31a69f8d2718d5789d76fe209929 Regards Prashanth S On Mon, 14 Nov 2022 at 20:03, Prashanth S

[PATCH] cpukit/include/dev/can: Disabled debug prints in CAN Framework

--- cpukit/include/dev/can/can.h | 2 +- testsuites/libtests/can01/init.c | 14 -- 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/cpukit/include/dev/can/can.h b/cpukit/include/dev/can/can.h index 9e55395039..27afd00088 100644 --- a/cpukit/include/dev/can/can.h +++

Re: [PATCH] cpukit/include/dev/can: Disabled debug prints in CAN Framework

>On Mon, Nov 28, 2022 at 8:46 PM Prashanth S wrote: >> >> --- >> cpukit/include/dev/can/can.h | 2 +- >> testsuites/libtests/can01/init.c | 14 -- >> 2 files changed, 9 insertions(+), 7 deletions(-) >> >> diff --git a/cpukit/i

Re: [PATCH] cpukit/include/dev/can: Disabled debug prints in CAN Framework

ceived? > > > > Yes, and you probably know also the expected content of the message. > This should be also checked. If there are ordering guarantees, then each > message should have a unique content and the ordering should be checked > as well. The CAN framework has only m

Re: [PATCH] cpukit/include/dev/can: Disabled debug prints in CAN Framework

>On Tue, Nov 29, 2022 at 6:58 AM Prashanth S wrote: >> >> > On 29/11/2022 05:57, Gedare Bloom wrote: >> > >> @@ -111,18 +113,18 @@ static void test_task(rtems_task_argument data) >> > >> >> > >> msg_size = ((char *)[msg.len] -

Re: [PATCH] cpukit/include/dev/can: Disabled debug prints in CAN Framework

>etc etc etc > >Can these please be fixed? Use #4662. Yes, I will typecast the value returned by sizeof(). Regards Prashanth S On Fri, 2 Dec 2022 at 09:09, Chris Johns wrote: > The CAN bus changes have warnings ... > > In file included from ../../../cpukit/include/dev/

Re: [PATCH] c-user: CAN framework docs

he CAN framework and its usage by BSP CAN drivers and > Remove the comma after covers > typo: Initialize > typo: Further I will update these typo errors. Regards Prashanth S On Tue, 15 Nov 2022 at 20:34, Gedare Bloom wrote: > Hi Prashant, > > What are the images? >

Re: CAN Framework Docs for RTEMS-DOCS

Hi All, This is a reminder for the CAN framework docs written with .uml diagrams. Regards Prashanth S On Fri, 25 Nov 2022 at 20:07, Prashanth S wrote: > Hi All, > > This is a review request for CAN Framework docs. > > I pasted the link to gitlab, as the patch size exceeds t

CAN Framework Docs for RTEMS-DOCS

Hi All, I have pasted the link to CAN framework docs for rtems-docs. As the patch size exceeds the mailing list, so pasted the link to GitLab. https://gitlab.com/slpp95prashanth/gsoc-2022/-/commit/01bd99dd8228128fdb5189e65ffa198312012d34 Regards Prashanth S

Re: CAN driver implementation for Xilinx Zynq

Hi @carlo.broker...@dlr.de , Once the commands are defined the corresponding command and buffer should be passed as arguments. As the commands are not defined Null and zero are passed as buffer and command respectively. Regards Prashanth S On Thu, 2 Mar, 2023, 2:22 pm , wrote: > He

Re: CAN driver implementation for Xilinx Zynq

vice specific commands (To add commands for hardware independent functionality the commands can be added before "if (bus == NULL || bus->can_dev_ops->dev_ioctl == NULL)" statement. struct can_dev_ops dev_ops (.dev_ioctl member should be registered). > > > @Prashanth S (fi

Re: CAN driver implementation for Xilinx Zynq

LL, 0); The ioctl commands are not defined for the CAN framework, so NULL and 0 are passed to dev_ioctl. Regards Prashanth S On Wed, 1 Mar 2023 at 21:08, wrote: > Hello Prashanth S, > > > > the design for the rx data path including the RxFIFO looks promising. If > nobody i