Re: RTEMS Release Snapshot: 5.0.0-m1911 (01 Nov 2019)

[Chris Johns]

On 1/11/19 3:59 pm, chr...@rtems.org wrote:
> RTEMS Release Build - 5.0.0-m1911
> 
> RTEMS 5 Release snapshot m1911 is avaliable for testing.
> It can be found at:
> 
>  https://ftp.rtems.org/pub/rtems/releases/5/5.0.0-m1911/5.0.0-m1911

Bug in the announce generation, the path is ...

https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m1911

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

RTEMS Release Snapshot: 5.0.0-m1911 (01 Nov 2019)

[chrisj]

RTEMS Release Build - 5.0.0-m1911

RTEMS 5 Release snapshot m1911 is avaliable for testing.
It can be found at:

 https://ftp.rtems.org/pub/rtems/releases/5/5.0.0-m1911/5.0.0-m1911

Please test and report any issues to the u...@rtems.org or de...@rtems.org
mailing lists or please raise a ticket.

If you are part of the RTEMS testing program please build on your preferred
host posting build and BSP test results to bu...@rtems.org.

This is a development release and may have errors and be unstable.

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

shell output

[Mathew Benson]

is there any documentation that explains the actual output of the shell
commands?  For example, the documentation for the task command says how to
run it, and gives the following sample output:

SHLL [/] # task
ID   NAME SHED PRI STATE  MODESEVENTS WAITINFO
--
0a010001 UI1  UPD  254 EV P:T:nA   NONE
0a010002 SHLL UPD  100 READY  P:T:nA   NONE


But doesn't actually explain what the data in the columns mean.  What do
the following "STATE" values mean:  EV, SIG:IS, READY, MSG, SEM, and TIME?
What do the MODES mean?  Same question for the "sema" command output.

-- 
*Mathew Benson*
CEO | Chief Engineer
Windhover Labs, LLC
832-640-4018


www.windhoverlabs.com
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Help for using simulator for Beagleboard

[Utkarsh Rai]

Thank you for your suggestion, I will look into it.

On Thu, Oct 31, 2019 at 3:23 AM Joel Sherrill  wrote:

>
>
> On Wed, Oct 30, 2019 at 4:01 PM Chris Johns  wrote:
>
>> On 31/10/19 6:44 am, Utkarsh Rai wrote:
>> > I am trying to get my hands dirty with RTEMS using Beagleboard. I have
>> been
>> > successful in building the toolchain, RTEMS, the beagle BSPs, and the
>> test
>> > suites.
>>
>> Excellent and well done.
>>
>> > As of now, I do not have any physical hardware to run and test the BSPs,
>> > it would be very kind of you if I can get a few indicators for setting
>> up the
>> > simulator for Beagleboard and testing the BSPs on it.
>>
>> Qemu supports some of beagle boards. I suggest you investigate qemu and
>> running
>> on it.
>>
>
> qemu-system-arm -M ? will list the "models" supported. I don't see the
> Beagle in the
> qemu I have from the qemu.bset. qemu4.bset might have it. I don't know if
> it is in
> the mainline qemu.
>
> People used to use the Linaro distribution qemu to get this.
>
> --joel
>
>
>>
>> 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: installing Doorstop on macOS (for RTEMS use)

[Andrew Butterfield]

Hi Sebastian,

I just did option 3 (python.org ) again on another iMac - 
very straightforward- my recommendation.

Regards, Andrew

> On 30 Oct 2019, at 13:24, Sebastian Huber 
>  wrote:
> 
> On 25/10/2019 01:18, Chris Johns wrote:
>> On 24/10/19 9:52 pm, Andrew Butterfield wrote:
>>>   I got around to doing a doorstop install that does not rely on homebrew,
>>> using the python.org  distribution for 3.8
>>> 
>>> Everything worked fine - python3 is installed in /Library just like the OS X
>>> native python 2.7
>>> Doorstop runs just fine too.
>> Excellent and thanks for this. I think this or the other solution that was
>> posted should work. This means I cannot see any blockers for Doorstop on our
>> supported hosts.
> 
> Ok, great. Thanks for all the testing and other valuable input.
> 
> I think on macOS we have now five options:
> 
> 1. homebrew
> 
> 2. MacPorts
> 
> 3. python.org installer
> 
> 4. pyenv
> 
> 5. wait for Apple to ship a Python 3
> 
> We need a recommendation for the user manual.
> 
> -- 
> 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.
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users


Andrew Butterfield Tel: +353-1-896-2517 Fax: +353-1-677-2204
Lero@TCD, Head of Foundations & Methods Research Group
School of Computer Science and Statistics,
Room G.39, O'Reilly Institute, Trinity College, University of Dublin
 http://www.scss.tcd.ie/Andrew.Butterfield/


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

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 31/10/19 5:21 pm, Sebastian Huber wrote:
> On 30/10/2019 21:39, Chris Johns wrote:
>> On 31/10/19 12:24 am, Sebastian Huber wrote:
>>> On 25/10/2019 01:18, Chris Johns wrote:
 On 24/10/19 9:52 pm, Andrew Butterfield wrote:
>     I got around to doing a doorstop install that does not rely on 
> homebrew,
> using the python.org  distribution for 3.8
>
> Everything worked fine - python3 is installed in /Library just like the 
> OS X
> native python 2.7
> Doorstop runs just fine too.

 Excellent and thanks for this. I think this or the other solution that was
 posted should work. This means I cannot see any blockers for Doorstop on 
 our
 supported hosts.
>>>
>>> Ok, great. Thanks for all the testing and other valuable input.
>>>
>>> I think on macOS we have now five options:
>>>
>>> 1. homebrew
>>>
>>> 2. MacPorts
>>>
>>> 3. python.org installer
>>>
>>> 4. pyenv
>>>
>>> 5. wait for Apple to ship a Python 3
>>>
>>> We need a recommendation for the user manual.
>>>
>>
>> I suggest 3. because it is the simplest to do and it does not step on global
>> paths.
> 
> Ok.
> 
>>
>> Can we assume Doorstop is only needed if developing or maintaining RTEMS?
> 
> Yes, definitely.
> 
> You mean the user manual is not the right place to add Python 3.6+ to the host
> computer requirements? We could add this to the RTEMS Software Engineering 
> manual.
> 

Good question. If there is nothing in the User Manual related to developing or
maintaining RTEMS then yes the eng manual would be the correct place. I am sure
we will find other things that are specific to each host. For example I will
need to add a section to the eng manual on the release procedure and this has a
range of specific packages that are needed.

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