RTEMS / RTOS / RTEMS¶
Go to Issues or Merge Requests
Issues Summary
Merge Requests Summary
Issues¶
4725 - Git commit message format instrunctions (cloned)¶
Id |
4725 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Joel Sherrill |
Created |
2022-09-26T01:50:47.000Z |
Updated |
2025-09-19T01:28:32.304Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::task, version::5 |
Link |
|
Merges |
0 |
The Eng docs Creating A Patch references the Wiki. The content should be in the manual.
Note lots of git related bits are in the Eng manual and still on the Wiki so which is correct?
Author: Chris Johns
2022-11-15T10:29:58.000Z
Why is this on the 5 branch?
Author: Joel Sherrill
2022-12-14T23:25:58.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”d144cf0962e7e6881cbdd3ac93afa4fe0a489f5d/rtems-docs” d144cf0/rtems-docs]:
eng/vc-users.rst: Add commit message guidance Closes #4275.
Author: Chris Johns
2025-09-19T01:11:12.893Z
changed the description
4704 - Fix invalid RSB source URLs¶
Id |
4704 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-08-17T06:12:26.000Z |
Updated |
2025-09-19T01:28:32.188Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Some packages now have invalid source URLs
Author: Chris Johns
2022-12-06T22:45:21.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
The release fetching of sources is now clean.
Author: Chris Johns
2025-09-19T01:11:11.875Z
changed the description
4687 - Documentation List for Releases Completely Missing 5.x¶
Id |
4687 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Chris Johns |
Created |
2022-07-27T18:27:48.000Z |
Updated |
2025-09-19T01:28:32.073Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
See https://docs.rtems.org/releases.html and fix it. :)
Author: Chris Johns
2022-11-09T23:29:04.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
The website now handles the 5.1 release correctly.
Author: Chris Johns
2025-09-19T01:11:11.559Z
changed the description
4711 - RSB does not expand dir type macros correctly (cloned)¶
Id |
4711 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-08-28T22:34:28.000Z |
Updated |
2025-09-19T01:28:31.922Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Cloned from #4710:
The expansion of the dir type macros is not done correctly. Macro replacement only appends the file part to the last element of a path list. For example:
%{mydir}/abc.cfg
with a path of:
%define mydir x:y:z
results in:
x:y:z/abc.cfg
The config load code handles this but it is wrong. The expansion of dir type macro variables should handle path separators (:) so you get:
x/abc.cfg:y/abc.cfg:z.abc.cfg
This has not been a problem in the RSB because the _configdir has only had two elements and the last one only ever had subdirectories.
Author: Chris Johns
2022-11-09T23:32:16.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
Fixed with backports from
mainfor deployment.
Author: Chris Johns
2025-09-19T01:11:12.204Z
changed the description
4709 - Installed header break C++¶
Id |
4709 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-08-26T01:38:01.000Z |
Updated |
2025-09-19T01:28:31.796Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Some headers generate C++ errors and so cannot be included.
Author: Trac Migrate
2022-08-29T03:23:10.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”c5b794227b72c99538f725919eaa0c90636df3d1/rtems” c5b7942/rtems]:
cpukit/include: Fix including in C++ Closes #4709
Author: Chris Johns
2025-09-19T01:11:12.025Z
changed the description
4734 - RSB decode exception stops build¶
Id |
4734 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-09-29T23:11:12.000Z |
Updated |
2025-09-19T01:28:31.646Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Cloned from #4726:
Building in a Rocky VM on FB 12 with 5 I got:
Traceback (most recent call last):
File "/usr/lib64/python3.9/threading.py", line 973, in _bootstrap_inner
self.run()
File "/usr/lib64/python3.9/threading.py", line 910, in run
self._target(*self._args, **self._kwargs)
File "/opt/work/chris/rtems/rsb/rtems-source-builder.git/source-builder/sb/execute.py", line 204, in _readthread
data = data.decode(sys.stdout.encoding)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 4095: unexpected end of data
If the data is corrupted or broken things stop. Fix to attempt to keep going.
This issue also effect rtems-tools.
Author: Trac Migrate
2022-09-29T23:13:14.000Z
In [changeset:”ddfcc320ab740cd6ac30d70aaff7987dda25ee7f/rtems-source-builder” ddfcc32/rtems-source-builder]:
sb/execute: Use a decoder that maintains state aross blocks Update #4734
Author: Trac Migrate
2022-09-30T20:19:01.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”af0f612c4656d556efcaa03119475ca6fbdc7928/rtems-source-builder” af0f612/rtems-source-builder]:
sb/execute: Fix incremental decoder with --dry-run Closes #4734
Author: Chris Johns
2025-09-19T01:11:13.752Z
changed the description
4733 - Set top in RSB version.py¶
Id |
4733 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-09-29T08:15:41.000Z |
Updated |
2025-09-19T01:28:31.529Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Cloned from #4732:
Setting the top lets the code be used in deployment to get the version of the RSB being used. An RSB version lets a user track the exact tools being built and version numbers reported by the tools can match the packaged build, eg an rpm name and version info.
Author: Trac Migrate
2022-09-29T23:13:12.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”08ca387229e6ec697f34050d8eaad26a38464aa5/rtems-source-builder” 08ca387/rtems-source-builder]:
sb/version: Set top from external package Closes #4733
Author: Chris Johns
2025-09-19T01:11:13.480Z
changed the description
4731 - rtems-source-builder doesn’t generate tar archives for all packages any more¶
Id |
4731 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Chris Johns |
Created |
2022-09-29T08:12:46.000Z |
Updated |
2025-09-19T01:28:31.399Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Original author: Christian Mauderer
Cloned from #4730:
Like discussed in the following mailing list thread, the rtems-source-builder doesn’t generate tar archives for all packages anymore:
https://lists.rtems.org/pipermail/devel/2022-September/073369.html
All RTEMS tools build sets 6/rtems-* work fine except for 6/rtems-microblaze. devel/qemu and devel/dtc do not generate a tar archive. If the patch
https://git.rtems.org/rtems-source-builder/commit/?id=6205068c5a429e9ee1b471f4c8a3a119bb6757b2
is reverted, the tar files are generated just like before.
Author: Trac Migrate
2022-09-29T23:13:11.000Z
Original author: Christian Mauderer
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”6f1e9149b5b22248ee80a5368699817200b5b3a4/rtems-source-builder” 6f1e914/rtems-source-builder]:
sb/set-builder: Fix staging and tar file generation with a single config build Closes #4731
Author: Chris Johns
2022-09-30T02:24:57.000Z
Original author: Christian Mauderer
Resolution ~”fixed” deleted
Status changed from closed to reopened
This has broken staging for multiple packages in a top level buildset.
Author: Trac Migrate
2022-09-30T20:19:03.000Z
Original author: Christian Mauderer
Resolution set to ~”fixed”
Status changed from reopened to closed
In [changeset:”d592ee88380786a93af9b4baea691c3e61f4cbf2/rtems-source-builder” d592ee8/rtems-source-builder]:
sb/set-bulder: Fix installing builds when a single buildset - Always stage a build - Install if installable and outter most buildset instance Closes #4731
Author: Chris Johns
2025-09-19T01:11:13.239Z
changed the description
4727 - RSB decode exception stops build¶
Id |
4727 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-09-26T05:39:18.000Z |
Updated |
2025-09-19T01:28:31.280Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Building in a Rocky VM on FB 12 with 5 I got:
Traceback (most recent call last):
File "/usr/lib64/python3.9/threading.py", line 973, in _bootstrap_inner
self.run()
File "/usr/lib64/python3.9/threading.py", line 910, in run
self._target(*self._args, **self._kwargs)
File "/opt/work/chris/rtems/rsb/rtems-source-builder.git/source-builder/sb/execute.py", line 204, in _readthread
data = data.decode(sys.stdout.encoding)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 4095: unexpected end of data
If the data is corrupted or broken things stop. Fix to attempt to keep going.
Author: Chris Johns
2022-09-26T05:39:53.000Z
Summary changed from RSB decode exception stops build (cloned) to RSB decode exception stops build
Author: Chris Johns
2022-11-09T23:48:42.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
Fixed https://git.rtems.org/rtems-source-builder/commit/?h=5&id=ddfcc320ab740cd6ac30d70aaff7987dda25ee7f
Author: Chris Johns
2025-09-19T01:11:13.059Z
changed the description
4715 - RSB get sources misses a number of files¶
Id |
4715 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-09-08T03:40:07.000Z |
Updated |
2025-09-19T01:28:31.155Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Back port the changes from the development branch. The get sources tool is used during the release to collect the sources so they are hosted on https://ftp.rtems.org
The changes exposes a number of configuration file issues on the 5 branch.
Author: Trac Migrate
2022-09-19T21:24:53.000Z
In [changeset:”3138ff5295f27883f1f01feefc76fee36b34ea6c/rtems-source-builder” 3138ff5/rtems-source-builder]:
sb/getsources: Fix getting sources - Back ported from the development branch Updates #4715
Author: Trac Migrate
2022-09-19T21:24:56.000Z
In [changeset:”db3d470c3126e9cddbd301d70876f78a16789f69/rtems-source-builder” db3d470/rtems-source-builder]:
sb/getsources: Fixes to configurations Updates #4715
Author: Chris Johns
2022-11-09T23:32:33.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
Author: Chris Johns
2022-11-11T02:57:37.000Z
Resolution ~”fixed” deleted
Status changed from closed to reopened
More missed files.
Author: Trac Migrate
2022-11-14T20:58:24.000Z
In [changeset:”5992bc9519a183b04b737136601332358ec3e3da/rtems-source-builder” 5992bc9/rtems-source-builder]:
bare/gcc: Remove gcc-4.8.2 because newlib references the unsupported CVS Updates #4715
Author: Trac Migrate
2022-11-14T22:36:16.000Z
In [changeset:”b57948f66684b2b161f84065f9b6d87dfba8cdbc/rtems-source-builder” b57948f/rtems-source-builder]:
rtems: Update source and patch URLs to valid locations Updates #4715
Author: Trac Migrate
2022-11-15T21:42:36.000Z
In [changeset:”3ec64413c9d7a74a58b48b0e64f89cc43516d719/rtems-source-builder” 3ec6441/rtems-source-builder]:
rtems: Update source and patch URLs to valid locations Updates #4715
Author: Trac Migrate
2022-11-15T23:10:26.000Z
In [changeset:”1116c5f85fb5dceca4a57c1b69195b6e9215b084/rtems-source-builder” 1116c5f/rtems-source-builder]:
rtems: Add back gcc-4.6 build configuration Updates #4715
Author: Chris Johns
2022-12-06T22:46:37.000Z
Resolution set to ~”fixed”
Status changed from reopened to closed
The release now fetches all sources.
Author: Chris Johns
2025-09-19T01:11:12.438Z
changed the description
4683 - Leaked BSP section flags in Makefile.inc breaks EPICS¶
Id |
4683 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Trac Migrate |
Created |
2022-07-21T05:47:07.000Z |
Updated |
2025-09-19T01:28:31.041Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::invalid, rtems::build, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
RTEMS 5 added -ffunction-sections -fdata-sections to the target flags for BSPs in an architecture that supports code and data sections.
Some EPICS code such as the NTP have code the linker does not link into the final executable. The data sections means the done variable is not linked into the executable when a function in the module is referenced.
RTEMS 6 only exports the ABI flags and any internal build flags are not exported.
EPICS should also review this type of code because it excludes potential optimizations.
Author: Chris Johns
2022-07-21T05:52:08.000Z
Description changed
RTEMS 5 added `-ffunction-sections -fdata-sections` to the target flags for BSPs in an architecture that supports code and data sections. - Some EPICS code such as the [NTP have code](https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/src/osi/os/RTEMS-score/osdTime.cpp#L148). The data sections means the `done` variable is not linked into the executable when a function in the module is referenced. ? ^^ + Some EPICS code such as the [NTP](https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/src/osi/os/RTEMS-score/osdTime.cpp#L148) have code the linker does not link into the final executable. The data sections means the `done` variable is not linked into the executable when a function in the module is referenced. ? + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ RTEMS 6 only exports the ABI flags and any internal build flags are not exported. EPICS should also review this type of code because it excludes potential optimizations.
Author: Joel Sherrill
2022-07-21T14:26:42.000Z
This is not a good code pattern to use if per item sectioning is used. There is no reference to the variable done at all and no reason for it to be included. Why not just call an explicit initialization method?
Author: Chris Johns
2022-11-09T22:39:30.000Z
Resolution set to ~”invalid”
Status changed from new to closed
This topic has been discussed in an EPICS github issue #288 and Michael thinks the flags are fine. Further testing has shown no real issue. I will set this ticket to
invalidand close it. It can be reopened if it is a problem.
Author: Chris Johns
2025-09-19T01:11:11.382Z
changed the description
4716 - Backport RSB fixes from Development¶
Id |
4716 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-09-08T05:31:58.000Z |
Updated |
2025-09-19T01:28:30.922Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Backport RSB fixes from the development branch.
Author: Trac Migrate
2022-09-19T21:24:54.000Z
In [changeset:”6116d9c872895a659026b6dbd1cdb2faaffc6dd7/rtems-source-builder” 6116d9c/rtems-source-builder]:
sb: Back port fixes from the development branch Updates #4716
Author: Trac Migrate
2022-09-19T21:24:58.000Z
In [changeset:”e85e2a730009fd1833fd7702a5332cab015cdfcc/rtems-source-builder” e85e2a7/rtems-source-builder]:
sb/setbuilder: Support line continuation Updates #4716
Author: Trac Migrate
2022-09-19T21:24:59.000Z
In [changeset:”0253d81ad2a19101c540c49c54b314e0290a6189/rtems-source-builder” 0253d81/rtems-source-builder]:
sb/config: Correctly handle multiple config paths - Add rtems/config to the config directories searched to better support deployment - Correctly expand the configdir and path searchs Updates #4716
Author: Trac Migrate
2022-09-19T21:25:01.000Z
In [changeset:”828feec622c3ebfdf96a50f5789fcace93717f82/rtems-source-builder” 828feec/rtems-source-builder]:
sb/setbuilder: Correctly create build set tar files - Make a single tarfile for all buildsets built - Use the staging tree as the tarfile source - Use python's tarfile module - Create a config.file object without loading a .cfg file Updates #4716
Author: Trac Migrate
2022-09-19T21:25:02.000Z
In [changeset:”25972d90824bd3f3f416ad9bfbba286f98b5b63d/rtems-source-builder” 25972d9/rtems-source-builder]:
sb/setbuilder: Do not install if --no-install option is used - This is a bug introduced in the recent bset tar file changes Updates #4716
Author: Trac Migrate
2022-09-19T21:25:05.000Z
In [changeset:”6afc04b3328351c34d961e8bd6441aaddbeb3c0a/rtems-source-builder” 6afc04b/rtems-source-builder]:
sb/setbuilder: Install the build when stagging or configured to install Updates #4716
Author: Chris Johns
2022-11-09T23:32:51.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
Author: Chris Johns
2025-09-19T01:11:12.591Z
changed the description
4717 - Add RSB Deployment support¶
Id |
4717 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-09-14T07:09:32.000Z |
Updated |
2025-09-19T01:28:30.811Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::enhancement, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Provide deployment support for RTEMS 5.
The support will be a single architecture with multiple BSPs for that architecture.
This change does not effect any existing functionality.
Author: Trac Migrate
2022-09-19T21:25:04.000Z
In [changeset:”16d4f2c934b49482d4a4f570ecea2d025eeef00d/rtems-source-builder” 16d4f2c/rtems-source-builder]:
rtems/kernel: Support deployment standard buildset configs - Check and optionally support arch/bsp format 'with_rtems_bsp' defines Updates #4717
Author: Trac Migrate
2022-09-30T20:19:04.000Z
In [changeset:”369b60a0b4ed961eba8da634d09691841e67e3de/rtems-source-builder” 369b60a/rtems-source-builder]:
rtems/bsps: Optionally support arch/bsp if used Updates #4717
Author: Chris Johns
2022-11-09T23:33:09.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
Author: Chris Johns
2025-09-19T01:11:12.741Z
changed the description
4752 - RTEMS docs do not build with a recent sphinx¶
Id |
4752 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-11-10T04:00:02.000Z |
Updated |
2025-09-19T01:26:07.294Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
The build does not configure:
$ ./waf distclean configure --prefix=/opt/src/rtems/test --pdf --singlehtml
'distclean' finished successfully (0.000s)
Setting top to : /opt/work/chris/rtems/docs/rtems-docs.git
Setting out to : /opt/work/chris/rtems/docs/rtems-docs.git/build
Checking for program 'git' : /usr/local/bin/git
Checking for program 'sphinx-build' : /opt/work/chris/rtems/releasing/rng/bin/sphinx-build
Checking for program 'aspell' : /usr/local/bin/aspell
Checking if Sphinx is at least 1.3 : yes (5.3)
Checking Sphinx Options : none
Checking Sphinx Nit-Pick mode : no
Checking for 'sphinx.ext.autodoc' : found
Checking for 'sphinx.ext.coverage' : found
Checking for 'sphinx.ext.doctest' : found
Checking for 'sphinx.ext.graphviz' : found
Checking for 'sphinx.ext.intersphinx' : found
Checking for 'sphinx.ext.mathjax' : found
Checking for 'sphinxcontrib.bibtex' : not found (see README.txt)
The configuration failed
(complete log in /opt/work/chris/rtems/docs/rtems-docs.git/build/config.log)
Author: Trac Migrate
2022-11-10T04:28:51.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”07f151f4579458de8b6255cd88509e9a5d86ade1/rtems-docs” 07f151f/rtems-docs]:
waf: Backport from main build fixes Closes #4752
Author: Chris Johns
2025-09-19T01:11:14.001Z
changed the description
4754 - Set RSB GDB source path to https¶
Id |
4754 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-11-10T20:43:01.000Z |
Updated |
2025-09-19T01:25:55.745Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Backport https://git.rtems.org/rtems-source-builder/commit/?id=949cf500b4f4ab560a77c2ac60cd9ac0f47aa852
Author: Trac Migrate
2022-11-14T20:58:22.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”2eda12e1da530b921ecc864288f4054d3cb5a3dc/rtems-source-builder” 2eda12e/rtems-source-builder]:
gdb: Use https for downloads Close #4754
Author: Chris Johns
2025-09-19T01:11:14.178Z
changed the description
4755 - Docs build system does not build singlehtml¶
Id |
4755 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-11-10T22:04:50.000Z |
Updated |
2025-09-19T01:25:41.293Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
The configure logic does not handle the inliner detection correctly.
Author: Trac Migrate
2022-11-10T22:14:54.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”031cb12fe11d06d71a6393cc007aa0e3348e982b/rtems-docs” 031cb12/rtems-docs]:
waf: Handle the enable options for singlehtml and ditaa/puml Close #4755
Author: Chris Johns
2025-09-19T01:11:14.338Z
changed the description
4757 - RSB freetype 2.4.10 source not hosted any longer¶
Id |
4757 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Trac Migrate |
Created |
2022-11-11T02:34:00.000Z |
Updated |
2025-09-19T01:25:23.450Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
The source is not present any longer. I think the simplest solution maybe using the source in the 5.1 release and pointing the RSB 5 freetype URL to that file.
Any updates would be a change in the code and functionality.
Author: Chris Johns
2022-11-15T10:31:23.000Z
Resolution set to ~”fixed”
Status changed from new to closed
Author: Chris Johns
2025-09-19T01:11:14.489Z
changed the description
4758 - Net-Snmp referenced patch missing¶
Id |
4758 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-11-13T20:59:29.000Z |
Updated |
2025-09-19T01:25:08.578Z |
Milestone |
5.2 |
Labels |
libbsd, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
The Net-SNMP configuration references a patch that is missing. I cannot find it.
Update to 5.9.3 and for the libbsd stack.
Author: Chris Johns
2022-11-13T22:49:57.000Z
Attachment rtems-net-snmp-5.9.3-20221113.patch added
NetSNMP RTEMS 5.9.3 patch
Author: Trac Migrate
2022-11-14T20:58:25.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”c7e85e3319db59bc81c2b14fcc4f6c78b9a40b77/rtems-source-builder” c7e85e3/rtems-source-builder]:
rtems/net-snmp: Update to 5.9.3 with the RTEMS patch The 5.7.2.1 patch referenced in the configuration cannot be located so update the version to the latest. Checked with Zynq A9 qemu and libbsd. Closes #4758
Author: Chris Johns
2025-09-19T01:11:14.662Z
changed the description
4761 - RSB fatal error on missing hash checksums (cloned)¶
Id |
4761 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2022-11-15T02:25:36.000Z |
Updated |
2025-09-19T01:24:20.210Z |
Milestone |
5.2 |
Labels |
priority::high, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Cloned from #4760:
The time has come to raise a fatal error if a hash is missing rather than a warning. This will stop missing checksums being present when releasing.
It also makes it simpler to test releases for no missing checksums.
Author: Chris Johns
2022-11-15T10:33:25.000Z
Milestone changed from %”5.3” to %”5.2”
Author: Trac Migrate
2022-11-15T21:42:34.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”0a7ecef07e865464a9d98d8a6df36f4aac22e1ec/rtems-source-builder” 0a7ecef/rtems-source-builder]:
sb/downloads: Raise errors on no hash present Close #4761
Author: Chris Johns
2025-09-19T01:11:14.836Z
changed the description
4185 - arm/bsps: Small MMU pages are rounded to 1 MiB (cloned)¶
Id |
4185 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-11-24T08:34:18.000Z |
Updated |
2025-09-19T01:10:59.267Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Original author: soja
Cloned from #4184:
The function arm_cp15_start_set_translation_table_entries rounds the end address of a section up to 1 MiB even if small 4kiB pages are used (i.e. ARM_MMU_USE_SMALL_PAGES enabled).
Will submit a patch which only rounds the end address to 4kiB boundary.
Author: Trac Migrate
2020-12-02T12:39:29.000Z
Original author: soja
To keep track of it during the Christmas break: The patch is here:
https://lists.rtems.org/pipermail/devel/2020-November/063461.html
Author: Trac Migrate
2020-12-11T05:55:49.000Z
Original author: soja
Owner set to Jan Sommer <jan.sommer@dlr.de>
Resolution set to ~”fixed”
Status changed from new to closed
In [changeset:”21ed8d11c58c6a8f5bb8a5e03b8df50163a612f1/rtems” 21ed8d11/rtems]:
bsps/arm: Fix MMU small pages support - For small tables only round to the next 4kiB instead of 1MiB Close #4185.
Author: Trac Migrate
2020-12-15T10:27:33.000Z
Original author: soja
In [changeset:”2a8f7551074dea0082353e300aacb8581adae5d6/rtems” 2a8f755/rtems]:
bsps/arm: Fix MMU configuration Update #4185.
Author: Chris Johns
2025-09-19T01:10:59.231Z
mentioned in issue #4394
4096 - shell: CRTL-U sets the cursor to the wrong position¶
Id |
4096 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-09-28T12:12:11.000Z |
Updated |
2025-06-10T15:03:10.273Z |
Milestone |
5.2 |
Labels |
cpukit::shell, priority::normal, resolution::fixed, rtems::shell, tickettype::defect |
Link |
|
Merges |
1 |
Original author: frank_k
This patch fixes a tiny bug in the command line editing of the RTEMS shell. Typing CTRL-U in the shell should remove all characters left of the cursor. After pressing CTRL-U, the current implementation does wrongly place the cursor at the end of the line instead at its beginning.
To reproduce the bug, start the shell and type ‘abc123’ (no <RETURN>):
{{{ ~/src/rtems $ qemu-system-arm -net none -nographic -M realview-pbx-a9 -m 256M -kernel build/arm/realview_pbx_a9_qemu/testsuites/libtests/dl10.exe * BEGIN OF TEST libdl (RTL) 10 * * TEST VERSION: 6.0.0.d9bdf166644f612dd628fe4951c12c6f8e94ba5f * TEST STATE: USER_INPUT * TEST BUILD: RTEMS_DEBUG RTEMS_NETWORKING RTEMS_POSIX_API RTEMS_SMP * TEST TOOLS: 10.2.1 20200904 (RTEMS 6, RSB 31f936a7b74d60bda609a9960c6e1a705ba54974, Newlib a0d7982) RTL (libdl) commands: dl, rtl
RTEMS Shell on /dev/foobar. Use ‘help’ to list commands. SHLL [/] # abc123 }}}
Then move the cursor onto the ‘1’ by hitting three times the <ARROW-LEFT> key. Next type <CTRL>-U:
{{{ SHLL [/] # 123 }}}
Note that the cursor is at the end of the line (after ‘3’) instead of correctly at the beginning (on the ‘1’), now.
Continuing typing ‘echo ‘ incorrectly results in the output:
{{{ SHLL [/] # 123echo 123 }}}
The patch changes this behavior so that the cursor in the second last step will be on the ‘1’ and typing ‘echo ‘ will then correctly reflected as:
{{{ SHLL [/] # echo 123 }}}
Author: Trac Migrate
2020-09-28T12:21:17.000Z
Original author: frank_k
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”18549295beb0c6d3f1dc2027acfc1f043431cf12/rtems” 18549295/rtems]:
Fixing bug in line editing of the shell with CTRL-U. This patch fixes a tiny bug in the command line editing of the RTEMS shell. Typing CTRL-U in the shell should remove all characters left of the cursor. After pressing CTRL-U, the current implementation does wrongly place the cursor at the end of the line instead at its beginning. To reproduce the bug, start the shell and type 'abc123' (no <RETURN>): ~/src/rtems $ qemu-system-arm -net none -nographic -M realview-pbx-a9 \\ -m 256M -kernel build/arm/realview_pbx_a9_qemu/testsuites/libtests/dl10.exe *** BEGIN OF TEST libdl (RTL) 10 *** *** TEST VERSION: 6.0.0.d9bdf166644f612dd628fe4951c12c6f8e94ba5f *** TEST STATE: USER_INPUT *** TEST BUILD: RTEMS_DEBUG RTEMS_NETWORKING RTEMS_POSIX_API RTEMS_SMP *** TEST TOOLS: 10.2.1 20200904 \\ (RTEMS 6, RSB 31f936a7b74d60bda609a9960c6e1a705ba54974, Newlib a0d7982) RTL (libdl) commands: dl, rtl RTEMS Shell on /dev/foobar. Use 'help' to list commands. SHLL [/] # abc123 Then move the cursor onto the '1' by hitting three times the <ARROW-LEFT> key. Next type <CTRL>-U: SHLL [/] # 123 Note that the cursor is at the end of the line (after '3') instead of correctly at the beginning (on the '1'), now. Continuing typing 'echo ' incorrectly results in the output: SHLL [/] # 123echo 123 The patch changes this behavior so that the cursor in the second last step will be on the '1' and typing 'echo ' will then correctly reflected as: SHLL [/] # echo 123 Close #4096.
Author: Gedare Bloom
2025-06-10T15:03:10.658Z
changed the description
Author: Gedare Bloom
2025-06-10T15:03:15.374Z
mentioned in issue #4097
4232 - Timeout for automatic barriers is broken (cloned)¶
Id |
4232 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-02-06T20:03:57.000Z |
Updated |
2024-05-01T19:18:11.468Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, rtems::score, tickettype::defect, version::4.11 |
Link |
|
Merges |
1 |
Original author: sebastian.huber
Cloned from #4230:
A barrier wait timeout at an automatic barrier doesn’t decrement the count of waiting threads.
Author: Trac Migrate
2021-02-06T20:35:05.000Z
Original author: sebastian.huber
In [changeset:”5861e4256774bc2d629c703ac3d0a3692500ca0e/rtems” 5861e42/rtems]:
score: Constify Thread_queue_First_operation Update #4232.
Author: Trac Migrate
2021-02-06T20:35:09.000Z
Original author: sebastian.huber
In [changeset:”cc2a2371290b1a093b17e8a58913f78835cf5b9d/rtems” cc2a237/rtems]:
score: Make FIFO thread queue ops public Update #4232.
Author: Trac Migrate
2021-02-06T20:35:12.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”ef1ac8afff4b3b3700fdebdeb4a2ae04211b5686/rtems” ef1ac8af/rtems]:
score: Add barrier thread queue operations This fixes a missing decrement of the number of waiting threads during a barrier wait timeout. Close #4232.
Author: Ning Yang
2024-05-01T19:18:11.368Z
mentioned in merge request !9
4567 - Atomic store does not use the order parameter for C++ (cloned)¶
Id |
4567 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-12-07T11:07:44.000Z |
Updated |
2024-04-25T20:49:27.615Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, rtems::score, smp, tickettype::defect, version::4.11 |
Link |
|
Merges |
1 |
Original author: sebastian.huber
Cloned from #4566:
This could result in invalid inline code for the SMP ticket locks if used from C++.
Author: Trac Migrate
2021-12-07T11:25:53.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”18bbfc729ef81a1895c481da37e8700767e1144a/rtems” 18bbfc7/rtems]:
score: Fix atomic stores for C++ Close #4567.
Author: Amar Takhar
2024-04-25T20:49:27.664Z
changed the description
4347 - Allow RTEMS_PRIORITY for MrsP semaphores¶
Id |
4347 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-16T13:27:05.000Z |
Updated |
2024-04-25T20:48:44.584Z |
Milestone |
5.2 |
Labels |
priority::normal, qualification, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
1 |
Original author: sebastian.huber
In order to improve the compatibility of RTEMS 5.2 with future version of RTEMS which fixed #4346 allow MrsP semaphores to be created with RTEMS_PRIORITY.
Author: Trac Migrate
2021-03-17T09:47:01.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”0965b7c8b7956846167f43b813d68f8b5f2a60a1/rtems” 0965b7c8/rtems]:
rtems: Require RTEMS_PRIORITY for MrsP semaphores MrsP semaphores are a generalization of the priority ceiling semaphores for SMP configurations. Priority ceiling semaphores are required to use the priority task wait queue discipline. Require this discipline also for MrsP semaphores. Close #4347.
Author: Trac Migrate
2021-03-17T09:48:57.000Z
Original author: sebastian.huber
In [changeset:”3a66586c9e8432eee26b0e74c49c91362e22d24d/rtems” 3a66586/rtems]:
rtems: Allow RTEMS_PRIORITY for MrsP semaphores In order to improve the compatibility of RTEMS 5.2 with future version of RTEMS which fixed #4346 allow MrsP semaphores to be created with RTEMS_PRIORITY. Close #4347.
Author: Trac Migrate
2021-03-17T13:05:34.000Z
Original author: sebastian.huber
In [changeset:”7c43a4b4023587ab386d94c57b5c1f8a4afc604e/rtems-docs” 7c43a4b/rtems-docs]:
c-user: Update MrsP semaphore documentation Update #4347.
Author: Amar Takhar
2024-04-25T20:48:44.631Z
changed the description
4154 - Improve the workaround for the LEON3FT store-store errata: TN-0009¶
Id |
4154 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-10-16T05:45:40.000Z |
Updated |
2024-04-25T20:48:23.148Z |
Milestone |
5.2 |
Labels |
arch:sparc, priority::normal, qualification, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: sebastian.huber
See also:
https://www.gaisler.com/doc/antn/GRLIB-TN-0009.pdf
Some areas were already fixed by #3057.
Author: Trac Migrate
2021-03-07T15:56:20.000Z
Original author: sebastian.huber
In [changeset:”980cdb82a70c948b8531d99c3d1868725f503aa0/rtems” 980cdb8/rtems]:
sparc: Remove sequences that the B2BST scan script warns about Update #4154.
Author: Trac Migrate
2021-03-07T15:57:36.000Z
Original author: sebastian.huber
In [changeset:”3074eb0f37d4ac3ebcd19f9ea1b6566c1280bfa6/rtems” 3074eb0/rtems]:
sparc,leon: avoid triggering TN-0009 bad sequence Update #4154.
Author: Trac Migrate
2021-03-07T15:57:40.000Z
Original author: sebastian.huber
In [changeset:”2497a46a76161ef78340a7e3f54dcea44a74dd6a/rtems” 2497a46a/rtems]:
sparc,leon: avoid triggering LEON3FT errata TN-0009 Update #4154.
Author: Trac Migrate
2021-03-11T15:17:11.000Z
Original author: sebastian.huber
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
Author: Trac Migrate
2021-03-11T17:01:09.000Z
Original author: sebastian.huber
Summary changed from Add a workaround for the LEON3FT store-store errata: TN-0009 to Improve the workaround for the LEON3FT store-store errata: TN-0009
Author: Amar Takhar
2024-04-25T20:48:23.200Z
changed the description
4060 - The reworked <rtems/confdefs.h> has a cyclic dependency with RTEMS_MULTIPROCESSING enabled¶
Id |
4060 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-08-21T06:47:02.000Z |
Updated |
2024-04-25T20:48:18.601Z |
Milestone |
5.2 |
Labels |
priority::normal, qualification, resolution::fixed, rtems::config, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Original author: sebastian.huber
The changes for #3875 introduced a cyclic dependency between <rtems/confdefs/mpci.h> and <rtems/confdefs/threads.h>.
Author: Trac Migrate
2020-08-21T18:03:24.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”7661402bc2a35c267f532788bd882f5fe393d297/rtems” 7661402/rtems]:
confdefs: Fix cyclic dependency Close #4060.
Author: Amar Takhar
2024-04-25T20:48:18.650Z
changed the description
3540 - How To Use SPARC memscrub¶
Id |
3540 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Trac Migrate |
Created |
2018-10-05T16:32:08.000Z |
Updated |
2024-04-25T20:46:31.740Z |
Milestone |
5.2 |
Labels |
priority::normal, qualification, resolution::wontfix, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
The SPARC memory scrubber code on the RTEMS master is undocumented from a using standpoint. Google shows the RCC has documentation (chapter 49) using it. Can this information be made available in the RTEMS Ecosystem somehow?
Author: Joel Sherrill
2018-10-05T16:32:26.000Z
Owner set to daniel
Status changed from new to assigned
Author: Joel Sherrill
2018-10-13T22:54:56.000Z
Milestone changed from %”5.1” to %”5.2”
Author: Chris Johns
2022-11-09T23:06:34.000Z
Resolution set to ~”wontfix”
Status changed from assigned to closed
Please reopen if this is going to be worked on.
Author: Amar Takhar
2024-04-25T20:46:31.774Z
changed the description
4274 - GR1553RT driver: fixes to memory allocation and locking on descriptor updates¶
Id |
4274 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-02-26T15:23:59.000Z |
Updated |
2022-12-14T23:27:11.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
Issues in GRLIB GR1553B RT mode device driver (used by GR740 BSP): gr1553rt_list_init() - fixed memory leak when dynamic allocation failed gr1553rt_bd_update() - release interrupt/spin-lock correctly
Author: Trac Migrate
2021-03-07T15:56:23.000Z
Original author: daniel
In [changeset:”a97a4732f7c2c3ea34b7de1ddbcf383ed6a6c5d1/rtems” a97a473/rtems]:
leon,gr1553rt: Fixed memory leak Update #4274.
Author: Trac Migrate
2021-03-07T15:56:26.000Z
Original author: daniel
In [changeset:”1223f5e402ea38c2083b03982ce947b67d4c0538/rtems” 1223f5e/rtems]:
leon,gr1553rt: Fixed spinlock unlock Update #4274.
Author: Trac Migrate
2021-03-09T13:20:48.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4275 - GR1553B: use new codec available in GR740 revision 1¶
Id |
4275 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-02-26T15:46:50.000Z |
Updated |
2022-12-14T23:26:11.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
Select the new 1553 codec available specifically in GR740.
Author: Trac Migrate
2021-03-07T15:56:30.000Z
Original author: daniel
In [changeset:”14fcf388914d9c4abc0f1a67f030762c8f78d830/rtems” 14fcf388/rtems]:
leon,gr1553b: set codec version This is enables the updated codec for GR740 and is backwards compatible with all other versions of the IP. Updates #4275.
Author: Trac Migrate
2021-03-09T13:21:45.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4359 - Priority discipline is broken for semaphores and message queues in SMP configurations (cloned)¶
Id |
4359 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-25T08:09:28.000Z |
Updated |
2022-11-09T23:25:23.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::wontfix, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: sebastian.huber
Cloned from #4358:
The priority queues in clustered scheduling configurations use a per scheduler priority queue rotation to ensure FIFO fairness across schedulers. This mechanism is implemented in the thread queue surrender operation. Unfortunately some semaphore and message queue directives use wrongly the thread queue extract operation.
Author: Chris Johns
2022-11-09T23:25:23.000Z
Original author: sebastian.huber
Resolution set to ~”wontfix”
Status changed from assigned to closed
Please use RTEMS 6 for SMP. Please reopen if this is to be fixed on the RTEMS 5 branch.
4357 - rtems_semaphore_set_priority() uses an invalid SMP lock (cloned)¶
Id |
4357 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-23T17:14:20.000Z |
Updated |
2022-11-09T23:24:24.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::wontfix, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: sebastian.huber
Cloned from #4356:
If the priority of a locked priority ceiling mutex is set, the used SMP lock sequence is invalid.
Author: Chris Johns
2022-11-09T23:24:24.000Z
Original author: sebastian.huber
Resolution set to ~”wontfix”
Status changed from assigned to closed
Please use RTEMS 6 for SMP
4119 - rtems-bsp-tester: Off By One for Completed Jobs¶
Id |
4119 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Chris Johns |
Created |
2020-10-02T17:36:58.000Z |
Updated |
2022-11-09T23:17:29.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::wontfix, tickettype::defect, tool, version::5 |
Link |
|
Merges |
0 |
Looking at https://lists.rtems.org/pipermail/build/2020-September/019154.html, you can see that the completed number of jobs doesn’t match up with the number for the last build:
Total Time : 2:05:13.725904 for 1696 completed job(s)
Average BSP Build Time: 0:00:04.430262
.....
1695 profiling v850/v850sim build:
configure: /home/joel/rtems-cron-6/rtems/configure\\
--target=v850-rtems6 --enable-rtemsbsp=v850sim --prefix=/home/joel\\
/rtems-cron-6/tools/6/bsps --enable-profiling --disable-smp
I think there are 1695 jobs completed not 1696. :)
Author: Chris Johns
2022-11-09T23:17:29.000Z
Resolution set to ~”wontfix”
Status changed from assigned to closed
Please reopen if this is still valid and important for the 5 branch.
4102 - rtems-pairs includes invalid BSP¶
Id |
4102 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Chris Johns |
Created |
2020-09-29T22:00:07.000Z |
Updated |
2022-11-09T23:16:11.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::wontfix, tickettype::defect, tool, version::5 |
Link |
|
Merges |
0 |
On both 5 and master, the list of BSP pairs includes bbxm which appears to come from the file bsps/arm/beagle/simscripts/bbxm.cfg which is obviously not a build configuration file.
arm: (families:21 bsps:57)
altcycv_devkit altera-cyclone-v
atsamv atsam
bbxm beagle
beagleboardorig beagle
beagleboardxm beagle
beagleboneblack beagle
beaglebonewhite beagle
Author: Joel Sherrill
2020-09-29T22:00:18.000Z
Owner set to @chrisj
Status changed from new to assigned
Author: Chris Johns
2022-11-09T23:16:11.000Z
Resolution set to ~”wontfix”
Status changed from assigned to closed
4064 - RSB needs to support waf with no python command¶
Id |
4064 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2020-08-28T00:25:08.000Z |
Updated |
2022-11-09T23:14:51.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Recent Linux distros may not provide a python command by default. This breaks building any waf based tools such as the rtems-tools and rtems-libbsd.
Provide support for waf builds by check for a suitable Python executable and using it to directly invoke waf. For example:
/usr/local/bin/python3.7 ./waf configure --prefix=/blah/blah
Author: Chris Johns
2022-11-09T23:14:51.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
RTEMS 5 has a hack’ish detect that has been removed in RTEMS 6.
3601 - Block device disk management implementation can underflow rtems_disk_device.uses¶
Id |
3601 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2018-11-12T01:35:03.000Z |
Updated |
2022-11-09T23:08:11.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::wontfix, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: Kevin Gordon
The source file discdevs.c contains logic error with regard to a rtems_disk_device.uses member, in that the .uses value can underflow and wrap-around because this member is unsigned and the implementation does not check for a current value of 0.
Case in point, see diskdevs.c line 373:
physical_disk->uses -= deleted_count;
If deleted_count is greater than physical_disk->uses, e.g. physical_disk->uses is 0 and deleted_count is 1, physical_disk->uses will underflow. There are other references to the uses member that can result in errors, e.g., line 448:
uses = –dd->uses;
We discovered this bug via a unit-test that creates multiple RAM disks and then attempts to delete them, without any uses, resulting in RTEMS errors because the uses member had wrapped around. To circumvent this bug, we had to force the uses member to a value of 1 prior to calling rtems_disk_release(), which then successfully deleted the RAM disks via rtems_disk_delete(), otherwise the results cascaded into error situations that were undesirable.
Author: Trac Migrate
2018-11-12T06:21:35.000Z
Original author: Kevin Gordon
This API is deprecated in RTEMS 5.1 and will be removed in RTEMS 6.1.
Author: Trac Migrate
2019-01-29T08:06:16.000Z
Original author: Kevin Gordon
Milestone changed from %”5.1” to %”5.2”
If you want to get this fixed, then please send a patch to devel@rtems.org. I would avoid this API and use rtems_blkdev_create() and rtems_blkdev_create_partition() instead.
Author: Trac Migrate
2020-07-13T15:22:47.000Z
Original author: Kevin Gordon
Owner set to Needs Funding
Status changed from new to assigned
Author: Chris Johns
2022-11-09T23:07:23.000Z
Original author: Kevin Gordon
Milestone changed from %”5.2” to %”Indefinite”
Author: Chris Johns
2022-11-09T23:08:11.000Z
Original author: Kevin Gordon
Milestone changed from %”Indefinite” to %”5.2”
Resolution set to ~”wontfix”
Status changed from assigned to closed
Sebastian has recommended avoiding this API.
4106 - RSB Missing BSP bset for xilinx_zynq_a9_qemu¶
Id |
4106 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Trac Migrate |
Created |
2020-09-30T15:52:28.000Z |
Updated |
2022-11-09T22:32:24.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::wontfix, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
This needs to be added to the RSB for 5 and master.
Author: Chris Johns
2022-11-09T22:32:24.000Z
Resolution set to ~”wontfix”
Status changed from new to closed
Please reopen when the bset is added.
4071 - RSB does not pass BSP options correctly.¶
Id |
4071 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-09-06T22:19:37.000Z |
Updated |
2022-11-09T22:31:38.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: kgardas
Using 5.1 RTEMS release and RSB to build the beast I’ve found out it’s not able to pass BSP options correctly using –with-rtems-bspopts option:
../source-builder/sb-set-builder
--prefix=$HOME/sfw/rtems/5.1-smp2-vga80x50-key-to-reset 5/bsps/pc
--with-rtems-tests --with-rtems-smp
--with-rtems-bspopts="BSP_VIDEO_80x50=1 BSP_PRESS_KEY_FOR_RESET=1"
command fails with:
Build Set: Time 0:00:28.975685
Build Set: Time 0:03:36.556012
installing: 5/bsps/pc ->
/export/home/karel/sfw/rtems/5.1-smp2-vga80x50-key-to-reset
clean staging: 5/bsps/pc
Staging Size: 4.271GB
Build Set: Time 0:24:53.756984
Build Set: BSP_PRESS_KEY_FOR_RESET=1
error: no build set file found: BSP_PRESS_KEY_FOR_RESET=1.bset
Build Set: Time 0:00:00.000420
Build FAILED
It looks like even if I use just one BSP options, it’s still not passed to the BSP, but build is built fine at least.
Author: Chris Johns
2022-11-09T22:31:38.000Z
Original author: kgardas
Resolution set to ~”fixed”
Status changed from new to closed
The RTEMS 5 RSB has been updated to support deployment and I think this will now be fixed. Please refer to the RTEMS Deployment repo for example configurations known to work.
4059 - RSB: UnicodeDecodeError¶
Id |
4059 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-08-21T06:12:00.000Z |
Updated |
2022-11-09T22:21:25.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Original author: sebastian.huber
The RSB some times cannot create a report due to an Unicode decode error:
error: building powerpc-rtems5-gdb-9.1-x86_64-linux-gnu-1
Build FAILED
error: failure to create error report
Build Set: Time 0:01:29.712543
Traceback (most recent call last):
File "../source-builder/sb/cmd-set-builder.py", line 26, in <module>
setbuilder.run()
File "/scratch/git-rtems-release/5.1-rc2/rtems-source-builder-5.1-rc2/source-builder/sb/setbuilder.py", line 736, in run
b.build(deps, mail = mail)
File "/scratch/git-rtems-release/5.1-rc2/rtems-source-builder-5.1-rc2/source-builder/sb/setbuilder.py", line 473, in build
self.build_package(configs[s], b)
File "/scratch/git-rtems-release/5.1-rc2/rtems-source-builder-5.1-rc2/source-builder/sb/setbuilder.py", line 258, in build_package
_build.make()
File "/scratch/git-rtems-release/5.1-rc2/rtems-source-builder-5.1-rc2/source-builder/sb/build.py", line 603, in make
self._generate_report_('Build: %s' % (gerr))
File "/scratch/git-rtems-release/5.1-rc2/rtems-source-builder-5.1-rc2/source-builder/sb/build.py", line 126, in _generate_report_
self.opts, header, footer)
File "/scratch/git-rtems-release/5.1-rc2/rtems-source-builder-5.1-rc2/source-builder/sb/ereport.py", line 56, in generate
l.write(os.linesep.join(r))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 50: ordinal not in range(128)
RSB Error Report:
Author: Trac Migrate
2021-09-17T06:25:25.000Z
Original author: sebastian.huber
This error also happens when the RSB tool is trying to build RTEMS for others architectures and packages (found on release 5.1): building: rtems-tools-29ad0ec7a8ec8aae5afeb32ef8be03707f626843-1 error: building rtems-tools-29ad0ec7a8ec8aae5afeb32ef8be03707f626843-1 Build FAILED error: failure to create error report Build Set: Time 3:07:57.408978 Traceback (most recent call last): File “../source-builder/sb/cmd-set-builder.py”, line 26, in <module> setbuilder.run() File “$Dev/RTEMS/rtems-bbb/tools/rtems-source-builder/source-builder/sb/setbuilder.py”, line 736, in run b.build(deps, mail = mail) File “$Dev/RTEMS/rtems-bbb/tools/rtems-source-builder/source-builder/sb/setbuilder.py”, line 473, in build self.build_package(configs[s], b) File “$Dev/RTEMS/rtems-bbb/tools/rtems-source-builder/source-builder/sb/setbuilder.py”, line 258, in build_package _build.make() File “$Dev/RTEMS/rtems-bbb/tools/rtems-source-builder/source-builder/sb/build.py”, line 603, in make self._generate_report_(‘Build: %s’ % (gerr)) File “$Dev/RTEMS/rtems-bbb/tools/rtems-source-builder/source-builder/sb/build.py”, line 126, in _generate_report_ self.opts, header, footer) File “$Dev/RTEMS/rtems-bbb/tools/rtems-source-builder/source-builder/sb/ereport.py”, line 56, in generate l.write(os.linesep.join(r)) UnicodeDecodeError: ‘ascii’ codec can’t decode byte 0xe2 in position 70: ordinal not in range(128)
Author: Trac Migrate
2021-12-22T11:37:04.000Z
Original author: sebastian.huber
This error occurs when the python locale environment is not set correctly. I got this for an compile error message when rtems-source-builder failing to building expat on MacOS.
ensuring LANG and LC_ALL are set fixed the problem writing the error log
export LANG=’en_US.UTF-8’ LC_ALL=’en_US.UTF-8’
LANG is generally set correctly on macos.
if one is setting one of the LC_* variables to a different locale (I use LC_TIME=”de_DE.UTF-8”)
then python assumes the encoding is ascii only.
setting LC_ALL overrides this and python happily uses utf-8 again.
Author: Chris Johns
2022-11-09T22:21:25.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from new to closed
Fixed here https://git.rtems.org/rtems-source-builder/commit/?h=5&id=ddfcc320ab740cd6ac30d70aaff7987dda25ee7f
4011 - Test compilation error in riscv bsps¶
Id |
4011 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-06-22T07:06:41.000Z |
Updated |
2022-11-09T22:17:48.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::wontfix, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: soja
Configuring the riscv bsps with –enable-tests fails to build at least the dl06 test.
../rtems-5.0.0-m2006-2/configure –target=riscv-rtems5 –prefix../install/bsps –disable-networking –enable-tests –enable-rtemsbsp=griscv
Error during the compilation step:
rtems-ld -r /localdata2/somm_ja/rtems/5-0-rc/build-riscv/riscv-rtems5/c/griscv -C riscv-rtems5-gcc -c “-march=rv32imafd -mabi=ilp32d” -O rap -b dl06.pre -e rtems_main -s -o dl06.rap dl06-o1.o dl06-o2.o -lm error: rap::object: Section index ‘0’ not found: dl06-o1.o Makefile:8479: recipe for target ‘dl06.rap’ failed make[5]: * [dl06.rap] Error 10 make[5]: Leaving directory ‘/localdata2/somm_ja/rtems/5-0-rc/build-riscv/riscv-rtems5/c/griscv/testsuites/libtests’ Makefile:663: recipe for target ‘libtests’ failed make[4]: * [libtests] Error 2 make[4]: Leaving directory ‘/localdata2/somm_ja/rtems/5-0-rc/build-riscv/riscv-rtems5/c/griscv/testsuites’ Makefile:1222: recipe for target ‘testsuites’ failed make[3]: * [testsuites] Error 2 make[3]: Leaving directory ‘/localdata2/somm_ja/rtems/5-0-rc/build-riscv/riscv-rtems5/c/griscv’ Makefile:716: recipe for target ‘all-recursive’ failed make[2]: * [all-recursive] Error 1 make[2]: Leaving directory ‘/localdata2/somm_ja/rtems/5-0-rc/build-riscv/riscv-rtems5/c/griscv’ Makefile:289: recipe for target ‘all-recursive’ failed make[1]: * [all-recursive] Error 1 make[1]: Leaving directory ‘/localdata2/somm_ja/rtems/5-0-rc/build-riscv/riscv-rtems5/c’ Makefile:410: recipe for target ‘all-recursive’ failed make: * [all-recursive] Error 1 make all 112,71s user 27,01s system 102% cpu 2:16,13 total
Author: Chris Johns
2022-11-09T22:17:48.000Z
Original author: soja
Resolution set to ~”wontfix”
Status changed from new to closed
Please use the RISCV support in RTEMS 6.
2746 - RTEMS gdb python script do not load.¶
Id |
2746 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Trac Migrate |
Created |
2016-06-24T23:49:05.000Z |
Updated |
2022-11-09T22:14:21.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::wontfix, tickettype::defect, tool::gdb, version::5 |
Link |
|
Merges |
0 |
Loading the scripts does not work …
(gdb) python import rtems
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/opt/work/rtems/4.12/share/gdb/python/rtems/__init__.py", line 31, in <module>
import rtems
File "/opt/work/rtems/4.12/share/gdb/python/rtems/rtems.py", line 38, in <module>
import threads
File "/opt/work/rtems/4.12/share/gdb/python/rtems/threads.py", line 39, in <module>
import rbtrees
ImportError: No module named rbtrees
Error while executing Python code.
(gdb)
Author: Chris Johns
2016-06-24T23:49:53.000Z
Description changed
Loading the scripts does not work ... + {{{ (gdb) python import rtems Traceback (most recent call last): File "<string>", line 1, in <module> File "/opt/work/rtems/4.12/share/gdb/python/rtems/__init__.py", line 31, in <module> import rtems File "/opt/work/rtems/4.12/share/gdb/python/rtems/rtems.py", line 38, in <module> import threads File "/opt/work/rtems/4.12/share/gdb/python/rtems/threads.py", line 39, in <module> import rbtrees ImportError: No module named rbtrees Error while executing Python code. (gdb) + }}}
Author: Chris Johns
2017-03-27T06:48:47.000Z
Milestone changed from %”4.12.1” to %”4.12.0”
Move to the first 4.12 milestone.
Author: Joel Sherrill
2017-10-12T02:48:37.000Z
Milestone changed from %”4.12.0” to %”4.12.1”
Author: Trac Migrate
2017-11-09T06:27:05.000Z
Milestone changed from %”4.12.1” to %”5.2”
Milestone renamed
Author: Chris Johns
2022-11-09T22:14:21.000Z
Resolution set to ~”wontfix”
Status changed from new to closed
The scripts are too hard to maintain on the 5 branch because a lot of detail in the
scorehas changed. On 6 and laterlibdebuggerprovides a highlevel access to a number of pieces or data.
4058 - RSB 5/rtems-riscv fails to build on Windows¶
Id |
4058 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Trac Migrate |
Created |
2020-08-20T22:33:34.000Z |
Updated |
2022-09-08T03:36:29.000Z |
Milestone |
5.2 |
Labels |
priority::high, resolution::wontfix, tickettype::defect, tool::gdb, version::5 |
Link |
|
Merges |
0 |
To repeat run rtems-release-test 5 1-rc2 on Windows.
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ada-tasks.o: in function `memcpy':
C:/msys64/mingw64/x86_64-w64-mingw32/include/string.h:202: undefined reference to `__memcpy_chk'
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: breakpoint.o: in function `strcpy':
C:/msys64/mingw64/x86_64-w64-mingw32/include/string.h:228: undefined reference to `__strcpy_chk'
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:/msys64/mingw64/x86_64-w64-mingw32/include/string.h:228: undefined reference to `__s
trcpy_chk'
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: breakpoint.o: in function `memset':
C:/msys64/mingw64/x86_64-w64-mingw32/include/string.h:208: undefined reference to `__memset_chk'
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: breakpoint.o: in function `sprintf(char*, char const*, ...)':
C:/msys64/mingw64/x86_64-w64-mingw32/include/stdio.h:366: undefined reference to `__chk_fail'
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cli/cli-decode.o: in function `strcat':
C:/msys64/mingw64/x86_64-w64-mingw32/include/string.h:234: undefined reference to `__strcat_chk'
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:/msys64/mingw64/x86_64-w64-mingw32/include/string.h:234: undefined reference to `__m
emcpy_chk'
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:/msys64/mingw64/x86_64-w64-mingw32/include/string.h:234: undefined reference to `__m
emcpy_chk'
I think this has been resolved in a later GDB version.
Author: Chris Johns
2022-09-08T03:36:29.000Z
Resolution set to ~”wontfix”
Status changed from new to closed
Please use RTEMS 6. The RISCV is in the tier-4 list for this release.
4024 - NFS Client is broken on 64-bit targets¶
Id |
4024 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-07-08T11:33:11.000Z |
Updated |
2022-08-17T06:09:40.000Z |
Milestone |
5.2 |
Labels |
libbsd, priority::normal, resolution::wontfix, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: sebastian.huber
Packed and unpacked structures are mixed leading to invalid XDR encode/decode operations if addresses > 4GiB are used.
Author: Chris Johns
2020-08-10T05:44:39.000Z
Original author: sebastian.huber
Milestone changed from %”5.1” to %”5.2”
Author: Chris Johns
2022-08-17T06:09:40.000Z
Original author: sebastian.huber
Resolution set to ~”wontfix”
Status changed from assigned to closed
Use master or RTEMS 6.
4655 - sync() whould synchronize all file descriptors¶
Id |
4655 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2022-05-13T10:58:34.000Z |
Updated |
2022-05-17T13:24:35.000Z |
Milestone |
5.2 |
Labels |
filesystem, priority::normal, resolution::fixed, tickettype::defect, version::4.5 |
Link |
|
Merges |
1 |
Original author: sebastian.huber
According to POSIX
https://pubs.opengroup.org/onlinepubs/9699919799/functions/sync.html
we have
The sync() function shall cause all information in memory that updates file systems to be scheduled for writing out to all file systems.
Currently, the RTEMS sync() implementation synchronizes only the file descriptors associated with a FILE object. This should be changed to call fsync() and fdatasync() for all file descriptors.
Author: Trac Migrate
2022-05-17T13:24:35.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”8d54187a19f6e6d2849066f80254730302482934/rtems” 8d54187/rtems]:
Synchronize all file descriptors in sync() Synchronize all file descriptors and not just the ones associated with a FILE object. Close #4655.
4310 - bsps,leon3: BSP assumes that timer pre-scaler runs at 1MHz¶
Id |
4310 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:19:31.000Z |
Updated |
2021-10-20T08:16:23.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
When driver manager GPTIMER driver is used a different pre-scaler can be supported by a driver setting. This is used to increase the resolution of the timer.
Author: Trac Migrate
2021-03-07T15:57:12.000Z
Original author: daniel
In [changeset:”81e4a15b188a8d3aff526fc39ca6f09ac85d27bb/rtems” 81e4a15/rtems]:
leon,ckinit: avoid assuming 1MHz timer pre-scaler clock Update #4310.
Author: Trac Migrate
2021-03-09T13:27:14.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
Author: Trac Migrate
2021-10-20T08:16:23.000Z
Original author: daniel
Is there the same assumption in RTEMS 4.8 too?
4370 - RTEMS5: Add spi driver for AXI SPI ip core from Xilinx (cloned)¶
Id |
4370 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-31T08:06:09.000Z |
Updated |
2021-04-06T13:16:42.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
1 |
Original author: soja
Cloned from #4321: –> Backport to RTEMS5
Add a spidev compatible driver for the xilinx axi quad spi ip core for standard SPI mode
Author: Trac Migrate
2021-03-31T08:06:22.000Z
Original author: soja
Owner set to soja
Status changed from new to accepted
Author: Trac Migrate
2021-04-06T13:16:32.000Z
Original author: soja
In [changeset:”ce2b276803e6febe0492a89e48ae5de3a7d88cf1/rtems” ce2b276/rtems]:
bsps/xilinx_zynq: Add SPI driver for xilinx-axi-spi Updates #4370
Author: Trac Migrate
2021-04-06T13:16:42.000Z
Original author: soja
Resolution set to ~”fixed”
Status changed from accepted to closed
In [changeset:”ec2660548eea901e2159cf8dd3f8cd4ddd8aa6be/rtems” ec26605/rtems]:
bsps/xilinx_zynq: Add Xilinx AXI SPI driver to build Closes #4370
4369 - RTEMS5: Add driver for cadence-spi device for xilinx based BSPs (cloned)¶
Id |
4369 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-31T07:15:07.000Z |
Updated |
2021-04-06T13:16:22.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
1 |
Original author: soja
Cloned from #4320: Backport to RTEMS5
Implement a spidev compatible driver for using the cadence-spi device of the Zynq devices in standard SPI mode.
Author: Trac Migrate
2021-03-31T07:15:33.000Z
Original author: soja
Owner set to soja
Status changed from new to accepted
Author: Trac Migrate
2021-04-06T13:16:11.000Z
Original author: soja
In [changeset:”c86d5136648ccffb63f444a15ec529ef52a270cb/rtems” c86d5136/rtems]:
bsps/xilinx_zynq: Add SPI driver for cadence-spi Updates #4369
Author: Trac Migrate
2021-04-06T13:16:22.000Z
Original author: soja
Resolution set to ~”fixed”
Status changed from accepted to closed
In [changeset:”14e74e43125ddc6cc831812e089e3423e8706fb6/rtems” 14e74e4/rtems]:
bsps/xilinx_zynq: Add cadence SPI driver to build system Closes #4369
4316 - grlib,grspw_pkt: SpaceWire link-state defines corrected¶
Id |
4316 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:45:22.000Z |
Updated |
2021-03-09T13:30:05.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
Numbering of SPW_LS_CONNECTING and SPW_LS_STARTED was swapped.
Author: Trac Migrate
2021-03-07T15:57:33.000Z
Original author: daniel
In [changeset:”291267113bdf2c453790fe1f6dc7c1933cf57515/rtems” 29126711/rtems]:
grlib,grspw_pkt: correct link state enum numbering Not used by the driver itself, but shuold be correct if used by application. Update #4316.
Author: Trac Migrate
2021-03-09T13:30:05.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4315 - grlib,l2cache: prevent unused diagnostic access¶
Id |
4315 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:42:54.000Z |
Updated |
2021-03-09T13:29:33.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
GR740 L2-cache driver improvement.
Author: Trac Migrate
2021-03-07T15:57:30.000Z
Original author: daniel
In [changeset:”8cfaa0eb76d248ea9afab471708fe7d35cd05a48/rtems” 8cfaa0eb/rtems]:
leon, l2cache: prevent unused diagnostic access Update #4315.
Author: Trac Migrate
2021-03-09T13:29:33.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
Minor improvement, no need to add to 5.2 changelog.
4314 - grlib,ahbstat: add new register definitions for AHBSTAT version 1¶
Id |
4314 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:40:01.000Z |
Updated |
2021-03-09T13:29:07.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
This is needed for GR740 users.
Author: Trac Migrate
2021-03-07T15:57:26.000Z
Original author: daniel
In [changeset:”b0eb952427513d978ec6d80a1b86ac56abeb2a95/rtems” b0eb9524/rtems]:
leon, ahbstat: register definitions for AHBSTAT version 1 Update #4314.
Author: Trac Migrate
2021-03-09T13:29:07.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4313 - grlib,grspw_router: add function to control SpaceWire run clock divisor¶
Id |
4313 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:37:36.000Z |
Updated |
2021-03-09T13:28:44.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
The driver needs to allow the user to set SpaceWire run clock divisor for an individual port.
Author: Trac Migrate
2021-03-07T15:57:22.000Z
Original author: daniel
In [changeset:”1161e1fb92fa5d01f66ab5b796d1813d0c0123a3/rtems” 1161e1f/rtems]:
leon, grspw_router: added router_port_link_div() Allows user to set SpaceWire run clock divisor for an individual port. Update #4313.
Author: Trac Migrate
2021-03-09T13:28:44.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4312 - bsps,leon3: need to make cpucounter restart after underflow¶
Id |
4312 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:34:33.000Z |
Updated |
2021-03-09T13:28:21.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
Fix for the BSP timer initialization when GPTIMER is used as the cpucounter. Without restarting in HW the cpucounter would stop after some time.
Author: Trac Migrate
2021-03-07T15:57:16.000Z
Original author: daniel
In [changeset:”cb8379dc0915c10960a0923a9869e98869e410bd/rtems” cb8379d/rtems]:
leon: restart and load timer counter at initialization Without this smp05 and smpthreadlife01 tests may fail depending on how the boot loader initialized the GPTIMER. Before the time counter stopped counting when reaching zero, but tests could work since it could take 2^32 us before stopping. The timer driver will potentially overwrite this, but it happens later due to the initialization order having RTEMS_SYSINIT_CPU_COUNTER very early. Update #4312.
Author: Trac Migrate
2021-03-09T13:28:21.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4311 - bsps,leon3: _st64() did not follow the SPARC ABI¶
Id |
4311 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:29:23.000Z |
Updated |
2021-03-09T13:27:56.000Z |
Milestone |
5.2 |
Labels |
arch:sparc, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
STD instruction requires even register alignment for 64-bit data.
Author: Trac Migrate
2021-03-07T15:57:19.000Z
Original author: daniel
In [changeset:”d9d96f06084b1c7d4bd8653f26cc1001b5de1d56/rtems” d9d96f0/rtems]:
sparc: fix bad register alignment for 64 bit store Update #4311.
Author: Trac Migrate
2021-03-09T13:27:56.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4309 - bsps,leon3: avoid BSP dependency on apbuart/timer driver¶
Id |
4309 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:13:17.000Z |
Updated |
2021-03-09T13:26:49.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
The BSP amba.c references the GPTIMER and APBUART drivers causing them to be dragged in when the driver manager is used. By moving the dependencies to a separate file the user can override the default without dragging in unused drivers.
Author: Trac Migrate
2021-03-07T15:57:09.000Z
Original author: daniel
In [changeset:”0ed294b6cce8f1cb123327f32eb8fdc973d7f4a7/rtems” 0ed294b6/rtems]:
leon3: avoid dependency on apbuart/timer driver Moves drvmgr_drivers[] from amba.c to a separate file in order to avoid the dependecy on APBUART/GPTIMER drivers. This has an effect when user configured not to use timer or uart in their project. Update #4309.
Author: Trac Migrate
2021-03-09T13:26:49.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4308 - grlib,greth: added support for variable sized descriptor table sizes¶
Id |
4308 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:06:05.000Z |
Updated |
2021-03-09T13:26:25.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
Author: Trac Migrate
2021-03-07T15:57:06.000Z
Original author: daniel
In [changeset:”c13205f6916544c6f8bb2ade7ed5f2959ae6f173/rtems” c13205f/rtems]:
leon,greth: added support for variable sized descriptor table sizes The descriptor table size is equal to its alignment and set when configuring the HW IP through VHDL generics. This SW patch simply probes the HW how large the RX/TX descriptor tables are and adjusts accordingly. The number of descriptors actual used are controlled by other settings (rxDescs and txDescs) controlled by the user. Update #4308.
Author: Trac Migrate
2021-03-09T13:26:25.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
Minor improvement, no need to add to 5.2 changelog.
4307 - grlib,grcanfd: extend the GRCAN driver with GRCANFD support¶
Id |
4307 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T14:00:03.000Z |
Updated |
2021-03-09T13:25:50.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
The new GRCAN_FD IP supports CAN FD standard and is mostly backwards compatible with GRCAN SW interface. It introduces support for CAN-FD frames and a new bit-rate timing registers for new baud-rate.
The GRCAN driver have been extended to support the GRCANFD IP using the same API. Device IP-core specific functions are split into different files (grcanstd.c and grcanfd.c).
Author: Trac Migrate
2021-03-07T15:56:53.000Z
Original author: daniel
In [changeset:”e1062fae3cf16e08c949ff1bac732a0ed79d7a3a/rtems” e1062fae/rtems]:
grlib: added 64-bit read no-cache function Update #4307.
Author: Trac Migrate
2021-03-07T15:56:56.000Z
Original author: daniel
In [changeset:”c41e7bae9cf8a04be6fdebe4c7ebd327f39faf02/rtems” c41e7ba/rtems]:
leon,grcan: added support for GRCANFD The new GRCAN_FD IP supports CAN FD standard and is mostly backwards compatible with GRCAN SW interface. The GRCAN driver have been extended to support the GRCANFD IP using the same driver. Additional functions have been added that uses a new CAN FD frame format and read/write/baud-rate functions that supports both GRCANFD and GRCAN. To keep the SW API fully backwards compatible with GRCAN, the old functions remain. Update #4307.
Author: Trac Migrate
2021-03-07T15:56:59.000Z
Original author: daniel
In [changeset:”e180f281abc778d9ca7ca798d4a81d5da1a507da/rtems” e180f281/rtems]:
leon,grcanfd: split out GRCANFD specific support in separate file Update #4307.
Author: Trac Migrate
2021-03-07T15:57:03.000Z
Original author: daniel
In [changeset:”23cc5a6090a4610b96cc593e2d11a6b3c028b41a/rtems” 23cc5a6/rtems]:
leon,grcan: split out GRCAN non-FD specific support in separate file Update #4307.
Author: Trac Migrate
2021-03-09T13:25:50.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4306 - grlib,can: introduce a new common CAN baud-rate timing calculating functions¶
Id |
4306 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T13:46:26.000Z |
Updated |
2021-03-09T13:25:01.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
There is no point in having two different implementations specific per GRLIB CAN device driver (OCCAN and GRCAN). Instead we can use the common CAN timing definitions and translate that into the device specific parameters using a new common calculation function.
Author: Trac Migrate
2021-03-07T15:56:43.000Z
Original author: daniel
In [changeset:”da7cb87b4df3047795f0674775131b34469d5fa5/rtems” da7cb87/rtems]:
leon,can: introduce common CAN baud-rate calculation function Reimplemented the baud-rate algorithm from scratch to cope with GRCAN, GRCANFD and OC_CAN devices. Update #4306.
Author: Trac Migrate
2021-03-07T15:56:46.000Z
Original author: daniel
In [changeset:”78b45cc56169830f788458d908d308f483d41d9e/rtems” 78b45cc5/rtems]:
leon,grcan: use common CAN baud-rate calculation routine Update #4306.
Author: Trac Migrate
2021-03-07T15:56:49.000Z
Original author: daniel
In [changeset:”7db032cf0216747a87b2ad4b0af07f073cb8a722/rtems” 7db032cf/rtems]:
leon,occan: use common CAN baud-rate calculation routine Update #4306.
Author: Trac Migrate
2021-03-09T13:25:01.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4305 - grlib,ambapp: update GRLIB IP core ID list¶
Id |
4305 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T13:41:16.000Z |
Updated |
2021-03-09T13:24:23.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
Add the new AMBA PnP IDs of the new cores.
Author: Trac Migrate
2021-03-07T15:56:39.000Z
Original author: daniel
In [changeset:”0ab993b04a0a0e96b9e0d23941f102b54fe36147/rtems” 0ab993b/rtems]:
grlib,ambapp: added new IP core IDs Update #4305.
Author: Trac Migrate
2021-03-09T13:24:23.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
Minor improvement, no need to add to 5.2 changelog.
4304 - grlib,grspw: SET_PACKET_SIZE could use old DMA address¶
Id |
4304 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T13:37:08.000Z |
Updated |
2021-03-09T13:23:36.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
When the DMA table has been allocated dynamically, the IOCTL_SET_PACKETSIZE will trigger an issue where pDev->rx and pDev->tx are not updated with the new DMA tables base address. Instead the old pointers are used.
There is no point in reallocting the DMA tables because there is no configuration option to it.
Author: Trac Migrate
2021-03-07T13:37:33.000Z
Original author: daniel
Summary changed from leon,grspw: SET_PACKET_SIZE could use old DMA address to grlib,grspw: SET_PACKET_SIZE could use old DMA address
Author: Trac Migrate
2021-03-07T15:56:36.000Z
Original author: daniel
In [changeset:”84fb340ac464c6aba2c5b4f3352c1c8f60466d47/rtems” 84fb340/rtems]:
leon,grspw: fix for SET_PACKET_SIZE When the DMA table has been allocated dynamically, the IOCTL_SET_PACKETSIZE will trigger an issue where pDev->rx and pDev->tx are not updated with the new DMA tables base address. Instead the old pointers are used. There is no point in reallocting the DMA tables because there is no configuration option to it. Therefore the DMA tables allocation is moved to a separate function never called from SET_PACKETSIZE. Update #4304.
Author: Trac Migrate
2021-03-09T13:23:36.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
4303 - grlib,gr1553bc: better check of the DMA area address alignment¶
Id |
4303 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-03-07T13:26:40.000Z |
Updated |
2021-03-09T13:22:56.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: daniel
GR1553 BC hardware truncates unaligned DMA memory addresses. Need to check input and the final DMA address and fail if unaligned address.
Author: Trac Migrate
2021-03-07T15:56:33.000Z
Original author: daniel
In [changeset:”8004ffb6491872529da5453942bd0a04822a5f46/rtems” 8004ffb/rtems]:
leon,gr1553b: Only align allocated memory. Verify alignment of memory. Update #4303.
Author: Trac Migrate
2021-03-09T13:22:56.000Z
Original author: daniel
Milestone changed from %”6.1” to %”5.2”
Resolution set to ~”fixed”
Status changed from assigned to closed
Minor fix, no need to add to 5.2 Changelog.
4263 - Activate ehci_pci in rtems-libbsd¶
Id |
4263 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-02-22T10:29:08.000Z |
Updated |
2021-03-09T10:38:24.000Z |
Milestone |
5.2 |
Labels |
libbsd, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
0 |
Original author: GabrielMoyano
Import ehci_pci from freebsd-org using freebsd-to-rtems.py
Author: Trac Migrate
2021-03-09T10:37:15.000Z
Original author: GabrielMoyano
Owner set to soja
Status changed from new to accepted
Author: Trac Migrate
2021-03-09T10:38:24.000Z
Original author: GabrielMoyano
Resolution set to ~”fixed”
Status changed from accepted to closed
4236 - bsps/zynq: termios not working correctly for stdin¶
Id |
4236 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-02-09T12:22:15.000Z |
Updated |
2021-03-09T08:30:38.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Original author: soja
The termios test application does not work correctly for Zynq based BSPs. Also scanf and similar functions reading from stdin do return immediately and do not block as expected.
The console driver has been fixed in master. This should be backported to 5.x.
Author: Trac Migrate
2021-03-09T08:30:07.000Z
Original author: soja
In [changeset:”2f323700b9cde52603e5773611bdc8932c109f58/rtems” 2f32370/rtems]:
zynq-uart: Fix set_attributes implementation The zynq-uart set_attributes implementation was configured to always return false which causes spconsole01 to fail. This restores the disabled implementation which sets the baud rate registers appropriately and allows spconsole01 to pass. This also expands the set_attributes functionality to allow setting of the stop bits, character width, and parity. Updates #4236
Author: Trac Migrate
2021-03-09T08:30:38.000Z
Original author: soja
Owner set to Jan Sommer <jan.sommer@dlr.de>
Resolution set to ~”fixed”
Status changed from new to closed
In [changeset:”645dbc5fccd8b73e12ca17ab35962fe751854913/rtems” 645dbc5/rtems]:
bsps/shared: Allow setting baud rate for zynq uart Closes #4236
4266 - motorola_powerpc bootloader images not linking correctly¶
Id |
4266 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2021-02-24T05:52:30.000Z |
Updated |
2021-03-03T19:58:04.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
The change to support code and data sections has broken creating net boot images for the MVME 2700 (mvme2307) BSP. The linker command file ppcboot.lds does not handle the per function text sections.
Author: Trac Migrate
2021-02-24T21:50:13.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”3824960f24304eec051fdc59121ba9ba8a8346da/rtems” 3824960/rtems]:
powerpc/motorola_power: Link all text sections into the executable image - The change to building all code with code and data sections means we have a section per function. Make sure all functions are placed in the text section. Closes #4266
Author: Chris Johns
2021-02-26T04:19:33.000Z
Resolution ~”fixed” deleted
Status changed from closed to reopened
The change does not resolve the issue. I am not sure what happened in my testing.
The bootloader linked executable has the
.text.*sections present. I am wondering if the Motorola debug monitor is not capable of loaded this type of ELF file. As a result the card information is not found and boot process fails. You can observe this by runningreadelf -aon thertems.img.elffile created when making the image file. This is the RTEMS 5 executable linked with the RTEMS 6 bootloader:Section Headers: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al [ 0] NULL 00000000 000000 000000 00 0 0 0 [ 1] .text PROGBITS 00000000 010000 00f145 00 AX 0 0 32 [ 2] .eh_frame PROGBITS 0000f148 01f148 0017e0 00 A 0 0 4 [ 3] .image PROGBITS 00010928 020928 017778 00 WA 0 0 1 [ 4] .reloc PROGBITS 000280a0 0380a0 0002bc 00 WA 0 0 4 [ 5] .handlers PROGBITS 0002835c 03835c 0003ac 00 WA 0 0 1 [ 6] .data PROGBITS 00028720 038720 003c80 00 WA 0 0 32 [ 7] .bss NOBITS 0002c3a0 03c3a0 001158 00 WA 0 0 32 [ 8] .gnu.attributes GNU_ATTRIBUTES 00000000 03c3a0 000010 00 0 0 1 [ 9] .symtab SYMTAB 00000000 03c3b0 0066c0 10 10 698 4 [10] .strtab STRTAB 00000000 042a70 00616c 00 0 0 1 [11] .shstrtab STRTAB 00000000 048bdc 00005e 00 0 0 1The RTEMS 6 executable has more code than the RTEMS 5. I tried a number of combinations in the linker command script but could not find a suitable result.
I have now looked into fixing the building of the bootloader in the RTEMS 5
automakebuild system and there are some fundamental issues present and I am yet to decide how this is to be resolved.The bootloader
Makefilehas a variableBOOTLOADER_CPU_FLAGS: https://git.rtems.org/rtems/tree/c/src/lib/libbsp/powerpc/motorola_powerpc/bootloader/Makefile.am?h=5#n22 This is empty becauseCPU_FLAGSis not exported into this file:$ grep CPU_FLAGS powerpc-rtems5/c/mvme2307/lib/libbsp/powerpc/motorola_powerpc/bootloader/Makefile $The CPU flags are being provided the globally set
CFLAGSand this includes the text and data segment flags which is causing the problem. Adding:CFLAGS = CPPFLAGS = CCASFLAGS =Results in no valid CPU flags being set.
I am reluctant to add exporting the CPU flags to a high level in the build process because it will be seen by all BSPs and it is very difficult to know if there are possible side effects in another BSP.
I cannot only see a couple of solutions:
Remove the problem flags from the build
Find a way to include the config with the flags
Author: Chris Johns
2021-02-26T07:14:46.000Z
I have isolated the issue to the building of
zlib.cby the RTEMS 5 gcc. If I build just this file with the RTEMS 6 gcc the board boots.
Author: Chris Johns
2021-02-26T19:04:37.000Z
Comparing the
zlib.oELF sections for RTEMS 5 and 6 the.bsssize is almost0:Section Headers: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al [ 0] NULL 00000000 000000 000000 00 0 0 0 [ 1] .text PROGBITS 00000000 000034 003cb8 00 AX 0 0 4 [ 2] .rela.text RELA 00000000 004890 000444 0c I 16 1 4 [ 3] .data PROGBITS 00000000 003cec 00027c 00 WA 0 0 4 [ 4] .bss NOBITS 00000000 003f68 000008 00 WA 0 0 4and
zlibhas a set of tables it generates. The RTEMS 6 or gcc-10 ELF sections are:Section Headers: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al [ 0] NULL 00000000 000000 000000 00 0 0 0 [ 1] .text PROGBITS 00000000 000034 003c7c 00 AX 0 0 4 [ 2] .rela.text RELA 00000000 005014 000444 0c I 18 1 4 [ 3] .data PROGBITS 00000000 003cb0 00027c 00 WA 0 0 4 [ 4] .bss NOBITS 00000000 003f2c 0010a8 00 WA 0 0 4An inspection of the generated assember shows the data being allocated using the
.commdirectory placing the data in thecommonsection. Adding-f-no-commonto the building of the bootloader has it working.
Author: Chris Johns
2021-02-26T19:06:17.000Z
GCC 10 defaults to
-fno-common…
Author: Chris Johns
2021-02-26T19:21:14.000Z
The preferred solution is to add
*(COMMON)to the.bsssection in the linker command file used to link the boot loader. This will work with any gcc version and default they decide on.
Author: Trac Migrate
2021-02-28T01:28:36.000Z
Resolution set to ~”fixed”
Status changed from reopened to closed
In [changeset:”d1bab986ca364cc691f332d914d8bb0e4142886b/rtems” d1bab98/rtems]:
powerpc/motorola_power: Place any common data in the .bss section - It seems the compiler how defaults to -fcommon and this means some uninitialised data is ignored. Closes #4266
Author: Trac Migrate
2021-02-28T03:37:18.000Z
In [changeset:”75fb7a0ee5d76f392e3b38bb920969dffef6e86c/rtems” 75fb7a0e/rtems]:
powerpc/motorola_power: Link all text sections into the executable image - The change to building all code with code and data sections means we have a section per function. Make sure all functions are placed in the text section. Closes #4266
Author: Trac Migrate
2021-02-28T03:37:22.000Z
In [changeset:”96918affc34e50cccdf30b1c8e0fe0e73d122d78/rtems” 96918af/rtems]:
powerpc/motorola_power: Place any common data in the .bss section - It seems the compiler how defaults to -fcommon and this means some uninitialised data is ignored. Closes #4266
Author: Trac Migrate
2021-03-03T19:58:04.000Z
Maybe worthwhile looking into the –orphan-handling=MODE argument for ld in newer binutils? At least “warn” if not “error” seems like it would have made this situation more obvious.
https://sourceware.org/binutils/docs/ld/Orphan-Sections.html
4247 - Change motorola_powerpc bsp to support irq-generic (cloned)¶
Id |
4247 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2021-02-16T04:18:24.000Z |
Updated |
2021-02-16T20:30:07.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
1 |
Cloned from #4238:
Update the motorola_powerpc to support irq-generic moving the IRQ management to the IRQ server. This enables libbsd support for interrupts.
Author: Trac Migrate
2021-02-16T20:30:07.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”2f56b7375a36039750eee0ffbc7a5bd0e4382075/rtems” 2f56b737/rtems]:
Update motorola_power to irq-generic interrupt management - Add support to the BSP to enable irq-generic management - Update the powerpc shared irq code to support irq-generic. This is an opt in option for existing powerpc bsps. This change should be simpler now - Fix a number of issues in ISA IRQ controller handling by porting fixes from the i386 (PC) BSP Closes #4247 Closes #4248
4249 - fix mkimage.py script type processing¶
Id |
4249 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2021-02-16T05:21:34.000Z |
Updated |
2021-02-16T05:24:00.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool, version::5 |
Link |
|
Merges |
0 |
The explaination is taken from André on the user list:
Hello,
after some digging I think I found the problem and at least a workaround.
As a disclaimer, I do not know if this really counts as a general fix. I have not invested enough time to dig through the original mkimage U-Boot source to figure this out. But I have attached my workaround patch if anyone might face the same problems.
The source of the problem are eight bytes between the header and the actual input file which are missing when using mkimage.py. Also the input size and input crc are wrong which is a result of the missing bytes.
These eight bytes always reflect the actual size of the input file (first four bytes) with four bytes zeros following. Within the original mkimage tool these eight bytes are considered part of the input file section in the output file. Therefore the calculated input size is eight bytes higher and the input crc differs.
As a workaround the mkimage.py script will add these eight bytes to the output file and the input crc calculation and adjusts the input size. This only happens when the type script was selected.
Best regards André
https://lists.rtems.org/pipermail/users/2021-January/068060.html https://lists.rtems.org/pipermail/users/2021-February/068140.html https://lists.rtems.org/pipermail/devel/2021-February/064491.html
Author: Trac Migrate
2021-02-16T05:24:00.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”e621fd98e78c96b281211e666dedb5f3e81e6050/rtems-tools” e621fd9/rtems-tools]:
misc: tools: fix mkimage.py script type processing Closes #4249
4233 - MVME 2600/2700 has no console output (cloned)¶
Id |
4233 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2021-02-07T02:58:12.000Z |
Updated |
2021-02-10T06:36:01.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Cloned from #4231:
A single character is output then nothing further. Tests output using the printk but spconsole01 fails.
It seems there is a problem with the UART driver interrupts.
Author: Trac Migrate
2021-02-10T06:36:01.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”6d9843e189d584a3a18cb4f8fd96f5016175514d/rtems” 6d9843e/rtems]:
powerpc/shared: ISA bus bridge fails to enable the openpic irq - The call to enable the openpic irq for the ISA bridge fails because the IRQ used is offset by the ISA bus signals and the openpic call expects an IRQ relative to its signals. - Add the MVME 2600/2700 to the list of boards with an ISA bridge. Closes #4233
4224 - Missing “extern” in RTEMS_LINKER_ROSET_ITEM_ORDERED_DECLARE() (cloned)¶
Id |
4224 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2021-01-25T05:43:27.000Z |
Updated |
2021-01-25T05:48:17.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Original author: sebastian.huber
Cloned from #4223:
The fix for #3865 contains a typo. In RTEMS_LINKER_ROSET_ITEM_ORDERED_DECLARE() there is a missing “extern”.
Author: Trac Migrate
2021-01-25T05:48:17.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”5ae7ec94773478b5d57bf20592d94deb789d372b/rtems” 5ae7ec9/rtems]:
Fix RTEMS_LINKER_ROSET_ITEM_ORDERED_DECLARE() Add "extern" similar to RTEMS_LINKER_RWSET_ITEM_ORDERED_DECLARE(). Close #4224.
4174 - devctl.h does not compile from C++¶
Id |
4174 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Joel Sherrill |
Created |
2020-11-09T21:34:40.000Z |
Updated |
2020-12-10T21:08:18.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::newlib, version::5 |
Link |
|
Merges |
0 |
The closing boilerplate of the C++ extern C wrapper is out of order with another #endif and the resulting code does not compile.
The attached patch addresses this but it needs to be merged to newlib and the RSB updated before this ticket closed.
Patch to newlib is on #4193.
Author: Joel Sherrill
2020-11-09T21:35:20.000Z
Attachment 0001-libc-include-newlib.h-Fix-C-compilation-issue.patch added
Rework closing endif’s to compile on C++
Author: Joel Sherrill
2020-11-16T14:19:02.000Z
Fixed pushed to newlib.
https://sourceware.org/git/?p=newlib-cygwin.git;a=commit;h=302b82afee423fcb5a447a222e2b771ef9c06ee0
Author: Joel Sherrill
2020-11-17T15:44:02.000Z
Owner set to sebastian.huber
Assigning to Sebastian since he is bumping the RSB recipes and can close when that is done.
Author: Joel Sherrill
2020-12-08T17:47:04.000Z
Description changed
The closing boilerplate of the C++ extern C wrapper is out of order with another #endif and the resulting code does not compile. The attached patch addresses this but it needs to be merged to newlib and the RSB updated before this ticket closed. + + Patch to newlib is on #4193.
Owner set to @joel
Author: Trac Migrate
2020-12-10T21:08:18.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”803d42cda7b3360128126bc2748b5d2b452a8973/rtems-source-builder” 803d42c/rtems-source-builder]:
Add patch to newlib for devctl.h to compile with C++ Closes #4174.
4190 - Back port rtems_interrupt_server_create() improvements¶
Id |
4190 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-11-25T07:31:46.000Z |
Updated |
2020-11-25T07:33:28.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Original author: sebastian.huber
Back port 99c73303deb09ad66d4cc1c89961f62e4e618938 to RTEMS 5 to fix “fman” network interface driver issues in libbsd.
Author: Trac Migrate
2020-11-25T07:33:28.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”dedc3e1d49eaf5b4f5a9180c075ad5793532c52f/rtems” dedc3e1d/rtems]:
rtems: Improve rtems_interrupt_server_create() Also start interrupt server tasks on processors which do not have a scheduler. Applications may dynamically manage processors using rtems_scheduler_remove_processor() and rtems_scheduler_add_processor(). Close #4190.
4189 - rtems_interrupt_server_delete() does not destroy the ISR lock of the server control (cloned)¶
Id |
4189 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-11-25T07:24:37.000Z |
Updated |
2020-11-25T07:33:25.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Original author: sebastian.huber
Cloned from #4158:
This leads to memory corruption if RTEMS_PROFILING and RTEMS_SMP is enabled.
Author: Trac Migrate
2020-11-25T07:33:25.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”1dbdf94e67da026238ee051f4c438a93e9a76412/rtems” 1dbdf94e/rtems]:
bsps: Fix rtems_interrupt_server_delete() The ISR lock must be destroyed to prevent memory corruption if RTEMS_PROFILING and RTEMS_SMP is enabled. Close #4189.
4169 - Link problem of C++ tests when using libpci in BSP¶
Id |
4169 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-10-29T13:19:02.000Z |
Updated |
2020-10-30T02:22:13.000Z |
Milestone |
5.2 |
Labels |
library, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Original author: soja
When using libpci in a custom BSP we experienced linking problems for C++ test (e.g. spcxx01).
The reason is the missing extern C include guards for confdefs/libpci.h. Therefore, the reference to pci_config_lib_init is mangled.
A patch fixing this problem is provided here: https://lists.rtems.org/pipermail/devel/2020-October/062981.html
Author: Trac Migrate
2020-10-30T02:22:13.000Z
Original author: soja
Owner set to Jan Sommer <jan.sommer@dlr.de>
Resolution set to ~”fixed”
Status changed from new to closed
In [changeset:”f84c4a5b8107867a78326cca754c5278df768bb8/rtems” f84c4a5/rtems]:
confdefs: Add extern C guards to libpci.h Closes #4169
4165 - Fix NVMe disk synchronization and media block handling (cloned)¶
Id |
4165 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-10-27T05:24:30.000Z |
Updated |
2020-10-27T05:27:52.000Z |
Milestone |
5.2 |
Labels |
libbsd, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
Original author: sebastian.huber
Cloned from #4164.
Author: Trac Migrate
2020-10-27T05:27:52.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
4149 - RFS bit map search buffer overflow¶
Id |
4149 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Chris Johns |
Created |
2020-10-15T06:13:07.000Z |
Updated |
2020-10-16T23:55:53.000Z |
Milestone |
5.2 |
Labels |
filesystem::rfs, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Cloned from #4148:
The bit search create writes past the end of its buffer. See:
https://lists.rtems.org/pipermail/devel/2020-October/062701.html
Author: Trac Migrate
2020-10-16T23:55:53.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”7021c014640a24248b2aa7245a1e6248bb5c832a/rtems” 7021c014/rtems]:
libfs/rfs: Check search bit map end on last bit - Do not write past the last location of the search bit map whe nit is being created. Closes #4149
4114 - Cortex-A9 MPCore based BSPs should include the workaround for Errata 794072 and 845369¶
Id |
4114 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-10-02T09:34:40.000Z |
Updated |
2020-10-16T04:48:30.000Z |
Milestone |
5.2 |
Labels |
arch:arm, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
1 |
Original author: sebastian.huber
The workaround may be already set up by the bootloader. Not having the workaround applied may lead to system crashes, so make sure the BSP does it during system startup.
Author: Trac Migrate
2020-10-05T06:46:34.000Z
Original author: sebastian.huber
Original author: sebastian.huber
Description changed
- The workaround may be already set up by the bootloader. Not having the workaround applied may lead to system crashes, so make sure the BSP sets it also during system startup. ? --- ----- + The workaround may be already set up by the bootloader. Not having the workaround applied may lead to system crashes, so make sure the BSP does it during system startup. ? +++
Summary changed from Cortex-A9 MPCore based BSPs should include the workaround for Errata 845369 to Cortex-A9 MPCore based BSPs should include the workaround for Errata 794072 and 845369
Author: Trac Migrate
2020-10-16T04:48:26.000Z
Original author: sebastian.huber
In [changeset:”3d7da43562d83faf93f9a3827408d2a13a3658d3/rtems” 3d7da435/rtems]:
bsps/arm: Workaround for Errata 845369 Add a workaround for Cortex-A9 Errata 845369: Under Very Rare Timing Circumstances Transition into Streaming Mode Might Create Data Corruption. Update #4114.
Author: Trac Migrate
2020-10-16T04:48:30.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”e71e271ce15504559f3bda019f5adc9ddb4fd0bf/rtems” e71e271/rtems]:
bsps/arm: Add workaround for Errata 794072 Add a workaround for Cortex-A9 Errata 845369: A short loop including a DMB instruction might cause a denial of service on another which executes a CP15 broadcast operation. Close #4114.
4099 - Enhance rtems-bsps to print canonical names of bsps¶
Id |
4099 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-09-28T22:43:16.000Z |
Updated |
2020-09-29T12:59:41.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool, version::5 |
Link |
|
Merges |
1 |
Original author: rlong
For some purposes it is nice to have a list of the BSPs in the form ARCHITECTURE/BSP, which can be fed into other scripts.
Author: Trac Migrate
2020-09-28T22:52:00.000Z
Original author: rlong
Attachment 0001-rtems-bsps-add-ability-to-print-architecture-bsp-lis.patch added
Patch to add printing of architecture/bsps
Author: Trac Migrate
2020-09-29T05:11:25.000Z
Original author: rlong
Owner set to Ryan Long <ryan.long@oarcorp.com>
Resolution set to ~”fixed”
Status changed from new to closed
In [changeset:”0805930d0c1ee11fc74c6028d93a3aaff1973e02/rtems” 0805930/rtems]:
rtems-bsps: add ability to print architecture/bsp list Closes #4099.
Author: Trac Migrate
2020-09-29T12:59:41.000Z
Original author: rlong
In [changeset:”fdbe9b75994e90c71ee38212ec2d6867c9fa9b01/rtems” fdbe9b7/rtems]:
rtems-bsps: add ability to print architecture/bsp list Closes #4099.
4082 - License files missing on 5-freebsd-12 branch¶
Id |
4082 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-09-17T09:23:31.000Z |
Updated |
2020-09-28T11:51:48.000Z |
Milestone |
5.2 |
Labels |
priority::low, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
0 |
Original author: Christian Mauderer
The commits
https://git.rtems.org/rtems-libbsd/commit/libbsd.py?id=c64a1ebaf9c8871f3f72b8754097e272043012d6 https://git.rtems.org/rtems-libbsd/commit/libbsd.py?id=e2fc9082816452844a53dc97f862375b74d9523b https://git.rtems.org/rtems-libbsd/commit/libbsd.py?id=589f43d6af2302623229760fb0f37378241b8bfe
haven’t been added to the 5-freebsd-12 branch. Therefore the License files are missing.
Author: Trac Migrate
2020-09-28T11:51:26.000Z
Original author: Christian Mauderer
Fixed with patches 640b2a03b87481bd1a3c80d6e33a2a8a13868734, 5b3ee7027991fbf290e982a4eaffe7ea7ad21ae6, 9dd0bc27e3338bad08eaaf52d03265d2e7b9b4f7 in libbsd.
Author: Trac Migrate
2020-09-28T11:51:48.000Z
Original author: Christian Mauderer
Resolution set to ~”fixed”
Status changed from assigned to closed
4094 - RSB: pkgconfig.py uses python2 specific “unicode” keyword¶
Id |
4094 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-09-24T23:16:45.000Z |
Updated |
2020-09-26T01:01:38.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::rtems-source-builder, version::5 |
Link |
|
Merges |
0 |
Original author: stephenclark
https://git.rtems.org/rtems-source-builder/tree/source-builder/sb/pkgconfig.py#n218 uses the unicode keyword which is python2 specific. This problem exists on both the 5 branch and the master.
Author: Trac Migrate
2020-09-25T21:47:24.000Z
Original author: stephenclark
Attachment 0001-pkgconfig.py-Removed-use-of-unicode-keyword-for-pyth.patch added
Patch for 5 branch
Author: Trac Migrate
2020-09-26T01:00:05.000Z
Original author: stephenclark
Owner set to Stephen Clark <stephen.clark@oarcorp.com>
Resolution set to ~”fixed”
Status changed from new to closed
In [changeset:”e32e184d69b3a54059c9bf9a72a037eb7f9de6db/rtems-source-builder” e32e184/rtems-source-builder]:
pkgconfig.py: Removed use of "unicode" keyword for python3 compatibility Closes #4094.
Author: Trac Migrate
2020-09-26T01:01:38.000Z
Original author: stephenclark
In [changeset:”ed5030bc24dbfdfac52074ed78cf4231bf1f353d/rtems-source-builder” ed5030b/rtems-source-builder]:
pkgconfig.py: Removed use of "unicode" keyword for python3 compatibility Closes #4094.
4092 - bsps/pc386: Add missing license header¶
Id |
4092 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Trac Migrate |
Created |
2020-09-23T13:19:03.000Z |
Updated |
2020-09-23T13:30:01.000Z |
Milestone |
5.2 |
Labels |
bsp, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
bspsmp.c is missing a licence header.
Author: Joel Sherrill
2020-09-23T13:30:01.000Z
Resolution set to ~”fixed”
Status changed from new to closed
In [changeset:”1f77518fcab14b14868849c0f166b43136ff974b/rtems” 1f77518/rtems]:
bsps/pc386: Add missing license header Closes #4092.
2830 - throwing std::runtime on PC BSP fails.¶
Id |
2830 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Trac Migrate |
Created |
2016-12-02T05:10:06.000Z |
Updated |
2020-09-21T21:14:32.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, tool::gcc, version::5 |
Link |
|
Merges |
0 |
Throwing a std::runtime() exception locks up.
The lock up is in the exception clean up handler where the exception object is destructed. The destructor loops distructing the std::string object. The path ends up in libstdc++-v3/include/ext/atomicity.h line 48 or __exchange_and_add.
At a guess it would seem like the C++ atomics on i386 is broken or fragile.
UPDATE: This was broken when gcc i386 eliminated -mcpu in favor of -march/-mtune. The multilibs were built with -mtune and not -march.
Author: Chris Johns
2016-12-02T05:10:43.000Z
Attachment cdtest-throw-std_runtime.diff added
Patch to the cdtest sample that shows the problem
Author: Chris Johns
2016-12-02T05:12:22.000Z
Description changed
- Throwing a `std::runtime()` exception lock up. + Throwing a `std::runtime()` exception locks up. ? + - The lock up is in the exception clean up handler where the exception object is destructed. The destructor loop distructing the std::string object. The path ends up in libstdc++-v3/include/ext/atomicity.h line 48 or __exchange_and_add. + The lock up is in the exception clean up handler where the exception object is destructed. The destructor loops distructing the std::string object. The path ends up in libstdc++-v3/include/ext/atomicity.h line 48 or __exchange_and_add. ? + + At a guess it would seem like the C++ atomics on i386 is broken or fragile.
Author: Trac Migrate
2016-12-09T07:02:30.000Z
Works at least on SPARC and ARM. On which BSP fails this?
Author: Chris Johns
2016-12-09T11:24:02.000Z
Replying to sebastian.huber:
Works at least on SPARC and ARM. On which BSP fails this?
i386/pc686 tested on qemu with a core2duo cpu.
Author: Trac Migrate
2017-02-15T14:20:42.000Z
Milestone changed from %”4.12” to %”Indefinite”
Owner set to Needs Funding
Status changed from new to assigned
Author: Trac Migrate
2020-09-10T20:24:40.000Z
I’m observing a hang with RTEMS 5.1 with i386/pc686 which may be this issue, though it does not looks to me to be in an exception class dtor. This is a test case I’m running in QEMU w/ 1 virtual CPU.
It’s on exit from an catch(…){ block. The actual hang appears to be a tight loop in the
__atomic_fetch_add_4builtin. Specifically, these three instructions.=> 0x3f1780 <libat_fetch_add_4>: mov $0x5,%eax 0x3f1785 <libat_fetch_add_4+5>: mov %eax,0xc(%esp) 0x3f1789 <libat_fetch_add_4+9>: jmp 0x3f1780 <libat_fetch_add_4>The stack trace is:
(gdb) bt #0 libat_fetch_add_4 (mptr=0x75d7bc, opval=4294967295, smodel=5) at ../../../../gcc-7.5.0/libatomic/fop_n.c:44 #1 0x003b07fc in __gnu_cxx::__exchange_and_add (__val=-1, __mem=0x75d7bc) at /home/mdavidsaver/source/rtems/rtems-source-builder-5.1/rtems/build/i386-rtems5-gcc-7.5.0-newlib-7947581-x86_64-linux-gnu-1/build/i386-rtems5/mpentiumpro/libstdc++-v3/include/ext/atomicity.h:49 #2 __gnu_cxx::__exchange_and_add_dispatch (__val=-1, __mem=0x75d7bc) at /home/mdavidsaver/source/rtems/rtems-source-builder-5.1/rtems/build/i386-rtems5-gcc-7.5.0-newlib-7947581-x86_64-linux-gnu-1/build/i386-rtems5/mpentiumpro/libstdc++-v3/include/ext/atomicity.h:82 #3 __gnu_cxx::__eh_atomic_dec (__count=0x75d7bc) at ../../../../../gcc-7.5.0/libstdc++-v3/libsupc++/eh_atomics.h:72 #4 __gxx_exception_cleanup (code=_URC_FOREIGN_EXCEPTION_CAUGHT, exc=0x75d7fc) at ../../../../../gcc-7.5.0/libstdc++-v3/libsupc++/eh_throw.cc:46 #5 0x003ad9cb in _Unwind_DeleteException (exc=0x75d7fc) at ../../../../gcc-7.5.0/libgcc/unwind.inc:271 #6 0x003af8d0 in __cxxabiv1::__cxa_end_catch () at ../../../../../gcc-7.5.0/libstdc++-v3/libsupc++/eh_catch.cc:125 #7 0x001012fd in epicsTimeTest () at ../epicsTimeTest.cpp:116
Author: Trac Migrate
2020-09-11T04:51:16.000Z
If this BSP uses libatomic to load a 32-bit value, then it uses an obsolete instruction set.
Author: Trac Migrate
2020-09-11T16:56:14.000Z
I’ve not come across ‘libatomic’ before. I guess this is some compatibility glue for older x86?
From some playing around, it looks like the toolchain gcc is defaulting to ‘-march=i386’ if no other option is provided. Maybe not surprising given that the toolchain name is ‘i386-rtems5’. ‘<prefix>/make/custom/pc686.cfg’ has ‘-mtune=pentiumpro -march=pentium’. Passing this to a short test seems to result in the intrinsic actually being used. So I guess the RTEMS kernel config/build is ok?
Starting from the linker map of epicsTimeTest, I see that the symbol
__atomic_fetch_add_4(aka. ‘libat_fetch_add_4’) is undefined in<prefix>/lib/gcc/i386-rtems5/7.5.0/mpentiumpro/libstdc++.a. So I guess this means that the (multilib?) build of libstdc++ is not being done correctly?My knowledge of GCC internals doesn’t extend beyond ./configure arguments. So I don’t know where to look next.
Author: Joel Sherrill
2020-09-11T22:07:20.000Z
Could someone please try this test case with -march=i486 as the compiler selection?
I think we need to move the base uniprocessor x86 CPU model up from vanilla i386 w/FPU but what the new floor needs to be is TBD. If I understand things correctly, i486 is the minimum with any atomic instructions but you have to get into the pentium II era to get the earliest SMP support.
I’m not sure if going beyond i486 is needed for uniprocessor but that may be sufficient. For SMP, you probably need to go to at least pentium II. On Qemu, I used core2duo long ago to test SMP.
If we move the floor to greater than or equal to Pentium, there is more opportunity to remove a small bit of code. But I’d like to know the bare technical minimums first.
So what is the lowest architecture (-march=XXX) that appears to solve this for you?
Author: Trac Migrate
2020-09-11T23:18:34.000Z
I may have answered part of my question with a lucky grep of the gcc source. I found ‘gcc/config/i386/t-rtems’ which seems to show that the different multilib versions are built with ‘-mtune=…’, and presumably defaulting to ‘-march=i386’. RTEMS itself in ‘<prefix>/make/custom/pc686.cfg’ has ‘-march=pentium’. What is the logic here?
MULTILIB_OPTIONS = mtune=i486/mtune=pentium/mtune=pentiumpro msoft-float MULTILIB_DIRNAMES= m486 mpentium mpentiumpro soft-float MULTILIB_MATCHES = msoft-float=mno-80387 MULTILIB_MATCHES += mtune?pentium=mtune?k6 mtune?pentiumpro=mtune?athlon MULTILIB_EXCEPTIONS = \\ mtune=pentium/*msoft-float* \\ mtune=pentiumpro/*msoft-float*
Author: Trac Migrate
2020-09-12T07:47:29.000Z
We have two different issues:
The i386 BSPs use probably obsolete instruction sets which lead to the use of libatomic.
If libatomic is used, then there is some broken behaviour.
The libatomic seems to work fine on other architectures, e.g. it is also used by the sparc/erc32 BSP. Here the cdtest.exe test program runs successfully and executes a similar context:
Breakpoint 2, libat_fetch_add_4 (mptr=0x203d798, opval=4294967295, smodel=4) at ../../../gnu-mirror-gcc-c72a1b6/libatomic/fop_n.c:164 164 ../../../gnu-mirror-gcc-c72a1b6/libatomic/fop_n.c: No such file or directory. (gdb) bt #0 libat_fetch_add_4 (mptr=0x203d798, opval=4294967295, smodel=4) at ../../../gnu-mirror-gcc-c72a1b6/libatomic/fop_n.c:164 #1 0x0200eda0 in __gnu_cxx::__exchange_and_add (__val=-1, __mem=0x203d798) at /home/EB/sebastian_h/src/rtems-source-builder/rtems/build/sparc-rtems6-gcc-c72a1b6-newlib-ece49e4-x86_64-linux-gnu-1/build/sparc-rtems6/libstdc++-v3/include/ext/atomicity.h:84 #2 __gnu_cxx::__exchange_and_add_dispatch (__val=-1, __mem=0x203d798) at /home/EB/sebastian_h/src/rtems-source-builder/rtems/build/sparc-rtems6-gcc-c72a1b6-newlib-ece49e4-x86_64-linux-gnu-1/build/sparc-rtems6/libstdc++-v3/include/ext/atomicity.h:84 #3 __gnu_cxx::__eh_atomic_dec (__count=0x203d798) at ../../../../gnu-mirror-gcc-c72a1b6/libstdc++-v3/libsupc++/eh_atomics.h:72 #4 __gxx_exception_cleanup (code=_URC_FOREIGN_EXCEPTION_CAUGHT, exc=0x203d7d0) at ../../../../gnu-mirror-gcc-c72a1b6/libstdc++-v3/libsupc++/eh_throw.cc:46 #5 0x0201e584 in _Unwind_DeleteException (exc=0x203d7d0) at ../../../gnu-mirror-gcc-c72a1b6/libgcc/unwind.inc:283 #6 0x02001a44 in foo_function () at ../../../testsuites/samples/cdtest/main.cc:198 #7 main_task () at ../../../testsuites/samples/cdtest/main.cc:212 #8 0x02006b8c in _Thread_Entry_adaptor_numeric (executing=0x2032ae8 <_RTEMS_tasks_Objects>) at ../../../cpukit/score/src/threadentryadaptornumeric.c:25 #9 0x02006c64 in _Thread_Handler () at ../../../cpukit/score/src/threadhandler.c:143 #10 0x02006c04 in _Thread_Handler () at ../../../cpukit/score/src/threadhandler.c:87
Author: Trac Migrate
2020-09-12T10:29:03.000Z
Replying to Michael Davidsaver:
It’s on exit from an catch(…){ block. The actual hang appears to be a tight loop in the
__atomic_fetch_add_4builtin. Specifically, these three instructions. {{{ => 0x3f1780 <libat_fetch_add_4>: mov $0x5,%eax 0x3f1785 <libat_fetch_add_4+5>: mov %eax,0xc(%esp) 0x3f1789 <libat_fetch_add_4+9>: jmp 0x3f1780 <libat_fetch_add_4> }}}From this code it is clear, that this is a libatomic configuration issue on i386. We have a recursive call here. We probably use instruction sets which are not really tested these days by someone else.
Author: Joel Sherrill
2020-09-12T14:54:58.000Z
The bug goes back to when gcc replaced -mcpu= with -march= and -mtune=. We used to generated code specifically compatible with and optimized for a CPU model. -march is now the compatibility level flag and -mtune is an optimization indication. We are generating i386 compatible code which is tuned based on say an i686 instruction weighting.
The multilib -mtune needs to change to -march.
Since -march is the first x86 option described, it is at the top of this page in the GCC manual:
https://gcc.gnu.org/onlinedocs/gcc-7.5.0/gcc/x86-Options.html#x86-Options
A quick search browsing gcc/config/i386/t-* shows RTEMS seems to be the only i386 target building multilibs which are cpu model based. Others use m32/m64 or other things.
Author: Trac Migrate
2020-09-18T21:36:49.000Z
Is there agreement on a path forward for this issue? Is it as simple as replacing ‘mtune’ with ‘march’ in gcc/config/i386/t-rtems ? If so, who will do/test this? This change seems simple enough that I would just try it myself, but I’m not sure where/how to add a patch in the RSB recipies.
Author: Joel Sherrill
2020-09-18T21:53:00.000Z
I think that’s the extent of the source changes which we think will resolve the issue. Someone may point to documentation but it is Friday and I am going to point to an example of adding a patch and talk you through it. This assumes the 5 branch because we won’t get a patch merged into gcc 7. We can address RTEMS master after 5 is fixed. The patch for gcc should be the same. We just have more latitude to merge it to gcc master and newer release branches.
How to generate a patch: https://devel.rtems.org/wiki/Developer/Coding/GenerateAPatch which should also be in the Software Engineering Guide.
The easiest example I saw was in rtems/config/5/rtems-lm32.bset which adds a gdb patch only for lm32 builds. You would be adding a gcc patch to rtems/config/5/rtems-i386.bset.
For merging, a patch needs an Internet home (attaching to a ticket gives you a URL) but for testing, you can just drop the diff into the patches subdirectory config/rtems/patches. The RSB will see it there and not try to fetch it. But you need an sha checksum.
After that, it is build as normal for testing purpose. If this gives you a toolset that works, we can address changing the URL. But attaching it to this ticket and getting the URL for the “raw” attachment should work just fine.
Author: Trac Migrate
2020-09-19T14:46:42.000Z
Attachment gcc-7.5.0-i386march-1.diff added
Change gcc multiarch config to use -march
Author: Trac Migrate
2020-09-19T14:53:28.000Z
Attachment 0001-patch-gcc-i386-multiarch.patch added
Patch RSB to patch GCC
Author: Trac Migrate
2020-09-19T16:47:42.000Z
I’ve attached patches for GCC and RSB.
A successful test build: https://github.com/mdavidsaver/rsb/runs/1138090148?check_suite_focus=true#step:5:563
Author: Joel Sherrill
2020-09-19T17:49:16.000Z
Congratulations! Can you confirm you tested code compiled with the resulting toolchain and it solved the problem?
Author: Trac Migrate
2020-09-19T19:44:55.000Z
Ha. That would be a good thing to mention would it not? Yes, the epicsTimeTest now passes, and the cdtest completes as well (with qemu*). I am having a problem with another test, but this is almost certainly a separate issue.
Author: Joel Sherrill
2020-09-21T19:43:58.000Z
Description changed
Throwing a `std::runtime()` exception locks up. The lock up is in the exception clean up handler where the exception object is destructed. The destructor loops distructing the std::string object. The path ends up in libstdc++-v3/include/ext/atomicity.h line 48 or __exchange_and_add. At a guess it would seem like the C++ atomics on i386 is broken or fragile. + + UPDATE: This was broken when gcc i386 eliminated -mcpu in favor of -march/-mtune. The multilibs were built with -mtune and not -march.
Milestone changed from %”Indefinite” to %”5.2”
Author: Trac Migrate
2020-09-21T20:37:37.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”ebc3abe40309f47f3d024c6f2636d9682863a9e6/rtems-source-builder” ebc3abe/rtems-source-builder]:
patch gcc i386 multiarch Add patch to change from mtune to march when building multilibs. The mtune argument tunes or optimizes for a specific CPU model but does not ensure the generated code is appropriate for the CPU model. Prior to this patch, i386 compatible code was always generated but tuned for later models. Closes #2830.
Author: Trac Migrate
2020-09-21T21:14:32.000Z
In [changeset:”1ea1c9cdc56313e33abf39fce23a2ddf308ff5b3/rtems-source-builder” 1ea1c9c/rtems-source-builder]:
patch gcc i386 multiarch Add patch to change from mtune to march when building multilibs. The mtune argument tunes or optimizes for a specific CPU model but does not ensure the generated code is appropriate for the CPU model. Prior to this patch, i386 compatible code was always generated but tuned for later models. This is the same fix as #2830 but applying to gcc 10. Updates #4084.
4075 - POSIX Compliance Guide Missing Some math.h Methods¶
Id |
4075 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Trac Migrate |
Created |
2020-09-11T21:30:39.000Z |
Updated |
2020-09-14T18:30:42.000Z |
Milestone |
5.2 |
Labels |
priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
The following methods are provided as macros on top of compiler built-ins. They have been missed by previous reviews but have long been supported. The POSIX Compliance Guide for the 5 branch and master needs to be updated.
fpclassify()
isfinite()
isgreater()
isgreaterequal()
isless()
islessequal()
islessgreater()
isnormal()
isunordered()
nexttowardf()
signbit()
Author: Trac Migrate
2020-09-14T18:29:42.000Z
Owner set to Joel Sherrill <joel@rtems.org>
Resolution set to ~”fixed”
Status changed from new to closed
In [changeset:”6559511813957a2fce62a15cf5925cbb5f6eb06f/rtems-docs” 6559511/rtems-docs]:
Add missing <math.h> methods implemented as macros on compiler builtins. These methods have long been provided and this change is needed on the 5.x branch and master. Closes #4075.
Author: Trac Migrate
2020-09-14T18:30:42.000Z
In [changeset:”5642fe5d4b9f3755483c27eef5b91ee5f3d232e9/rtems-docs” 5642fe5/rtems-docs]:
Add missing <math.h> methods implemented as macros on compiler builtins. These methods have long been provided and this change is needed on the 5.x branch and master. Closes #4075.
4073 - libbsd: Back port ifmcstat command¶
Id |
4073 |
State |
closed |
Type |
ISSUE |
Author |
Trac Migrate |
Assignee(s) |
Trac Migrate |
Created |
2020-09-10T11:27:43.000Z |
Updated |
2020-09-10T11:31:20.000Z |
Milestone |
5.2 |
Labels |
libbsd, priority::normal, resolution::fixed, tickettype::enhancement, version::5 |
Link |
|
Merges |
0 |
Original author: sebastian.huber
The ifmcstat command is a useful diagnostics command to track down issues with multicasts.
Author: Trac Migrate
2020-09-10T11:31:09.000Z
Original author: sebastian.huber
Integrated in 7f47f2784138109b8363804c2aecd3d83231ab0f.
Author: Trac Migrate
2020-09-10T11:31:20.000Z
Original author: sebastian.huber
Resolution set to ~”fixed”
Status changed from assigned to closed
3347 - tms570: Register Macro Redefinition¶
Id |
3347 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Trac Migrate |
Created |
2018-03-15T14:56:57.000Z |
Updated |
2018-10-15T06:45:51.000Z |
Milestone |
5.2 |
Labels |
arch:arm, priority::normal, resolution::fixed, tickettype::defect, version::5 |
Link |
|
Merges |
0 |
This looks like the same name was accidentally used. Without knowing the architecture, you can’t know what was intended:
/home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:164:0: warning: “TMS570_SYS1_CDDIS_VCLKAOFF_SET” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:163:0: warning: “TMS570_SYS1_CDDIS_VCLKAOFF_GET” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:162:0: warning: “TMS570_SYS1_CDDIS_VCLKAOFF” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:146:0: warning: “TMS570_SYS1_CSDISCLR_CLRCLKSR_OFF_SET” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:145:0: warning: “TMS570_SYS1_CSDISCLR_CLRCLKSR_OFF_GET” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:144:0: warning: “TMS570_SYS1_CSDISCLR_CLRCLKSR_OFF” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:134:0: warning: “TMS570_SYS1_CSDISSET_SETCLKSR_OFF_SET” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:133:0: warning: “TMS570_SYS1_CSDISSET_SETCLKSR_OFF_GET” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:132:0: warning: “TMS570_SYS1_CSDISSET_SETCLKSR_OFF” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:122:0: warning: “TMS570_SYS1_CSDIS_CLKSROFF_SET” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:121:0: warning: “TMS570_SYS1_CSDIS_CLKSROFF_GET” redefined /home/joel/rtems-work/rtems-testing/rtems/rtems/bsps/arm/tms570/include/bsp/ti_herc/reg_sys.h:120:0: warning: “TMS570_SYS1_CSDIS_CLKSROFF” redefined
Author: Joel Sherrill
2018-03-15T14:57:13.000Z
Owner set to ppisa
Status changed from new to assigned
Author: Joel Sherrill
2018-10-13T22:51:07.000Z
Milestone changed from %”5.1” to %”5.2”
Author: Trac Migrate
2018-10-15T06:45:51.000Z
Resolution set to ~”fixed”
Status changed from assigned to closed
In [changeset:”1822649ced3c77eb0eb96a5fda93cd9faa97db85/rtems” 1822649/rtems]:
bsp/tms570: Simple fix to resolve macro redefinitions. closes #3347