Hello Hesham,
On 13/11/2019 16:32, Hesham Almatary wrote:
On Wed, 13 Nov 2019 at 14:48, Sebastian Huber
wrote:
Hello Hesham,
On 23/10/2019 15:50, Hesham Almatary wrote:
Hi,
I submitted a RFC patch series to be able to build RTEMS/RISC-V with
LLVM/Clang. I'd appreciate your feedback on that
On 14/11/2019 01:09, Chris Johns wrote:
On 13/11/19 5:22 pm, Sebastian Huber wrote:
On 13/11/2019 01:39, Chris Johns wrote:
> Ok, it seems a test program has exactly one state for a given BSP.
Yes, this is driven by the ABI, hardware profile and similar constraints.
This is gener
Sorry about the indenting. I don't know that we have an RTEMS style
recommendation on that.
It's a personal thing. I suspect there is RTEMS code with it. It makes
lock/unlock regions obvious
but it isn't conducive to unlocking inside if paths.
I will remove the indentation unless we think there is
On 14/11/19 12:46 am, Joel Sherrill wrote:
> Two use cases were envisioned for this.
>
> 1) a BSP or application which desires to update a real-time clock
>when the RTEMS TOD is set.
>
> 2) a paravirtualized BSP can use this to propagate setting the time
>in an RTEMS application to the ho
On 13/11/19 5:22 pm, Sebastian Huber wrote:
> On 13/11/2019 01:39, Chris Johns wrote:
>>> > Ok, it seems a test program has exactly one state for a given BSP.
>>>
>>> Yes, this is driven by the ABI, hardware profile and similar
>>> constraints.
>>>
>>>
>>> This is generally the case but
Hello Shubham Bhagat,
welcome to RTEMS and congratulations for completing the Hello World task.
You are quite early for GSoC 2020. So just to be sure let me ask: Do you
plan to participate as a GSoC student or do you want to start just out
of interest outside of a program like GSoC?
If you want
On Wed, 13 Nov 2019 at 14:48, Sebastian Huber
wrote:
>
> Hello Hesham,
>
> On 23/10/2019 15:50, Hesham Almatary wrote:
> > Hi,
> >
> > I submitted a RFC patch series to be able to build RTEMS/RISC-V with
> > LLVM/Clang. I'd appreciate your feedback on that.
> >
> > A sample configure line to build
Hello Hesham,
On 23/10/2019 15:50, Hesham Almatary wrote:
Hi,
I submitted a RFC patch series to be able to build RTEMS/RISC-V with
LLVM/Clang. I'd appreciate your feedback on that.
A sample configure line to build RTEMS with LLVM/Clang is:
../rtems/configure --target=riscv-rtems6
--enable-rte
Hello Joel,
there are a couple of
On 13/11/2019 14:46, Joel Sherrill wrote:
_TOD_Acquire( &lock_context );
which I don't understand. Please run the tests with SMP and debug
enabled. You should see some failed assertions in your code.
--
Sebastian Huber, embedded brains GmbH
Address : Dorn
Two use cases were envisioned for this.
1) a BSP or application which desires to update a real-time clock
when the RTEMS TOD is set.
2) a paravirtualized BSP can use this to propagate setting the time
in an RTEMS application to the hosting environment. This enables
the entire set of appl
Thank you for the help! sparc-rtems5-sis works well for me.
On Wednesday, 13 November, 2019, 2:46:02 pm IST, Jiri Gaisler
wrote:
On 11/13/19 9:48 AM, Vaibhav Gupta wrote:
You can also use "sis"
1- Open Terminal 1 and write:
$ sparc-rtems5-sis -gdb # It will prin
On 11/13/19 9:48 AM, Vaibhav Gupta wrote:
> You can also use "sis"
>
> 1- Open Terminal 1 and write:
>
> $ sparc-rtems5-sis -gdb
> # It will print 'gdb: listening on port 1234'.
> # Note you can define port number with '-port' option.
>
> 2-Open Terminal 2 and write:
>
> $ sparc-rt
You can also use "sis"
1- Open Terminal 1 and write:
$ sparc-rtems5-sis -gdb
# It will print 'gdb: listening on port 1234'.
# Note you can define port number with '-port' option.
2-Open Terminal 2 and write:
$ sparc-rtems5-gdb hello.exe
# gdb asks for several inputs
13 matches
Mail list logo
