Re: Re: smp support

[bin.w...@qkmtech.com]

before i use the rtems , i just write the bare-metal code. 

now i want to use the rtems. but i do not know how to add the original 
bare-metal interrupt routine into the rtems program.

is it has conflict betweent the bare-metal code and the rtems code? 

I has no idea about how to use my old code into the rtems code . in my old code 
,i has some interrupt routine which need nested. and has a background routine 
to process comunication .



bin.w...@qkmtech.com
 
From: Chris Johns
Date: 2017-12-29 14:21
To: bin.w...@qkmtech.com; Users
Subject: Re: smp support
On 29/12/17 12:16 pm, bin.w...@qkmtech.com wrote:
> thanks a lot . 
> 
> i have another question , if i use the smp, can i use the interrupt of  rtems?
> which i want to interrupt period of hard real time of 125us. 
> 
 
Yes you can.
 
> i do not know the difference of the bare-metal interrupt and the rtems 
> interrupt
> . is  the rtems interrupt have  performance loss of the hard real-time?
 
The interrupt overhead will have the same overhead each time and its
deterministic behaviour will depend on the other interrupts in your system and
their priority. The performance will depend on what you need to do in the 
interrupt.
 
> 
> what the schedule method of smp use? is it can affect the interrupt 
> performance?
> 
 
That depends on your application.
 
Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: smp support

[Chris Johns]

On 29/12/17 12:16 pm, bin.w...@qkmtech.com wrote:
> thanks a lot . 
> 
> i have another question , if i use the smp, can i use the interrupt of  rtems?
> which i want to interrupt period of hard real time of 125us. 
> 

Yes you can.

> i do not know the difference of the bare-metal interrupt and the rtems 
> interrupt
> . is  the rtems interrupt have  performance loss of the hard real-time?

The interrupt overhead will have the same overhead each time and its
deterministic behaviour will depend on the other interrupts in your system and
their priority. The performance will depend on what you need to do in the 
interrupt.

> 
> what the schedule method of smp use? is it can affect the interrupt 
> performance?
> 

That depends on your application.

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

Re: Re: the difference between posix user and c user

[bin.w...@qkmtech.com]

is the posix api and the c api used together?

sorry . i am also confused about this two things . because i find that when i 
config the rtems kernel ,there is a option which is  --enable posix.



bin.w...@qkmtech.com
 
From: bin.w...@qkmtech.com
Date: 2017-12-29 09:25
To: Chris Johns; Users
Subject: Re: Re: the difference between posix user and c user
i google the posix .now i know that posix is the abbreviation of "the Portable 
Operating System Interface" it is for software compatibility with variants of 
Unix and other operating systems

but you said, "POSIX and the Classic API are both C APIs."
than i think the posix is packaged on the basis of the standard C, is it right ?
the classic api is the standard c interface , is it right?

best wishes



bin.w...@qkmtech.com
 
From: Chris Johns
Date: 2017-12-29 02:18
To: users
Subject: Re: the difference between posix user and c user
On 29/12/17 12:00 am, bin.w...@qkmtech.com wrote:
> hi everyone:
> 
> i am new to linux and rtems. i do not understand
> what the difference between posix user and c user .
> 
> i am confused about these two concept. which condition i should choose posix ?
> which condition i should choose c ?
> 
 
This is a good question and it is understandable why you do not understand the
difference. The reason is specific to RTEMS and relates to it's history.
 
The original RTEMS was written in Ada and C and the C API is what we now call
the Classic API. It's manual was called the C User Guide hence the name.
 
The Ada version of RTEMS was removed from the source tree and POSIX came a while
later.
 
POSIX and the Classic API are both C APIs. The C User manual is now called the
RTEMS Classic API Guide. See:
 
https://docs.rtems.org/
 
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

The system initialization API

[bin.w...@qkmtech.com]

hi 

when i read the rtems c user pdf ,in  the 6.3.1 Initializing RTEMS  i find that 

"The system initialization API is available via‘‘#included‘‘."

but i do not find the sysint.h file in the source code folders . is it 
something wrong ?



bin.w...@qkmtech.com
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Re: smp support

[bin.w...@qkmtech.com]

hi joel

if i do not use smp mode ,i just use the mutiprocessor configure in the 
confdef.h, is it the amp mode?  

can i  use the mpci to comunication between the two core? 

best wishes
ben



bin.w...@qkmtech.com
 
From: Joel Sherrill
Date: 2017-12-28 21:32
To: bin.wang
CC: rtems-us...@rtems.org
Subject: Re: smp support
Smp support first was usable in the 4.11 release series. It matured between 
then and the git master which will be RTEMS 5. For new projects, we recommend 
just using the git master and moving to the 5.x releases when made. The smp has 
significant improvements and optimizations.

--joel

On Dec 28, 2017 2:53 AM, "bin.w...@qkmtech.com"  wrote:
hi: everybody:

i want to use the smp in the rtems.

when i see the c user doc .i find as follows

Warning: The SMP support in the release of RTEMS is a work in progress. Before 
you start
using this RTEMS version for SMP ask on the RTEMS mailing list.

is the smp in the developing phase?   can it be used in xilinx zynq702? 



bin.w...@qkmtech.com

___
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: Re: the difference between posix user and c user

[bin.w...@qkmtech.com]

i google the posix .now i know that posix is the abbreviation of "the Portable 
Operating System Interface" it is for software compatibility with variants of 
Unix and other operating systems

but you said, "POSIX and the Classic API are both C APIs."
than i think the posix is packaged on the basis of the standard C, is it right ?
the classic api is the standard c interface , is it right?

best wishes



bin.w...@qkmtech.com
 
From: Chris Johns
Date: 2017-12-29 02:18
To: users
Subject: Re: the difference between posix user and c user
On 29/12/17 12:00 am, bin.w...@qkmtech.com wrote:
> hi everyone:
> 
> i am new to linux and rtems. i do not understand
> what the difference between posix user and c user .
> 
> i am confused about these two concept. which condition i should choose posix ?
> which condition i should choose c ?
> 
 
This is a good question and it is understandable why you do not understand the
difference. The reason is specific to RTEMS and relates to it's history.
 
The original RTEMS was written in Ada and C and the C API is what we now call
the Classic API. It's manual was called the C User Guide hence the name.
 
The Ada version of RTEMS was removed from the source tree and POSIX came a while
later.
 
POSIX and the Classic API are both C APIs. The C User manual is now called the
RTEMS Classic API Guide. See:
 
https://docs.rtems.org/
 
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: the difference between posix user and c user

[Chris Johns]

On 29/12/17 12:00 am, bin.w...@qkmtech.com wrote:
> hi everyone:
> 
> i am new to linux and rtems. i do not understand
> what the difference between posix user and c user .
> 
> i am confused about these two concept. which condition i should choose posix ?
> which condition i should choose c ?
> 

This is a good question and it is understandable why you do not understand the
difference. The reason is specific to RTEMS and relates to it's history.

The original RTEMS was written in Ada and C and the C API is what we now call
the Classic API. It's manual was called the C User Guide hence the name.

The Ada version of RTEMS was removed from the source tree and POSIX came a while
later.

POSIX and the Classic API are both C APIs. The C User manual is now called the
RTEMS Classic API Guide. See:

 https://docs.rtems.org/

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

Re: smp support

[Joel Sherrill]

Smp support first was usable in the 4.11 release series. It matured between
then and the git master which will be RTEMS 5. For new projects, we
recommend just using the git master and moving to the 5.x releases when
made. The smp has significant improvements and optimizations.

--joel

On Dec 28, 2017 2:53 AM, "bin.w...@qkmtech.com" 
wrote:

> *hi: everybody:*
>
> *i want to use the smp in the rtems.*
>
> *when i see the c user doc .i find as follows*
>
> *Warning: *The SMP support in the release of RTEMS is a work in progress.
> Before you start
> using this RTEMS version for SMP ask on the RTEMS mailing list.
>
> is the smp in the developing phase?   can it be used in xilinx zynq702?
>
> --
> bin.w...@qkmtech.com
>
> ___
> 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: setjmp/longjmp in RTEMS C API

[Joel Sherrill]

Setjmp and longjmp are part of the C Library and should be available on all
architectures supported by RTEMS

--joel

On Dec 28, 2017 5:09 AM, "Vicent Brocal"  wrote:

> Hi all,
>
> Does anyone know if the RTEMS C API provide some functionality similar to
> the setjmp/longjmp functions of the POSIX API? I did a quick search trough
> the official RTEMS C API doc, but at first glance I did not find anything
> like that.
>
> We are trying to implementing something as the C++ try/catch feature.
>
> Thanks,
>
> Vicent
>
>
>
>
>
> ___
> 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

the difference between posix user and c user

[bin.w...@qkmtech.com]

hi everyone:

i am new to linux and rtems. i do not understand what the difference between 
posix user and c user .

i am confused about these two concept. which condition i should choose posix ? 
which condition i should choose c ?

best



bin.w...@qkmtech.com
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

setjmp/longjmp in RTEMS C API

[Vicent Brocal]

Hi all,

Does anyone know if the RTEMS C API provide some functionality similar
to the setjmp/longjmp functions of the POSIX API? I did a quick search
trough the official RTEMS C API doc, but at first glance I did not find
anything like that.

We are trying to implementing something as the C++ try/catch feature.

Thanks,

Vicent





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

smp support

[bin.w...@qkmtech.com]

hi: everybody:

i want to use the smp in the rtems.

when i see the c user doc .i find as follows

Warning: The SMP support in the release of RTEMS is a work in progress. Before 
you start
using this RTEMS version for SMP ask on the RTEMS mailing list.

is the smp in the developing phase?   can it be used in xilinx zynq702? 



bin.w...@qkmtech.com
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Questions about Configuration for shell prompt & file system

[jaeho jo]

Hi, I have 2 Questions about RTEMS!
1. What is the relationship between shell prompt and unlimited_object?
When I using RTEMS 4.11.2, I need 'CONFIGURE_UNLIMITED_OBJECTS' to use
shell prompt.
I already read 'RTEMS C User Manual - 24.7. Unlimited Objects ' page,
but I don't understand exactly why I need that configuration.
What is the relationship between shell prompt and unlimited_object?
Also, Can you briefly describe the structural differences associated
with this? between RTEMS 4.10.2 and RTEMS 4.11.2.

2. I wonder if it is designed to ignore file system options when mounting a
file system in RTEMS 4.10.2
I mounted the file system using OSAL source code.


https://github.com/nasa/osal/blob/master/src/os/rtems/osfilesys.c#L529
The 4th parameter of this function determines whether a write
operation is possible to the file system

Option for file system
typedef enum {
RTEMS_FILESYSTEM_READ_ONLY,
RTEMS_FILESYSTEM_READ_WRITE,
RTEMS_FILESYSTEM_BAD_OPTIONS
} rtems_filesystem_options_t;  // libio.h

With RTEMS 4.10.2, Even if RTEMS_FILESYSTEM_READ_ONLY(0) is used as an
option of the file system, the file writing to the file system is working
With RTEMS 4.11.2, if RTEMS_FILESYSTEM_READ_ONLY(0) is used as an
option of the file system, the file writing to the file system is not
working.
  if RTEMS_FILESYSTEM_READ_WRITE(1) is
used as an option of the file system, the file writing to the file system
is working.
As far as I can see, RTEMS 4.11.2 seems to be working properly.
I wonder if it is designed to ignore file system options when mounting
a file system in RTEMS 4.10.2 or is it a bug?


Thank you for reading the long questions.

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