Re: Change Control Board (CCB) proposal for requirements (v2)

On 25/07/2019 01:17, Joel Sherrill wrote: On Wed, Jul 24, 2019 at 1:39 AM Sebastian Huber > wrote: Hello, I work currently on a requirements engineering section for RTEMS in the RTEMS Software Engineering manual:

Re: assistance needed in bumping newlib version

On 24/07/2019 22:11, Joel Sherrill wrote: I got this error from github. I was bumping the newlib hash to get ndbm. download: (full) https://codeload.github.com/RTEMS/sourceware-mirror-newlib-cygwin/tar.gz/6b843b8 -> sources/newlib-6b843b8.tar.gz download:

Re: GSoC Project | Basic Support for Trace Compass

On 25/07/2019 06:34, Ravindra Kumar Meena wrote: Being not equal is necessary but not sufficient. Your code is too complicated.  Please try to simplify it.  Avoid the magic numbers and use the enumerator constants instead. Okay Why do you use values from

Re: GSoC Project | Basic Support for Trace Compass

> > Being not equal is necessary but not sufficient. > > Your code is too complicated. Please try to simplify it. Avoid the > magic numbers and use the enumerator constants instead. > Okay > > Why do you use values from RTEMS_RECORD_THREAD_STACK_CURRENT for the > sched_switch? Do you know what

GSoC 2019 : Basic support for Trace Compass

Hello all, This is a mail to update my weekly status since the meeting got canceled this week. Progress so far: * Added compact header in both client-side and metadata. * Imported trace in Trace Compass with the updated event.header in the metadata. Trace Compass can still read the values. *

Re: Change Control Board (CCB) proposal for requirements (v2)

On Wed, Jul 24, 2019 at 1:39 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > I work currently on a requirements engineering section for RTEMS in the > RTEMS Software Engineering manual: > > https://docs.rtems.org/branches/master/eng/index.html > > One topic is the

Re: assistance needed in bumping newlib version

On 25/7/19 8:23 am, Chris Johns wrote: > Has the repo been updated with the upstream? It might be a manual operation. I > am not sure if there are any instructions available on doing this. I am also > not > aware of any jobs on our servers to handle this. The repo looks updated. Chris

Re: assistance needed in bumping newlib version

On 25/7/19 6:11 am, Joel Sherrill wrote: > Hi > > I got this error from github. I was bumping the newlib hash to get ndbm. > > download: (full) > https://codeload.github.com/RTEMS/sourceware-mirror-newlib-cygwin/tar.gz/6b843b8 > -> sources/newlib-6b843b8.tar.gz > download: >

Re: GSoC Status update : BBB Framebuffer Project

Am Mittwoch, 24. Juli 2019 schrieb Vijay Kumar Banerjee: > > > > > On Thu, Jul 25, 2019 at 1:17 AM Vijay Kumar Banerjee > wrote: > > > > > > > > > > On Thu, Jul 25, 2019 at 1:09 AM Christian Mauderer wrote: > > Hello Vijay, > > On 24/07/2019 18:14, Vijay Kumar Banerjee wrote: >

assistance needed in bumping newlib version

Hi I got this error from github. I was bumping the newlib hash to get ndbm. download: (full) https://codeload.github.com/RTEMS/sourceware-mirror-newlib-cygwin/tar.gz/6b843b8 -> sources/newlib-6b843b8.tar.gz download:

Re: GSoC Status update : BBB Framebuffer Project

On Thu, Jul 25, 2019 at 1:17 AM Vijay Kumar Banerjee < vijaykumar9...@gmail.com> wrote: > > > > > On Thu, Jul 25, 2019 at 1:09 AM Christian Mauderer > wrote: > >> Hello Vijay, >> >> On 24/07/2019 18:14, Vijay Kumar Banerjee wrote: >> > Hello all, >> > >> > This is a mail to update my weekly

Re: GSoC Status update : BBB Framebuffer Project

On Thu, Jul 25, 2019 at 1:09 AM Christian Mauderer wrote: > Hello Vijay, > > On 24/07/2019 18:14, Vijay Kumar Banerjee wrote: > > Hello all, > > > > This is a mail to update my weekly status since the meeting got > > canceled this week. > > Sorry for that. > > > > > Progress: > > * Completed

Re: GSoC Status update : BBB Framebuffer Project

Hello Vijay, On 24/07/2019 18:14, Vijay Kumar Banerjee wrote: > Hello all, > > This is a mail to update my weekly status since the meeting got > canceled this week. Sorry for that. > > Progress: > * Completed mmap patch > : https://lists.rtems.org/pipermail/devel/2019-July/026680.html > This

Re: RTEMS Software Coding Standard

On Wed, Jul 24, 2019 at 11:39 AM Manuel Coutinho wrote: > Regarding MISRA, we are not suggesting to have all the rules. Only the > ones that are automatically verified by a tool that we can use and only > those that make sense for the community. > MISRA is not open, that is understood. But there

Re: GSoC 2019 : POSIX Compliance- Low pace in last week

On Wed, Jul 24, 2019, 9:44 PM Joel Sherrill wrote: > Hi > > I have some progress to report on this. The ndbm patch is in newlib git > now but > the corresponding files were not regenerated. Once Corinna pushes those, I > will > test and bump the newlib version in the tools. > Corinna just did

GSoC 2019 : POSIX Compliance - Weekly Report

Hello, Progress so far: - NDBM patch is pushed by newlib. - NDBM Testsuite is sent to devel ([PATCH V6] ndbm test suite), its execution will be verified once newlib has required files. Although I have tested it by manually generating required file using 'autoreconf -fvi' on my local system.

RE: RTEMS Software Coding Standard

Regarding MISRA, we are not suggesting to have all the rules. Only the ones that are automatically verified by a tool that we can use and only those that make sense for the community. MISRA is not open, that is understood. But there are some sources

Re: GSoC 2019 : POSIX Compliance- Low pace in last week

On Wed, Jul 24, 2019 at 9:44 PM Joel Sherrill wrote: > Hi > > I have some progress to report on this. The ndbm patch is in newlib git > now but > the corresponding files were not regenerated. Once Corinna pushes those, I > will > test and bump the newlib version in the tools. > Thanks, Yah I saw

GSoC Status update : BBB Framebuffer Project

Hello all, This is a mail to update my weekly status since the meeting got canceled this week. Progress: * Completed mmap patch : https://lists.rtems.org/pipermail/devel/2019-July/026680.html This patch is pending approval. I'm not sure if it was supposed to be merged or will it be merged after

Re: GSoC 2019 : POSIX Compliance- Low pace in last week

Hi I have some progress to report on this. The ndbm patch is in newlib git now but the corresponding files were not regenerated. Once Corinna pushes those, I will test and bump the newlib version in the tools. I see you have a test posted and once I have tools, I will be able to review that

GSoC 2019 : POSIX Compliance- Low pace in last week

Hello, I want to apologise that I couldn't inform earlier, actually my time table got hectic. My college started last week and their initial time table is not much useful in terms of productivity. Hence my pace got slow last week. I am back on track and continuing with my fenv task. Thank you

GSoC Weekly IRC Meeting PRU

Hi, Since this weeks IRC meeting has been canceled, we were asked to post on devel. *What I did this week:* - I Ported the BSD pruss driver over to rtems-libbsd. - Moved the driver from my application to the rtems-libbsd repository, it makes more sense to develop it there I think.

Re: [rtems-docs commit] eng: Add bibliography

Hi Where possible, can we mirror the references to the ftp site? --joel On Wed, Jul 24, 2019 at 8:42 AM Sebastian Huber wrote: > Module:rtems-docs > Branch:master > Commit:735bcd765ab64aefa0fc9012d2143490fe090c8a > Changeset: >

Re: GSoC PRU: AM35xx Clock driver

Hi, @Vijay Kumar Banerjee thanks for the dtb file. I build my file from FreeBSD master. Prcm attaches now but still after the pruss driver...: " nexus0: ofwbus0: on nexus0 simplebus0: on ofwbus0 *ti_pruss0: mem 0x4a30-0x4a37 irq 20,21,22,23,24,25,26,27 on simplebus0ti_pruss0:

Re: [PATCH] eng: Add Software Requirements Engineering chapter

Hello, this is my first attempt to add a "Software Requirements Engineering" chapter to the RTEMS Software Engineering manual. You can find a PDF with this patch here: https://ftp.rtems.org/pub/rtems/people/sebh/eng.pdf I removed the binary files from the patch. -- Sebastian Huber,

[PATCH] eng: Add Software Requirements Engineering chapter

--- eng/index.rst | 1 + eng/req-eng.rst | 813 ++ images/eng/req-add.pdf| Bin 0 -> 81320 bytes images/eng/req-add.png| Bin 0 -> 50516 bytes images/eng/req-add.uml| 40 +++ images/eng/req-modify.pdf | Bin 0 ->

Re: GSoC PRU: AM35xx Clock driver

On Wed, 24 Jul 2019 at 15:14, Vijay Kumar Banerjee wrote: > > > > On Wed, Jul 24, 2019 at 6:36 PM Nils Hölscher wrote: > >> Hi again, >> >> Hi Nils > >> I just decompiled my device tree and checked. >> The probe code of the prcm driver is as follows: >> " >> static int >>

Addition of Rule Checkers

Hi I just wanted to make sure we followed proper procedures and policies when considering rule checkers. 1. The license must appropriate. 2. There should be some basic requirements that the tool is expected to meet to be fit for purpose 3. The tool must support the range of development hosts

Re: GSoC PRU: AM35xx Clock driver

On Wed, Jul 24, 2019 at 6:36 PM Nils Hölscher wrote: > Hi again, > > Hi Nils > I just decompiled my device tree and checked. > The probe code of the prcm driver is as follows: > " > static int > am335x_prcm_probe(device_t dev) > { > printk("am335x_prcm_probe\n"); > > if

Re: GSoC PRU: AM35xx Clock driver

Hi again, I just decompiled my device tree and checked. The probe code of the prcm driver is as follows: " static int am335x_prcm_probe(device_t dev) { printk("am335x_prcm_probe\n"); if (!ofw_bus_status_okay(dev)){ printk("ofw_bus_status_not_okay\n"); return (ENXIO);

Re: GSoC PRU: AM35xx Clock driver

Hi, I just found out that the prcm driver fails to probe on the simplebus and therefore cannot apply itself. Seems like I am back to checking dtb. Best, Nils On Tue, 23 Jul 2019 at 14:26, Nils Hölscher wrote: > Hi, > > After debugging with printk, didn't get the module loading working as >

Re: GSoC Project | Basic Support for Trace Compass

On 24/07/2019 14:07, Ravindra Kumar Meena wrote: You received RTEMS_RECORD_THREAD_SWITCH_OUT two record events before the   RTEMS_RECORD_THREAD_SWITCH_IN with the same timestamp. See my comment above. In these two record events all you need for the sched_switch event is

Re: GSoC Project | Basic Support for Trace Compass

> > You received RTEMS_RECORD_THREAD_SWITCH_OUT two record events before the > RTEMS_RECORD_THREAD_SWITCH_IN with the same timestamp. See my comment > above. In these two record events all you need for the sched_switch > event is contained. > Have made changes:

Re: RTEMS Software Coding Standard

On Wed, Jul 24, 2019, 3:59 AM Manuel Coutinho wrote: > Hello all, > > It has been some time since my last email. Hope you are doing well! > > Some of you already know that Edisoft together with Embedded Brains (and > some other institutions) are in a joint project to pre-qualify RTEMS >

Re: GSoC Project | Basic Support for Trace Compass

On 24/07/2019 11:04, Ravindra Kumar Meena wrote: This approach makes no sense to me. Per CPU you receive three record events in succession: [19:32:26.679099590] (+0.46608) Record_Item RTEMS_RECORDING_EVENT: { cpu_id = 5 }, { event = ( "RTEMS_RECORD_THREAD_SWITCH_OUT" :

Re: GSoC Project | Basic Support for Trace Compass

> > This approach makes no sense to me. > > Per CPU you receive three record events in succession: > > [19:32:26.679099590] (+0.46608) Record_Item RTEMS_RECORDING_EVENT: { > cpu_id = 5 }, { event = ( "RTEMS_RECORD_THREAD_SWITCH_OUT" : container = > 216 ), data = 167837707 } >

RTEMS Software Coding Standard

Hello all, It has been some time since my last email. Hope you are doing well! Some of you already know that Edisoft together with Embedded Brains (and some other institutions) are in a joint project to pre-qualify RTEMS according to the ESA (ECSS) standards. One of the items required is the

Change Control Board (CCB) proposal for requirements (v2)

Hello, I work currently on a requirements engineering section for RTEMS in the RTEMS Software Engineering manual: https://docs.rtems.org/branches/master/eng/index.html One topic is the Change Control Board (CCB). The Doorstop maintainer was not so fond of my idea to add support for digital