Large number of failures on leon3

[Joel Sherrill]

Hi

I was following up on Gedare's testing and tried leon3. There
were a surprising number of failures there with SMP disabled.
This is testing with gdb. Does anyone else get the same
results with qemu or tsim?  Any idea what's broken?


Passed:   458
Failed:20
Timeouts:  73
Invalid:3
-
Total:554

Failures:
 cdtest.exe
 spintrcritical20.exe
 dl05.exe
 spintrcritical01.exe
 spintrcritical04.exe
 spintrcritical10.exe
 spintrcritical22.exe
 sp69.exe
 spintrcritical21.exe
 sp11.exe
 spintrcritical16.exe
 spintrcritical23.exe
 psxfile01.exe
 spintrcritical05.exe
 spintrcritical02.exe
 spintrcritical08.exe
 psxgetrusage01.exe
 spcpucounter01.exe
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSOC 2017 apply

[Gedare Bloom]

As soon as you have gotten a good idea of what project you want to do,
send a brief description of it to make sure it is of a good value
before you put all your effort into making the proposal.

On Sat, Mar 18, 2017 at 2:47 AM, 赵 思晨  wrote:
> Hi all:
>
> My name is Sichen Zhao, and i already fill in the table in the rtems gsoc
> wiki, now working on the proposal.
>
> So there is anything i can do?
>
>
> 发自 Outlook
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: PI STATUS

[Gedare Bloom]

On Sat, Mar 18, 2017 at 4:59 PM, Sagar Gupta
 wrote:
> Hi Gedare
>
> I was looking at the ticket #2733(Related to your SPI issues) and potential
> project for GSoc 2017 for Raspberry Pi
> the one I find interesting is "Convert the existing SPI support to the new
> Linux SPI API and test with SPI devices".
>
> I have gone through the wordpress bolg(https://asuolgsoc2014.wordpress.com/)
> of André Marques to understand the SPI API developed by him as a part of
> GSoc 14,15 . I am going through his code which he commited in RTEMS
> repository in GitHub
> (https://github.com/RTEMS/rtems/commit/61e7c698a44137afbc1447ed328b14a0d9e55016)
>
> I have also gone through blog post of  Mudit
> Jain(http://rtemsgsoc2016-mudit.blogspot.in/) also i have gone through code
> which he commited in RTEMS repository in GitHub
> (https://github.com/RTEMS/rtems/commit/48704cdebdd40391c5ca8d8020e5a77edff37677).
>
> I have also read about how to port drivers from FreeBSD to Rtems/libBSD as
> posted by Ragunath in his blog post
> (http://ragustechblog.blogspot.in/2015/06/porting-driver-from-freebsd-to-rtems.html)
> .
>
> I have also read the Alan Blog
> post(http://alanstechnotes.blogspot.in/2013/04/setting-up-rtems-development.html)
> on how to compile GCC and RTEMS for arms and I am trying to get that running
> on my system . I will share the results as soon as I finish with the
> community.
>
Alan's blog post may be outdated by now.

>
> For the project the API which is refered to is that André Marques developed
> ?
> What is the new Linux here been refered to?
The Linux API is defined under cpukit/dev

> Can you please tell me the basic structue of what is to be implemented as
> the part for this project.
>
I don't know which  BSP already implements one, but you can probably
search for an include of  dev/spi.h in the libbsp to figure that out.

>
> On Mon, Mar 6, 2017 at 6:17 PM, Gedare Bloom  wrote:
>>
>> On Sun, Mar 5, 2017 at 12:24 PM, Alan Cudmore 
>> wrote:
>> > Hi everyone,
>> > This is how far I was able to get when trying to run libBSD on the Pi. I
>> > will give you a better idea of where to start.
>> > https://lists.rtems.org/pipermail/devel/2016-September/016092.html
>> > Since then, the libbsd version has been updated in RTEMS, so it may need
>> > some work to get it to compile again.
>> >
>> > Here is a general status as I understand it:
>> > RTEMS ( without bsdlib ) works on the original Pi model B, Pi A+, Pi B+,
>> > Pi
>> > Zero, and the Pi 2.
>> > SMP works on the Pi 2.
>> >
>> > RTEMS does not work on the Pi 3 yet, The UART that the current BSPs use
>> > as a
>> > console is now used by the Bluetooth.
>> > So a new UART driver has to be written for the "mini-uart" that serves
>> > as
>> > the console on the Pi3.
>> > I believe the same applies to the new Raspberry Pi Zero W, which has the
>> > same Bluetooth wireless stack.
>> >
>> >
>> > We have been working on I2C, SPI, and GPIO support.
>> > I2C has been converted to the new linux user API, but SPI has not.
>> > GPIO and I2C work, but I have not been able to get my SPI devices to
>> > work.
>> >
>> > So potential Raspberry Pi work includes:
>> > Convert the existing SPI support to the new Linux SPI API and test with
>> > SPI
>> > devices
>> > Continue to work on the LibBSD support
>> > Support the Pi Zero W ( and potentially the Pi 3 ) by creating a new
>> > uart
>> > driver
>> > Support Pi 3 SMP ( along with the UART )
>> >
>> > Even more advanced work could include:
>> > Support the Wifi and bluetooth in LibBSD for the Pi Zero W and/or Pi 3.
>> >
>> > Gedare, I know this should probably be on the GSOC wiki, right  ?
>> >
>>
>> I added to the relevant open project ticket:
>> https://devel.rtems.org/ticket/2899
>>
>> Related to your SPI issues may be: https://devel.rtems.org/ticket/2733
>>
>> > Alan
>> >
>> >
>> > On Sun, Mar 5, 2017 at 7:49 AM, Gedare Bloom  wrote:
>> >>
>> >> Hello Sagar Gupta,
>> >>
>> >> The best place to start is with the previous GSoC effort that focused
>> >> on Raspberry PI. This was last year's project
>> >> https://devel.rtems.org/wiki/GSoC/2016/USB%26EthernetRaspberryPi
>> >>
>> >>
>> >>
>> >> On Sat, Mar 4, 2017 at 2:21 AM, Sagar Gupta
>> >>  wrote:
>> >> > Hi ,
>> >> >
>> >> > I have done a course on Operating Systems at undergraduate level.
>> >> > I am specifically interested in development of drivers for operating
>> >> > systems
>> >> > which work on hardware such as the Raspberry Pi.
>> >> > Can I get to know what are the potential projects for Raspberry pi in
>> >> > GSoc'17 ?
>> >> > also can you guide me to such threads, projects, documentation which
>> >> > could
>> >> > be be helpful for the same.
>> >> >
>> >> > Thanks
>> >> >
>> >> > Warm Regards,
>> >> > Sagar Gupta
>> >> > Phone : +91 8686146518
>> >> > Computer Science Student
>> >> > BITS Pilani , Hyderabad Campus
>> >> >
>> >> > ___
>> >> > devel mailing list
>> >> > devel@rtems.org
>> >> > http://lists.rtems.org/mailm

Re: GSOC 2017

[Gedare Bloom]

Contact the potential mentors for your project to solicit their
feedback and/or give a more descriptive email subject related to your
project topic to garner interest.

On Sat, Mar 18, 2017 at 10:14 PM, 赵 思晨  wrote:
> Hi All:
>
> I already finished the proposals on RTEMS GSOC wiki.
>
> Best Regards
> Sichen Zhao
>
>
> 发自 Outlook
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

GSOC 2017 Beagleboard BSP projects

[赵 思晨]

Hi all:


I am interested in the ticket #2819 Beagleboard BSP projects


And i have a idea about the project: add the USB and wireless network card 
driver to RTEMS. So RTEMS can apply on many scene applications such as the UAV. 
And for now, i am working on transplant the USB driver from FreeBSD to RTEMS.



I am a master student from China NanJing University. and i am interested in 
applying for GSoC 2017 under RTEMS.
I have develop project on RTEMS for almost a year, so i am very familiar with 
RTEMS development.

For now, i have done these works on RTEMS:
1.Porting the ethernet driver from FreeBSD to RTEMS on BBB bsp.
2.Transplant the ION-DTN protocol stack on RTEMS.
3.Took over Punitvara's(GSOC 2016 student) unfinished work on BBB i2c driver, 
and can use i2c read the EEPROM info..(already send PV my pull request)
4.Porting  the ethernet driver from UBoot to RTEMS on BBB bsp.

Best Regrads
Sichen Zhao




发自 Outlook
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Queries regarding Tracing related bugs and GSoC 2017

[vivek kukreja]

Hello developers,

I have worked on CTF tracing last year under GSoC. I was working on my
previous deliverables and i noticed there are some bugs in the current
capture and function tracing examples on qemu for arm/xilinx_zynq_a9,
related to recent updates made to TCB and termios implementation. I'm
working on resolving these issues so I can merge my previous changes.
I have mailed Chris regarding this and I was suggested to ping the
developer list for further clarification on these errors, and whether
I should create any tickets.

I also wanted to enquire about the status of the Live tracing project
this year in GSoC. I'm considering the following ideas for a proposal,
once the tracing support is re-established:

1. libDWARF integration: I've been studying libDWARF for
functionalities that can be ported to RTEMS, for the purpose of
finding function signatures and variable types to be traced by the
trace linker. This can be used to auto-configure the signatures/types
at the trace linking phase of an application.

2. Transports API: In GSoC 2016 I worked on transport for moving
traces to host. I investigated serial and USB transport apart from
ethernet using libBSD. There is discussion on the Tracing projects
page about integrating all transports and providing an API for custom
transports in the application for both capture and function tracing.

3. Live tracing: In capture tracing, the trace process has to be
paused before reading the trace (as discussed with Jennifer Averrett,
the previous contributor). I'm looking at alternatives like copying
the unsafe buffer to a new one which can in turn be dumped on host
using NFS or other transport options. We can create a low priority
task for this purpose, along with the trace buffering functions
defined in rtld-trace-buffer.ini.

Please suggest any improvements or additions to the above ideas. Also
I dont know if there is any interest in this project for GSoC 2017 but
I would like to merge my previous changes soon nonetheless.

Regards,
Vivek
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Large number of failures on leon3

[Jiri Gaisler]

This could also be a simulator issue, the leon3 port of sis is quite
new. I will investigate a bit.

Jiri.


On 03/19/2017 02:32 PM, Joel Sherrill wrote:
> Hi
>
> I was following up on Gedare's testing and tried leon3. There
> were a surprising number of failures there with SMP disabled.
> This is testing with gdb. Does anyone else get the same 
> results with qemu or tsim?  Any idea what's broken?
>
>
> Passed:   458
> Failed:20
> Timeouts:  73
> Invalid:3
> -
> Total:554
>
> Failures:
>  cdtest.exe
>  spintrcritical20.exe
>  dl05.exe
>  spintrcritical01.exe
>  spintrcritical04.exe
>  spintrcritical10.exe
>  spintrcritical22.exe
>  sp69.exe
>  spintrcritical21.exe
>  sp11.exe
>  spintrcritical16.exe
>  spintrcritical23.exe
>  psxfile01.exe
>  spintrcritical05.exe
>  spintrcritical02.exe
>  spintrcritical08.exe
>  psxgetrusage01.exe
>  spcpucounter01.exe
>
>
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel

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

Re: GSOC 2017 Beagleboard BSP projects

[Christian Mauderer]

- Ursprüngliche Mail -
> Von: "赵 思晨" 
> An: "RTEMS" 
> Gesendet: Sonntag, 19. März 2017 15:29:03
> Betreff: GSOC 2017 Beagleboard BSP projects

> Hi all:
> 
> 
> I am interested in the ticket #2819 Beagleboard BSP projects
> 
> 
> And i have a idea about the project: add the USB and wireless network card
> driver to RTEMS. So RTEMS can apply on many scene applications such as the 
> UAV.
> And for now, i am working on transplant the USB driver from FreeBSD to RTEMS.
> 
> 
> 
> I am a master student from China NanJing University. and i am interested in
> applying for GSoC 2017 under RTEMS.
> I have develop project on RTEMS for almost a year, so i am very familiar with
> RTEMS development.
> 
> For now, i have done these works on RTEMS:
> 1.Porting the ethernet driver from FreeBSD to RTEMS on BBB bsp.
> 2.Transplant the ION-DTN protocol stack on RTEMS.
> 3.Took over Punitvara's(GSOC 2016 student) unfinished work on BBB i2c driver,
> and can use i2c read the EEPROM info..(already send PV my pull request)
> 4.Porting  the ethernet driver from UBoot to RTEMS on BBB bsp.
> 
> Best Regrads
> Sichen Zhao
> 
> 
> 
> 
> 发自 Outlook
> 
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel

Hello Sichen Zhao,

just a note regarding the WLAN support in rtems-libbsd: I have just recently 
ported a lot of the necessary kernel modules for unencrypted WLAN. Depending on 
the projects progress, It's quite possible that we (embedded brains) will work 
on encrypted WLAN too in the near future. So this might could collide with the 
goals in your proposal that relate to the hardware independent parts of the 
network stack.

Kind regards

Christian Mauderer
-- 

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.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: timeouts and failure

[Chris Johns]

On 19/03/2017 07:52, Joel Sherrill wrote:


That is much better than yours and is really only the known
spcontext01.exe failure.



Please tag the test as expected-fail.

Thanks
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

答复: GSOC 2017 Beagleboard BSP projects

[赵 思晨]

Hi Christian Mauderer:


I understand what you mean, the network stack is the last goal i wanna achieve.

My main goal is :
1. Finishing the I2C driver(last GSOC unfinished work)

2.Adding the USB driver on BBB, such as mass storage, keyboard input etc.


So maybe  it is not collide with my goals so much.


Best Regards

Sichen Zhao


发自 Outlook

发件人: Christian Mauderer 
发送时间: 2017年3月20日 5:38:09
收件人: 赵 思晨
抄送: RTEMS
主题: Re: GSOC 2017 Beagleboard BSP projects

- Ursprüngliche Mail -
> Von: "赵 思晨" 
> An: "RTEMS" 
> Gesendet: Sonntag, 19. März 2017 15:29:03
> Betreff: GSOC 2017 Beagleboard BSP projects

> Hi all:
>
>
> I am interested in the ticket #2819 Beagleboard BSP projects
>
>
> And i have a idea about the project: add the USB and wireless network card
> driver to RTEMS. So RTEMS can apply on many scene applications such as the 
> UAV.
> And for now, i am working on transplant the USB driver from FreeBSD to RTEMS.
>
>
>
> I am a master student from China NanJing University. and i am interested in
> applying for GSoC 2017 under RTEMS.
> I have develop project on RTEMS for almost a year, so i am very familiar with
> RTEMS development.
>
> For now, i have done these works on RTEMS:
> 1.Porting the ethernet driver from FreeBSD to RTEMS on BBB bsp.
> 2.Transplant the ION-DTN protocol stack on RTEMS.
> 3.Took over Punitvara's(GSOC 2016 student) unfinished work on BBB i2c driver,
> and can use i2c read the EEPROM info..(already send PV my pull request)
> 4.Porting  the ethernet driver from UBoot to RTEMS on BBB bsp.
>
> Best Regrads
> Sichen Zhao
>
>
>
>
> 发自 Outlook
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel

Hello Sichen Zhao,

just a note regarding the WLAN support in rtems-libbsd: I have just recently 
ported a lot of the necessary kernel modules for unencrypted WLAN. Depending on 
the projects progress, It's quite possible that we (embedded brains) will work 
on encrypted WLAN too in the near future. So this might could collide with the 
goals in your proposal that relate to the hardware independent parts of the 
network stack.

Kind regards

Christian Mauderer
--

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.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: timeouts and failure

[Sebastian Huber]

On 18/03/17 21:52, Joel Sherrill wrote:


FWIW here are my results for sparc/erc32:

Passed:   548
Failed: 1
Timeouts:   5
Invalid:0
-
Total:554

Failures:
 spcontext01.exe


Yes, this is expected.


Timeouts:
 fileio.exe
 top.exe
 termios.exe
 capture.exe
 monitor.exe


These tests should terminate after 20 seconds or so without input. A 
timeout should therefore not occur.



Average test time: 0:00:01.729638
Testing time : 0:15:58.219870


--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

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