On 7/8/19 8:46 am, Joel Sherrill wrote:
> This situation seems to have changed with the release of RHEL 7.7. It now
> includes Python 3.7 without having an addition repository per the
> announcement.
>
> https://www.zdnet.com/article/final-red-hat-enterprise-linux-7-version-released/
>
>
> No
Hi
This situation seems to have changed with the release of RHEL 7.7. It now
includes Python 3.7 without having an addition repository per the
announcement.
https://www.zdnet.com/article/final-red-hat-enterprise-linux-7-version-released/
No idea when this will show up as a CentOS 7 upgrade. But
From: Chris Johns
- Update the linkcmd file to support configure settings
- Set the workspace size based on the revision value
---
bsps/arm/raspberrypi/start/bspgetworkarea.c | 34 +--
bsps/arm/raspberrypi/start/bspstart.c | 93 +++
bsps/arm/raspberrypi/start/linkc
FWIW the pages converted by the high school students during Google Code-in
to be in the SW Eng Guide were from Wiki pages which ultimately need to be
deleted. There needs to be a pass to compare Rest version against the Wiki
version and then delete the Wiki version. And anytime a Wiki document is
d
On Tue, Aug 6, 2019 at 4:01 AM Sebastian Huber
wrote:
>
> The new content is based on the wiki page:
>
> https://devel.rtems.org/wiki/Developer/Bug_Reporting
>
> The goal is to remove the wiki page and direct the "New ticket" page to
> this user manual section. Some content of the wiki page shoul
- Am 6. Aug 2019 um 17:30 schrieb Ravindra Kumar Meena rmeena...@gmail.com:
>>
>> > I think this can be the right way to check bound access.
>> >
>> https://github.com/rmeena840/rtems-tools/commit/81bf2a9b9e57e7911d519c4719c5126e29a7adbe
>>
>> No, the API classes are 1, 2, and 3. The indices i
Adding the log with --trace.
I hope this helps someone.
--joel
On Tue, Aug 6, 2019 at 10:55 AM Joel Sherrill wrote:
> Hi
>
> I wanted to pitch in on the spike testing but can't build it:
>
> + ../source-builder/sb-set-builder --trace --log=l-spike.txt
> --prefix=/home/joel/rtems-work/tools/5 d
Hi
I wanted to pitch in on the spike testing but can't build it:
+ ../source-builder/sb-set-builder --trace --log=l-spike.txt
--prefix=/home/joel/rtems-work/tools/5 devel/spike
RTEMS Source Builder - Set Builder, 5 (29fab0500e22)
Build Set: devel/spike
config: devel/spike-1.1.0.cfg
package: spike
Awesome, thanks!
On Tue, Aug 6, 2019 at 8:50 PM Hesham Almatary
wrote:
> Hi Vaibhav,
>
> * I recommend you use rv64* because of a potential 32-bit HTIF issue on
> Spike.
> * Make sure you install Spike correctly [1] and it's in your path or
> also qemu-system-riscv* instead.
> * If you're buildi
>
> > I think this can be the right way to check bound access.
> >
> https://github.com/rmeena840/rtems-tools/commit/81bf2a9b9e57e7911d519c4719c5126e29a7adbe
>
> No, the API classes are 1, 2, and 3. The indices into the table must be
> 0, 1, and 2. Don't add asserts in this path. Ignore items which
Hi Vaibhav,
* I recommend you use rv64* because of a potential 32-bit HTIF issue on Spike.
* Make sure you install Spike correctly [1] and it's in your path or
also qemu-system-riscv* instead.
* If you're building RTEMS for Spike (i.e., rv*_spike), make sure to
add RISCV_ENABLE_HTIF_SUPPORT to you
---
newlib/libc/machine/msp430/Makefile.in | 1 -
newlib/libc/machine/riscv/Makefile.in | 21 +++---
newlib/libc/search/Makefile.in | 50 -
newlib/libm/machine/aarch64/Makefile.in | 7 +++--
4 files changed, 33 insertions(+), 46 deletions(-)
d
The default implementation of the fenv.h methods return
-EOPNOTSUPP.
The intention of the new fenv.h is that it be portable
and that architectures provide their own implementation
of sys/fenv.h.
---
newlib/libc/include/fenv.h | 42 ++
n
---
newlib/libm/Makefile.in | 12 +-
newlib/libm/configure| 3 +-
newlib/libm/fenv/Makefile.in | 628 +++
3 files changed, 636 insertions(+), 7 deletions(-)
create mode 100644 newlib/libm/fenv/Makefile.in
diff --git a/newlib/libm/Makefile.i
0001 - Miscellaneous changes from regenerating that I can't explain.
These are under libc.
0002 - Add fenv.h, template sys/fenv.h, and default non-functional
implementations of fenv.h methods with documentation.
0003 - Regeenerated under libm from my changes.
Joel Sherrill (3):
M
I am getting following error:
.
.
$ rtems-test --rtems-bsp=rv32imac_spike
--rtems-tools=$HOME/development/rtems/5
~/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples
RTEMS Testing - Tester, 5.0.not_released
Command Line: /home/varodek/development/rtems/5/bin/rtems-test
>
> No, when you emit a sched_switch event in print_item() you replace the
>
> snprintf( item_data_str, sizeof( item_data_str ), "%08"PRIx64,
>
> with a memcpy() from the corresponding thread_names entry.
>
Done.
https://github.com/rmeena840/rtems-tools/commit/6517c7b32f4dc063fd12dce02d5004741588ea
On 06/08/2019 15:14, Ravindra Kumar Meena wrote:
There is another bug here:
size_t api_id = ( ( cctx->thread_id_name[ item->cpu ].thread_id >> 24 )
& 0x7 );
Please make sure that you don't have an out of bounds access. Check the
dimensions of your array against the values yo
>
> There is another bug here:
>
> size_t api_id = ( ( cctx->thread_id_name[ item->cpu ].thread_id >> 24 )
> & 0x7 );
>
> Please make sure that you don't have an out of bounds access. Check the
> dimensions of your array against the values you get from the line above.
>
I think this can be the righ
On 06/08/2019 13:26, Ravindra Kumar Meena wrote:
> Yes, I tried that also. I can't see the 8 char for multiple
> RTEMS_RECORD_THREAD_NAME in print_item(). Still, I tried to
follow the
> previously mentioned algorithm.
>
>
https://github.com/rmeena840/rtems-tools/
On 06/08/2019 13:41, Ravindra Kumar Meena wrote:
> Done
>
https://github.com/rmeena840/rtems-tools/commit/8ceb3ccb97422044fb30b3c562fc736cf0686d48
Ok, good. Now please use this table to populate the thread names in the
sched_switch event.
Do we have to populate it at th
>
> > Done
> >
> https://github.com/rmeena840/rtems-tools/commit/8ceb3ccb97422044fb30b3c562fc736cf0686d48
>
> Ok, good. Now please use this table to populate the thread names in the
> sched_switch event.
>
Do we have to populate it at the end of the file when print_item() has done
its job?
And thi
On 06/08/2019 13:26, Ravindra Kumar Meena wrote:
> Yes, I tried that also. I can't see the 8 char for multiple
> RTEMS_RECORD_THREAD_NAME in print_item(). Still, I tried to
follow the
> previously mentioned algorithm.
>
>
https://github.com/rmeena840/rtems-tools/
On Tue, Aug 6, 2019 at 2:36 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> On 06/08/2019 10:54, Vaibhav Gupta wrote:
> > Getting this error:
> > $ rtems-test --rtems-bsp=rv32imac
> > --rtems-tools=$HOME/development/rtems/5
> >
> ~/development/rtems/kernel/rv32imac/riscv-rtem
>
> > Yes, I tried that also. I can't see the 8 char for multiple
> > RTEMS_RECORD_THREAD_NAME in print_item(). Still, I tried to follow the
> > previously mentioned algorithm.
> >
> >
> https://github.com/rmeena840/rtems-tools/commit/33c217642e36b91926dfd823e5b3b59974790084
>
> The code is more co
On 06/08/2019 12:50, Ravindra Kumar Meena wrote:
Have a look at the documentation of printf
(http://www.cplusplus.com/reference/cstdio/printf/).
The format specifier "%lx" refers to unsigned long int which is most
likely a 32bit integer on your machine.
So it will only read 4
>
> Have a look at the documentation of printf (
> http://www.cplusplus.com/reference/cstdio/printf/).
> The format specifier "%lx" refers to unsigned long int which is most
> likely a 32bit integer on your machine.
> So it will only read 4 bytes regardless of how many are stored in memory.
> Try u
> -Ursprüngliche Nachricht-
> Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Ravindra
> Kumar Meena
> Gesendet: Dienstag, 6. August 2019 10:59
> An: Sebastian Huber
> Cc: rtems-de...@rtems.org
> Betreff: Re: GSoC Project | Basic Support for Trace Compass
>
> e.g.
>
You find a PDF with this change here:
https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf
--
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
The new content is based on the wiki page:
https://devel.rtems.org/wiki/Developer/Bug_Reporting
The goal is to remove the wiki page and direct the "New ticket" page to
this user manual section. Some content of the wiki page should move to
the "Contributing" sections since it is not directly rela
On 06/08/2019 10:54, Vaibhav Gupta wrote:
Getting this error:
$ rtems-test --rtems-bsp=rv32imac
--rtems-tools=$HOME/development/rtems/5
~/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples
RTEMS Testing - Tester, 5.0.not_released
Command Line: /home/varodek/devel
>
> e.g.
> > Object Index: 30
> > Name: 36697773
> > Name: 71206b73
>
> On a 64-bit target, the data field contains 8 chars. Why do you only
> print 4 chars here?
>
This is what I am getting in Konsole output when I did this:
printf("Name: %lx\n",item->data);
May be full information is not receiv
Getting this error:
$ rtems-test --rtems-bsp=rv32imac --rtems-tools=$HOME/development/rtems/5
~/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples
RTEMS Testing - Tester, 5.0.not_released
Command Line: /home/varodek/development/rtems/5/bin/rtems-test
--rtems-bsp=rv32imac
On 06/08/2019 10:33, Vaibhav Gupta wrote:
But when I am trying to run hello world testsuite:
$ riscv-rtems5-run ./hello.exe
You have to use the RTEMS Tester, e.g.
rtems-test --rtems-bsp=rv32imac
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone
On 06/08/2019 10:26, Ravindra Kumar Meena wrote:
Thread name is in the right order now.
Yes, the order is all right, but you still overwrite thread names which
consist of multiple events.
I am not able to figure out how overwritten is happening. In my code
overwritten case is handl
Hello,
.
I build riscv tool chain using command:
$ ../source-builder/sb-set-builder
--prefix=/home/varodek/development/rtems/5 5/rtems-riscv
.
And then build the kernel using command:
$ /home/varodek/development/rtems/kernel/rtems/configure
--prefix=/home/varodek/development/rtems/5 --enable-mainta
On 06/08/2019 10:08, Chris Johns wrote:
Hi,
If I want to detect and set the workspace size what should I have as the RAM
length in the linkcmd file?
The length in the linkcmds should be the minimum of all variants this
linker command supports. A runtime detection can increase the size
availa
>
> Thread name is in the right order now.
>
> Yes, the order is all right, but you still overwrite thread names which
> consist of multiple events.
>
I am not able to figure out how overwritten is happening. In my code
overwritten case is handled by:
if( cctx->thread_names[ api_id ][ thread_id ][
On 06/08/2019 10:05, Chris Johns wrote:
On 6/8/19 4:36 pm, Sebastian Huber wrote:
Hello,
when you use document internal references, e.g.
:ref:`RSB`
then this is turned into:
"Chapter 12 - RTEMS Source Builder"
I think this "Chapter 12 - " prefix makes it harder to read the document. In a
Hi,
If I want to detect and set the workspace size what should I have as the RAM
length in the linkcmd file?
The RPi only has 128M configured and I am playing around with a patch that gives
me the full 1G on a 2B. The amount of RAM is easy to detect on a Pi.
Thanks
Chris
___
On 6/8/19 4:36 pm, Sebastian Huber wrote:
> Hello,
>
> when you use document internal references, e.g.
>
> :ref:`RSB`
>
> then this is turned into:
>
> "Chapter 12 - RTEMS Source Builder"
>
> I think this "Chapter 12 - " prefix makes it harder to read the document. In a
> default configuration
41 matches
Mail list logo
