wiki:Release/5/5.1

5.1 (open)

Statistics

Total591
Fixed456
Invalid8
Works for me6
Duplicate9
Won't fix23

Distribution

defect

302 / 368

enhancement

159 / 172

task

34 / 40

infra

3 / 6

project

4 / 5

Summary

#1247
RTEMS does not implement locks needed by multithreaded newlib
#1394
scandir() fails due to MAXNAMELEN is incorrect
#1662
termios.c: semaphore not deleted, consequently resulting in failure of rtems_termios_open
#1747
Heap extend allows discontinuous memory regions.
#1971
Memory leak in tmpfile()
#2132
<rtems/score/basedefs.h> superfluously includes <limits.h>
#2133
<rtems/score/basedefs.h> superfluously includes <string.h>
#2135
times() and _times() are subject to integer overflows
#2173
Potential integer overflow problem in EDF scheduler
#2176
fishy behavior in termios tx task mode
#2198
Automate doxygen build
#2200
Missing IRC logs
#2207
RTEMS tar does not overwrite.
#2213
Decreased performance for whetstone benchmark using GCC >=4.5
#2261
Add coverage report generation support to rtems-tools
#2266
Move bsp_pretasking_hook() into files named bsppretaskinghook.c
#2284
h8300 gets error linking dl0* tests
#2289
rtems_ada_self is broken on SMP
#2305
sp07 needs to be split into an user extensions and a notepad test
#2306
powerpc/mvme5500/vectors/exceptionhandler.c uses task variables
#2308
Change uniprocessor INIT task mode to preempt.
#2325
Broken console driver infrastructure for SPARC
#2344
Second argument of ualarm() is ignored
#2350
One watchdog ticks header per scheduler instance
#2354
Replace red-black tree implementation, change API
#2355
SPARC: Several shared drivers are not SMP ready
#2363
SPARC: Silent FP context corruption possible
#2366
Create a Public API for the Atomic Operations
#2367
Documentation of User Extensions needs more information
#2377
rtems_waf: Tools without a version are not supported
#2385
Warning from commit "bsps/arm: Do not use __ARM_ARCH_7A__"
#2407
Enable function and data sections
#2408
Linker set based initialization
#2412
Improved priority inheritance implementation
#2420
RSB %source file fails
#2423
rtems_iterate_over_all_threads lacks user callback private pointer pass through
#2428
Add 4.12 Tool Target Configurations to RSB
#2441
lpc1768 variants fail to build with error in gpio.c
#2442
Remove avrtest BSP
#2443
Remove AVR Architectural Port
#2444
Remove m68k/mvme136 BSP
#2445
Remove m68k/sim68000 BSP
#2446
Remove M32R Architectural Port
#2447
Remove m32r/m32rsim
#2448
Remove mips/mongoose BSP
#2449
Remove arm/gba BSP
#2450
Remove arm/nds
#2451
Remove arm/gp32 BSP
#2452
Remove H8300 Architectual Port
#2453
Remove h8300/h8sim BSP
#2454
Warning in threadqops.c
#2455
Warning in spsimplesched02
#2457
Remove powerpc/ep1a BSP
#2458
Remove powerpc/score603e BSP
#2459
Add rtems_chain_get_first_unprotected() to chain API
#2464
RSB: Tool patches use the RTEMS version
#2468
Add Thread Local Storage (TLS) support on x86
#2477
Remove <rtems/debug.h>
#2487
Should https://devel.rtems.org/wiki/TBR/Delete/SpecBuilder be Deleted?
#2488
Vagrant Scripts
#2490
RSB: Use SHA512 instead of MD5
#2493
Remove notepads
#2494
Remove task variables
#2503
mvme5500 BSP: Exception Handler uses deprecated Notepads.
#2509
Should "https://devel.rtems.org/wiki/TBR/Delete/BSP_Template" be replaced?
#2513
Remove m68k/idp BSP
#2514
Make POSIX API mandatory (except signals and the sporadic server)
#2515
i386 score/libcpu API Layering Violation
#2527
Move pc386/tools/bin2boot to rtems-tools
#2529
BSP for the Atmel SAM V71/V70/E70/S70 chip platform
#2536
RSB allows use of insecure hash algorithms like MD5 and SHA1
#2537
Use Newlib exec*() variants and remove RTEMS versions
#2542
Review cxx_iostream size change per function-section changes
#2543
Obsolete gen68302 BSP
#2544
Osolete m68k/ods68302
#2545
Obsolete mbx8xx BSP
#2546
Obsolete idp BSP
#2552
Add per-section compilation and rtems dynamic linking support
#2553
[mvme3100] boot_card() broken by 37030e38
#2554
New watchdog handler implementation
#2555
Eliminate the Giant lock
#2556
Implement the O(m) Independence-Preserving Protocol (OMIP)
#2557
Add word splitting to print output
#2559
Delete the EXTERN pattern
#2560
smdk2410 is broken due to gp32 removal
#2562
RSB Docs Quick Start version number
#2576
arm/lpc176x: linker script update (add KEEP() sections)
#2606
alarm() uses seconds watchdog and thus is affected by clock changes
#2608
POSIX Condition Variables Clock Attribute Support
#2617
rtems_heap_allocate_aligned_with_boundary() body and prototype inconsistent
#2624
Fix the year 2038 problem
#2625
Use one lookup tree per-thread for the POSIX keys
#2626
Unify thread cancel/join and delete
#2627
Fix CPU time used for threads on SMP
#2628
Avoid home-grown condition variable implementation in the Classic Regions
#2631
Use an ISR lock to protect the state of Classic Rate Monotonic objects
#2632
rtems-tester failure
#2633
waf build failed for rtems-libbsd
#2634
New warning in pc386 VESA driver
#2638
pc386: ld -r issue with per function sections
#2641
configure: enable-rtemsbsp doesn't warn if bsp does not exist
#2644
sis does not run on gdb 7.11 but does on gdb 7.9
#2649
RSB remove 4.11, 4.10 and 4.9 from the master branch.
#2663
pc386 BSP has complex dependencies
#2664
spclock_err02
#2669
Update OpenRISC toolchain in 4.12
#2672
After latest patches with Objects_Get_by_name rtems-master not compiling without --enable-posix
#2674
CORE spinlock implementation is next to be useless
#2676
Obsolete clock_get() directive
#2680
Add pthread_setconcurrency() and pthread_getconcurrency()
#2684
rtems/c/src/lib/libbsp/sparc/leon3/clock/ckinit.c:122: duplicate if
#2685
c/src/lib/libbsp/arm/atsam/network/if_atsam.c:409: possible bad if statement
#2689
POSIX key destructors must be called during thread restart
#2692
User extensions execution order must be clarified
#2693
Update doc to reflect obsoleting rtems_clock_get()
#2694
linking issue for htonl, etc when using -std=c99
#2695
Add libatomic for RTEMS
#2696
Unpredictable errno value returned by sem_wait() in case of semaphore deletion
#2698
GCC 6.1 is broken for microblaze
#2700
cpukit/libfs/src/nfsclient/src/rpcio.c:524]: (style) Suspicious condition
#2701
Rename asm file with .S(upper case) ext. name
#2702
Remove descriptor objects for POSIX message queues
#2706
Buffer allocation of capture engine is broken on SMP configurations
#2707
Unsafe use of current processor index in capture engine
#2714
A pthread_detach() does not lead to a resource reclamation
#2718
Blocking _CORE_message_queue_Submit() may lead to unpredictable results
#2722
SEM_VALUE_MAX is unusually small on RTEMS
#2723
CPUINFO command to report per-processor information
#2725
Classic binary semaphores without a locking protocol can be released by everyone
#2726
grascs.c: Questionable use of binary semaphore
#2727
FAT file systems use wrong semaphore for mutual exclusion
#2728
Pipes use wrong semaphore for mutual exclusion
#2729
TFTP client uses wrong semaphore for mutual exclusion
#2732
Add clock_nanosleep()
#2734
pthread_setschedprio() is missing
#2735
pthread_setschedparam() sets the priority not according to POSIX
#2736
pthread_getschedparam() returns wrong priority values
#2737
Add CLOCK_DRIVER_USE_ONLY_BOOT_PROCESSOR
#2740
Suboptimal type for Timestamp_Control
#2741
New warning from printf plugin changes
#2742
New warning in SHM driver
#2745
Use clock from pthread_condattr in pthread_cond_timedwait
#2748
Move RTEMS-specific socket wake-up to RTEMS-specific <rtems/rtems_bsdnet.h>
#2749
rtems_task_set_scheduler() has insufficient parameters
#2750
Compile Error When Multiprocessing Enabled
#2751
Thread dispatch via interrupt is broken at least on ARM and PowerPC
#2752
Relax execution enviroment for thread begin extensions
#2754
no .strtab section
#2765
Application level deadlocks may lead to SMP lock level deadlocks
#2768
untar does not keep permissions correctly.
#2769
rtems-syms does not clean up temp files.
#2770
Missing documentation for RTEMS_LINKER_ROSET_CONTENT and RTEMS_LINKER_RWSET_CONTENT
#2771
Empty C++ file with just <rtems.h> does not compile with HEAD.
#2775
ARM CP15 arm_cp15_set_translation_table_entries fails if TTB in read-only memory
#2776
SPI Framework
#2777
Remove librtems++
#2778
Error building RTEMS Source Builder recipe for libxml
#2780
Capture engine accesses 'capture_per_cpu' without first checking.
#2784
Add function to get the current priority of a task by scheduler instance
#2788
RTEMS I2C API only defines Standard-mode (Sm) speed as a default.
#2790
Linker sets broken with GCC 7
#2795
Overrun Handling for general real-time models
#2797
Add ability to add/remove processors to/from a scheduler instance
#2798
Fix POSIX timer interval
#2800
qoriq variants failing to build
#2802
Test "libdl (RTL) 5" fails on SPARC targets
#2803
Get rid of CPU_BIG_ENDIAN and CPU_LITTLE_ENDIAN
#2805
Use SPRG0 on PowerPC for current per-CPU control (SMP only)
#2807
rtems-docs repository is not known to trac
#2808
Conditionally provide rtems_interrupt_frame
#2809
Reduce interrupt latency on SMP configurations during thread dispatch
#2810
Remove sparc/sis BSP variant
#2811
More robust thread dispatching on SMP and ARM Cortex-M
#2816
Many ARM BSPs have Static Assert
#2817
All Blackfin BSPs do not Compile on Master
#2818
NIOS2 Does Not Compile on Master
#2819
powerpc-ss555 does not compile on master
#2820
All SPARC64 BSPs do not Build on master
#2821
No BSPs Build on Master
#2822
m32csim does not build on master
#2823
Nearly all m68k BSPs do not Build on Master
#2824
arm/lpc23xx_tli800 no longer links tar01
#2825
Improve the fatal error handling chapter of the user manual
#2826
arm_cp15_get_translation_table_base_control_register warning.
#2829
xz git URL in README is broken
#2835
Ada support is broken on SMP configurations
#2836
Add posix_devctl()
#2838
Termios task driven mode should use mutex for device operations
#2839
Add new interrupt server driven Termios mode
#2840
Use self-contained mutexes for Termios framework
#2841
Add NXP SC16IS752 serial device driver
#2843
Use self-contained objects instead of Classic API for drivers and support libraries
#2844
JFFS2: Add IO controls to get filesystem instance information and force a garbage collection
#2845
Add I2C framework documentation
#2849
ATA/IDE support in RTEMS is out-dated
#2850
Driver manual covers non-existent Analog Driver
#2851
Driver manual covers non-existent Discrete Driver
#2853
Driver manual covers non-existent Non-Volatile Memory Driver
#2858
Add user defined thread names
#2859
Implement POSIX Shared Memory Objects
#2860
docs.rtems.org does not work on iPhones or iPads
#2861
Collaspe boxes hover on docs.rtems.org should indicate clickable.
#2862
docs.rtems.org Add support to ReST format releases.
#2863
Update POSIX 1003.1 Compliance Guide for ReST
#2864
docs.rtems.org Automatic update of branches content when a rtems-doc.git change is made.
#2865
Coverpage installed when building the docs repeats catalogue.xml entries
#2867
Fix exclude rule in rtems-test-check
#2868
src/c/src/lib/libbsp/arm/smdk2410/smc/smc.c: 3 * pointless local variables ?
#2873
src/c/src/lib/libbsp/arm/raspberrypi/i2c/i2c.c:320: defective error checking ?
#2874
src/c/src/lib/libbsp/powerpc/beatnik/marvell/gt_timer.c: 4 * pointless check ?
#2877
DHCP client fails on complex networks
#2878
src/c/src/lib/libbsp/sparc/shared/can/occan.c:1573: broken error checking ?
#2879
src/cpukit/libdebugger/rtems-debugger-server.c: four problems
#2880
src/cpukit/libfs/src/jffs2/src/readinode.c:189: faulty logic
#2883
src/c/src/lib/libbsp/arm/tms570/console/tms570-sci.c:248: strange expression ?
#2885
Fix rtems_rate_monotonic_postponed_job_count() prototype
#2889
RTEMS_STACK_CHECKER_EXTENSION has incomplete definition
#2890
_RBTree_Initialize_node generates warnings
#2893
Remove CONFIGURE_SMP_APPLICATION
#2894
Rename CONFIGURE_SMP_MAXIMUM_PROCESSORS to CONFIGURE_MAXIMUM_PROCESSORS
#2895
Prefix the confdefs.h internal defines with an underscore
#2896
RSB requirements are missing pax
#2897
Update termios.h to match the latest FREEBSD definitions
#2905
Merge LEON
#2906
rtems-doc waf configure does not detect sphinxcontrib.bibtex status
#2909
xz: Support for 64-bit CRC is build although XZ_USE_CRC64 is not defined
#2912
libdebugger: control reaches end of non-void function
#2916
termios: Change receive callback invocation to enable select() and poll() support
#2917
termios: Make write POSIX compatible
#2922
libdl unresolved externals that use more than one block or multiple entries corrupts.
#2923
Questionable Code in resource_snapshot.c
#2924
Warnings in SPARC BSPs
#2925
Warnings in rtl-obj-cache.c on some targets
#2926
Coverity Reports Multiple Out of Bounds Accesses in rtd-mdreloc-sparc.c
#2930
Coverity Reports Out of Bounds Read in drvmgr_print.c
#2935
Termios task driven mode not compatible with SMP
#2941
building rsb freezes
#2942
rtems building error
#2943
rtems building error
#2945
Many failures on LEON3 with SMP disabled
#2946
Add a top level global testsuite configuration file (.tcfg) and a 'user-input' test state.
#2949
Questionable patch organization in RTEMS tools and RSB
#2951
Error path in rtems-gcc-6.3.0-newlib-2.5.0.20170228-1.cfg
#2954
ARM: Optimize context switch
#2957
Shared memory support internal locking is broken
#2958
Add some popular benchmark programs to the testsuite
#2959
arm/libdl: C++ exception index tables may not be ordered correctly
#2960
RSB: Reports modified Git version in case RSB is a Git submodule
#2962
Set test configurations to reflect test results.
#2963
Add a testsuite top level confguration file that is common to all tests.
#2965
bootstrap sort inconsistent with sb-bootstrap for acinclude
#2967
ARM: Change ABI to not use short enums
#2968
newlib inttypes.h is missing some methods
#2969
qoriq BSPs depend on mkimage which is not always available
#2976
warnings in rtems-debugger-server.c
#2977
warnings in Dhrystone Benchmark
#2979
Load rap files failure with zeroed sections
#2980
pc586-sse does not compile fsjffs2gc01
#2981
testdata excludes on included tcfg files does not work
#2982
LibBSD broken with GCC+RTEMS changes
#2983
Create <rtems/inttypes.h> to consolidate extensions to <inttypes.h>
#2984
Changing Trac milestone page fails.
#2990
RTEMS Source Builder Fails on Windows Builds
#2992
Long path crashes the RSB when listing a directory.
#2993
SMP assert in _Thread_Executing in libdebugger
#2994
tar01 XZ error
#2995
Missing bsets
#2997
Monitor config command does not handle unlimited objects.
#2998
RTEMS User Manual Quick Start does not cover releases.
#2999
sb-check on Cygwin
#3000
Setting interrupt level in the mode arg on SMP returns RTEMS_UNSATISFIED
#3001
SMP build of RTEMS Testsuite does not set CONFIGURE_MAXIMUM_PROCESSORS
#3003
FAT does not support clusters bigger than 32K
#3006
SPARC LEON3 BSP SMP build is broken.
#3007
ARM caching issues
#3008
missing pax causes install failures
#3009
Provide invalid link handler for docs.rtems.org so old docs can be removed.
#3010
src/cpukit/posix/src/mmap.c:189]: (style) Suspicious condition
#3011
Error compiling xilinx_zynq_zedboard.
#3012
Global C++ IO streams are broken (cout, cin, cerr)
#3014
interrupt vector indexing is assuming BSP_INTERRUPT_VECTOR_MIN = 0 for this code.
#3015
Add support for IBM PPC 750 chip
#3016
missing a couple register names + a #ifndef __ASM__ around serial.h inclusion
#3017
improvement in pci.h
#3018
RSB cannot compile tool chain in CentOS 7.
#3023
Parameter of CPU_COPY() are in wrong order
#3025
m32c/m32csim does not build linpack-pc.c
#3027
RTEMS source builder fails when building gcc documentation with newer versions of gcc
#3032
CPU_NAND_S() implementation is not in line with FreeBSD
#3036
CPU_CMP() implementation is not in line with FreeBSD
#3043
4.11/rtems-nios2 does not build on Windows.
#3046
4.12/rtems-moxie missing release number.
#3047
Remove docs directory from the RSB
#3049
Warnings in libdebugger
#3052
RSB: powerpc GDB build broken on Apple Darwin
#3054
gdb 7.12.1 on RSB 4.12 branch fail to build on Archlinux
#3056
Add EDF SMP scheduler
#3057
Add a workaround for the LEON3FT store-store errata
#3059
Add a simple processor affinity support to the EDF SMP scheduler
#3061
including 'unistd.h' in C++ does not build.
#3063
Make the EDF scheduler the default SMP scheduler
#3069
Add rtems_scheduler_ident_by_processor()
#3070
Add rtems_scheduler_ident_by_processor_set()
#3071
Create an interrupt server for every processor in the system
#3072
Declaration of global functions in driver source files
#3076
Test suite failures due to floating point usage
#3077
SPARC: Add lazy floating point context switching
#3079
Ada tests do not build
#3080
Infinite loop in SPARC rtems_invalidate_multiple_instruction_lines()
#3082
Add 64-bit support for PowerPC
#3083
parallel make not working
#3084
Makefile recipe override warning has returned
#3085
Add hypervisor support for QorIQ BSPs
#3087
RSB rtems-gdb-7.12-1.cfg MD5 value is ERROR
#3088
shell test in testsuites\samples\fileio many COMMANDs is Lost
#3089
Inconsistent blocking addressing in RFS
#3090
Add BSP for i.MX 7
#3091
Core Dump in powerpc-rtems4.12-ld
#3096
Shell internal commands should be public.
#3098
Add new RTEMS repos to github.
#3099
Add RTEMS FDT wrapper and shell command to libmisc
#3100
Add Xilinx AXI I2C driver
#3101
Add I2C Drivers for LM25066A, TMP112, ADS1113 and ADS1115
#3102
rtems-exeinfo does not decode ARM static constructors.
#3103
rtems-tools on CentOS 7 Build Failure
#3109
Add RISC-V support
#3111
Newlib: Change time_t and clock_t integer types to 64-bit
#3112
POSIX: Make pthread_mutex_t self-contained
#3113
POSIX: Make pthread_cond_t self-contained
#3114
POSIX: Make pthread_barrier_t self-contained
#3115
POSIX: Make pthread_rwlock_t self-contained
#3116
POSIX: Make sem_t self-contained
#3117
score: Optimize _Thread_queue_Enqueue() timeout handling
#3121
clock() implementation in Newlib is broken
#3122
Simplify and unify BSP_output_char
#3123
GDB 8.0.1 is broken on FreeBSD 11
#3124
Ignore pshared attribute for POSIX semaphores
#3125
Accept PTHREAD_PROCESS_SHARED for POSIX mutexes
#3126
Accept PTHREAD_PROCESS_SHARED for POSIX barriers
#3127
MIPS tool build on Darwin (MacOS) fails.
#3128
RTEMS Tools corvar does not build on Windows.
#3129
RTEMS Tools covoar build fails on Windows
#3130
RTEMS Doxygen.in latex output does not build
#3132
Add reference counting to file descriptors
#3133
Remove rtems_libio_t::driver
#3134
Remove LIBIO_FLAGS_CREATE
#3135
Devel mailing list doesn't work and Git push impossible due to disk full
#3136
Use FIFO for file descriptor free list
#3137
Accept PTHREAD_PROCESS_SHARED for POSIX condition variables
#3138
RTEMS server `service2` root disk is full
#3139
Remove old ISR parameter from Clock_driver_support_install_isr() and make it optional
#3140
CPU Kit broken with --enable-rtems-debug
#3141
Change the BSP Howto's name to something smaller.
#3142
POSIX: Reduce size of pthread_once_t and make it zero-initialized
#3148
PSXRDWRV Test failure on Beaglebone Black
#3152
Beaglebone Black crashes on u-boot master build.
#3153
Accept PTHREAD_PROCESS_SHARED for POSIX rwlocks
#3157
PowerPC tools don't build on 32-bit hosts
#3158
Examples v2 does not build
#3159
Examples v2 trace linker ini files reference non-existing dump-on-error
#3160
Trace linker score support is broken
#3163
Add I2C device driver for temperature sensor LM75A
#3165
Rework components of the ticket system
#3166
New default ticket assignee: NeedsReview
#3167
Internal status codes must not depend on RTEMS_POSIX_API
#3168
Simplify POSIX_API_Control
#3169
Trac view change set results in a Trac error.
#3170
Use BSP_output_char via RTEMS printer or simple console driver for test output by default
#3171
RSB GCC does not build on High Sierra and APFS
#3172
i386 PC BSP does not reset when bsp_reset is called.
#3173
XIlinx AXI I2C driver IP race condition causes clock glitch.
#3174
Remove rtems_pthread_attribute_compare()
#3175
Merge FreeBSD timecounter changes from 2015-01-20 to now
#3176
__getreent in libc.a and generated by confdefs.h
#3177
Replace/update POSIX Compliance Guide
#3178
Update sh-rtems4.12 bset to use rtems-default (using old gcc)
#3179
New warnings from Time Changes
#3181
Various cc1plus warnings for "valid for C/ObjC but not for C++"
#3182
CLOCK_REALTIME timeout implementation is not POSIX compliant
#3185
Change uptime seconds to int32_t
#3187
smptests/Makefile.am Issues
#3188
Add C11 Threading Examples
#3189
MUTEX_INITIALIZER missing braces warning
#3190
RTEMS Tester covoar does not link on MacOS
#3191
RTEMS Tester covoar dies with no arguments.
#3198
Add lazy update of line control and baud divisor to NS16550 serial driver
#3200
m32c tests don't build -- test_context too large
#3201
epiphany tools checksum error
#3202
or1k tools build error
#3204
Exception in rtems-tester
#3205
Relative timespec timeouts are subject to integer overflows
#3206
BSPs Wiki Page is Out of Date
#3207
Supported Architectures Page is out of date
#3209
RSB should fail on this error
#3210
Improve the RSB build email message
#3211
Fix pthread_create() with user provided stack
#3212
Qemu Fails to Build, RSB Gives Odd Traceback
#3213
Move erc32, leon2, leon3, psim and jmr3904 to Tier 2
#3215
Configuring a System Still Includes Notepads and Has Wrong Heading
#3216
Replace vprintk() implementation
#3217
Add RTEMS version, build and tools details to tests
#3218
Termios canonical mode (ICANON) does not return input line by line
#3219
Zynq BSP missing linker option --gc-sections
#3220
Change RTEMS release number scheme from 4.12 to 5
#3221
RSB wiki page duplicates documentation
#3224
Upgrade or1k and m32c to Binutils 2.29
#3225
Upgrade m32c to GDB 8.0.1
#3226
gdb: pr 16827, fix sim on Mavrick
#3227
sb-check fails on Msys2 64-bit
#3228
aarch64 missing from 5/rtems-all build set
#3229
Add index to all documents.
#3230
RSB does not report --rsb-file for patches correctly.
#3231
RTEMS Top level README needs updating.
#3232
Use of `.. include::` in the User Manual should be changed.
#3233
Documentation has a number of warning that need fixing.
#3234
Quick Start Instructions Inconsistent
#3235
Fix rtems_semaphore_flush() for priority inheritance semaphores
#3236
Fix thread queue owner priority update in _Thread_queue_Flush_critical()
#3237
Fix priority ceiling updates
#3238
Git push to Trac with more than one commit does not update tickets.
#3239
Add getentropy() implementation provided by each BSP
#3240
cpukit/libmisc/stackchk/check.c stack addresses formatted incorrectly.
#3242
Workarounds for UT699, UT700, and GR712RC errata
#3243
Simplify global construction
#3244
Change rtems_panic() implementation and document this function
#3245
Replace BSP_panic() with rtems_panic()
#3246
Remove _BSP_Fatal_error()
#3247
Remove BSP-specific defaults for RTEMS_BSP_CLEANUP_OPTIONS()
#3248
Add BSP_VERBOSE_FATAL_EXTENSION to RTEMS_BSP_CLEANUP_OPTIONS
#3249
imx7 does not link getentropy01 test on master
#3254
Reorganize header files to avoid "make preinstall"
#3255
Warnings on 64-bit targets
#3256
Ada run-time needs support for self-contained POSIX synchronization objects
#3260
libpci depends on BSP-specific header files
#3264
Add monotonic watchdog based on uptime
#3265
Use second one based uptime for CLOCK_MONOTONIC for FreeBSD compatibility
#3266
cpukit/libpci references BSP headers.
#3267
rtems/status-checks.h calls printk without including the needed header.
#3268
PowerPC BSP include naming mess.
#3270
Remove unused support for MPC505
#3273
RSB removed used tools configuration files.
#3276
rtems-test: Add option to consume a log file and generate a report for it
#3277
QorIQ: Add MAC-less DPAA driver to libbsd
#3278
bsp-builder has incorrect print (%s in output)
#3281
Add epiphany support to GDB 8.0.0
#3283
Bad URL in OpenOCD/Xilinx_Zynq Wiki Page
#3284
RSB uses hard coded GCC binary paths
#3285
Reorganize BSP source directory
#3290
Add device tree support to Altera/Intel Cyclone V BSP
#3294
gcc version report for released tools is wrong.
#3298
dlerror non-conformance
#3305
Add paravirtualization support to ARM
#3306
Add paravirtualization support to PowerPC
#3307
PowerPC linkcmds.base missing wildcards on some sections
#3309
rtems_task_create's initial_mode SMP update
#3312
RSB macro calls such as define fail on unicode keys.
#3315
Move expat's home site to github from SF.
#3318
Improve INTERNAL_ERROR_THREAD_EXITTED to show the id and thread name
#3320
Add a simple task console driver
#3323
mhttpd's http etag can result in invalid caching in a browser.
#3325
Simplify clustered scheduler configuration
#3327
Eliminate score/cpu/*/.../types.h
#3328
bootstrap uses non-POSIX compliant echo -e
#3334
deadlock in _once()
#3339
Several PowerPC linker commands do not support constructors/destructors with priority
#3340
gen83xx warning for macros redefined
#3341
sparc64: Macro Redefined
#3342
pthread_setschedparam() has incorrect prototype
#3343
pthread_mutex_getprioceiling() has incorrect prototype
#3344
mcf5272/mcf5272.h Timer3 Duplicate Definition
#3345
mvme3100 spaces needed around quote in macro definitions in bsp.h
#3346
bf533.h
#3347
tms570: Register Macro Redefinition
#3348
beatnick:spaces needed around quote in macro definitions in bsp.h
#3349
pc386 edid.h invalid macro names
#3350
sptimecounter02 warning due to defining _KERNEL and disabling part of <sys/time.h>
#3352
Warning in all lpc176x variants
#3354
PowerPC BSPs duplicate PAGE_MASK, etc redefinition
#3358
Deprecate rtems_disk_create_phys(), etc.
#3374
rtems-test does not honor --mail-from argument
#3375
Remove command line pre-processor defines
#3376
Remove cklength program
#3377
Remove eolstrip program
#3378
Remove unhex program
#3379
Remove packhex program
#3380
Move rtems-bin2c program to rtems-tools
#3381
rtems-test command line documentation appears to be out of date
#3382
Testsuite Makefile merge to one per group of tests
#3383
Require --enable-rtemsbsp with --enable-smp or --enable-multiprocessor
#3384
Prefer int for int32_t
#3385
Generate an error if RTEMS's gcc is not found when the user runs configure
#3386
Trac's git changeset browsing is suspect.
#3387
Add subdir-objects to automake flags
#3388
rtems-tester: possible parsing error for qemuprep-altivec on exclude SMP configuration
#3389
Warning flags have disappeared with recent autoconf changes
#3390
NFS: Remove support for cexp
#3392
infinite loop in RSB's path when a prefix path is not writable
#3395
rtems-ld does not remove executable when there is an output error
#3396
rtems-ld does not handle R_ARM_V4BX relocation records
#3397
The register keyword is deprecated in C++11
#3399
dl06 error for moxie unknown machine type
#3400
dl06 error for powerpc/qoriq_e6500 unknown machine type
#3401
dl06: tms570* Mixed LSB/MSB Error
#3402
dl06: mips hurricane Mixed Endian Error
#3403
RSB RTEMS tool set build is irreproducible
#3404
CLOCK_MONOTONIC option on all POSIX services not exercised
#3407
Move Gaisler.org and Gaisler.se hosted RSB patches to rtems.org
#3408
Remove pc386 BSP variant
#3409
Strip down configure checks to the bare minimum
#3410
Remove bin2boot program used by i386 BSPs
#3411
qemuppc does not install linkcmds.base
#3413
examples-v2 both_hello and triple_period fail to build
#3414
Remove Makefiles from examples-v2?
#3415
Add examples and tests as components
#3416
Update Ubuntu RSB Instructions for 17.10
#3417
Add libdwarf to elftoolchain and provide a C++ wrapper
#3418
Remove difftest and sorttimes test tools
#3419
Always build network services (tftpfs, ftpfs, ftpd, telnetd, libdebugger)
#3420
Deprecate/obsolete rtems_io_lookup_name
#3421
New Trac components for Coverage and Trace
#3422
Move nbench from examples-v2 to main RTEMS benchmarks
#3423
examples-v2: m68k/powerpc BSPs undefined reference to _Thread_Life_action_handler
#3424
examples-v2: no MIPS BSPs pass configuration step
#3425
examples-v2: PowerPC fails to build fat_ramdisk
#3431
Eliminate use of __ppc_generic and other PowerPC model defines in BSP configure.ac
#3432
Remove Simple SMP Priority Scheduler
#3433
Add SMP support for RISC-V
#3434
Add CONFIGURE_MINIMUM_POSIX_THREAD_STACK_SIZE configuration option
#3435
Add test case for CONFIGURE_BSP_PREREQUISITE_DRIVERS configuration option
#3436
Remove clock driver Clock_driver_support_shutdown_hardware() hook
#3437
Replace use of printk() in free() with a fatal error
#3443
Remove shgen program
#3444
Remove nios2gen program
#3445
Remove multigen script
#3446
Remove cvsignore-add.sh script
#3447
Remove rtems-testsuite-autostuff script
#3448
Add GCC, Binutils+GDB, Newlib mirrors to RTEMS github
#3450
Space character in path breaks rtems build on Linux
#3451
Remove size_rtems script
#3452
Update RISC-V tool chain to support standard 64-bit chips
#3453
Add RISC-V GDB
#3455
Remove install-if-change script
#3456
Add support for CPU counter timestamps
#3457
rtems-tools has errors with waf-2.0.7 and later.
#3458
rtems-test should not use the env PATH to find covoar
#3459
Rework initialization and interrupt stack support
#3461
Canadian cross compilation of RTEMS tools not supported for x86_64-w64-mingw32
#3462
Convert covoar C code to C++
#3463
Convert covoar to use DWARF function data
#3465
Integrate all changes from Linux v3.11 to v4.17 made in the JFFS2 sources
#3471
Update libfdt as of date 2018-07-09
#3472
Update of libbsd to a version close to the FreeBSD 12 release
#3473
Getting Started Wiki Page Redundant with Users Guide
#3475
Add RTEMS_PREDICT_TRUE() and RTEMS_PREDICT_FALSE() for static branch prediction hints
#3478
RISCV BSP Tester Cleanup Needed
#3480
CONFIGURE_MINIMUM_TASK_STACK_SIZE may affect CONFIGURE_INTERRUPT_STACK_SIZE
#3482
Relax the buffer alignment required by rtems_partition_create()
#3484
RFS: Remove stray call of rtems_disk_release() in rtems_rfs_buffer_sync()
#3486
Use uintptr_t and size_t instead of uint32_t in rtems_partition_create()
#3488
Remove CONFIGURE_HAS_OWN_MOUNT_TABLE
#3489
Obsolete CONFIGURE_HAS_OWN_CONFIGURATION_TABLE
#3490
Remove CONFIGURE_HAS_OWN_CONFIGURATION_TABLE
#3491
Align mprotect() prototype with POSIX
#3492
Incorporate High Quality SPARC Web Page into CPU SUpplement
#3496
Remove superfluous interrupt enable in _Thread_Dispatch_enable()
#3498
Command and Variable Index is empty
#3499
The "Index" chapter is empty
#3500
Change rtems_waf's RTEMS path check from `bin` to share/rtems<version>`
#3501
MSR_RI defined multiple places
#3502
PL111_LCD_CONTROL_LCD_BPP_16 Redefined
#3503
PDF Documentation is missing an index
#3504
Warning and formatting in bsps/powerpc/mpc55xxevb/dev/dspi.c
#3505
powerpc/virtex redefined warning
#3506
waf for building RTEMS applications needs updating
#3507
Add flexible per-CPU data
#3508
Add support for thread to processor pinning
#3510
ATA driver uses deprecated rtems_blkdev services
#3511
int/pointer size warnings in powerpc-qoriq_e6500_64
#3512
sb-check:No python command with Python 2 and Python 3 installed
#3513
Convert tqm8xx console driver to new Termios API
#3514
Resource Leak in hexdump-parse.c (CID 26032)
#3516
sb-set-builder should report disk usage of build
#3517
RSB Ubuntu Host Requirements Missing Some
#3518
RSB MacOS Nits
#3519
RSB does not strictly check args
#3520
Remove CONFIGURE_HAS_OWN_FILESYSTEM_TABLE
#3522
Update mDNSResponder to Apple version v878.30.4
#3523
Add FEC network interface driver for TQM8XX
#3524
Add a separate system initialization handler set for secondary processors
#3525
Add MMC/SDCard support for i.MX 7Dual BSP
#3526
Convert PTY driver to new Termios API

Details

Ticket Created Resolution Component Reporter Owner Modified
#1247 11 years ago fixed fs strauman Chris Johns 11 months ago
Summary

RTEMS does not implement locks needed by multithreaded newlib

Description

multi-threaded newlib protects a number of internal data structures (as of newlib-1.15 these comprise:

  • global list of FILE objects
  • stdio FILE object initializer
  • individual FILEs [since FILEs with the exception of stdin/stdout/stderr are per-process entities]
  • global hash table used by telldir/seekdir
  • individual DIR structures (opendir/readdir)
  • atexit list
  • list of environment variables
  • global timezone variable

) using mutexes. It expects the OS to implement these locks but defaults to not using locking if the OS does not provide an implementation. Currently, RTEMS does *not* provide its own implementation of 'sys/lock.h' and therefore vital data structures in newlib are currently *unprotected* (with the exception of environment variables -- 'envlock.c' had been added to RTEMS a while ago but since then, newlib has introduced more locks and a general OS interface which - once implemented - will obsolete 'envlock.c').

Note that while semantics of having no protection for individual FILE objects may be tolerable, having no protection for global newlib data structures such as lists of FILEs is not acceptable.

I am currently working on an implementation which should be available shortly.

#1394 10 years ago fixed tool/newlib Daniel Hellstrom Chris Johns 11 months ago
Summary

scandir() fails due to MAXNAMELEN is incorrect

Description

I have been trying to use scandir() however the newlib one does not work due to MAXNAMLEN and NAMLEN differ. scandir in libcsupport seems to have a fix for this, however my libcsupport_a-scandir.o is empty, I'm guessing because HAVE_SCANDIR is defined.

It is used in scandir() (newlib-1.17.0/newlib/libc/posix/scandir.c:117) by the macro DIRSIZ. Where DIRSIZ uses the MAXNAMELEN define which is set incorrectly. It does not match the sizeof(struct dirent) which makes the DIRSIZ return a negative number, then malloc(DIRSIZ(d)) will try to allocate 4GB which fail.

My guess is that MAXNAMELEN should be defined in newlib-1.17.0/newlib/libc/sys/rtems/sys/dirent.h or newlib-1.17.0/newlib/libc/sys/rtems/include/limits.h or in a new file.

I tried to run the code below on my FAT filesystem, taken directly from the scandir(3) man page.

/* print files in current directory in reverse order */ #include <dirent.h> main(){

struct dirent namelist; int n;

n = scandir(".", &namelist, 0, NULL); if (n < 0)

perror("scandir");

else {

while(n--) {

printf("%s\n", namelist[n]->d_name); free(namelist[n]);

} free(namelist);

}

}

#1662 8 years ago fixed fs Bharath Suri Chris Johns 8 months ago
Summary

termios.c: semaphore not deleted, consequently resulting in failure of rtems_termios_open

Description

The semaphore osem is still in use in rtems_termios_close while an attempt to delete it is made and hence is not deleted. Consequently, it results in a RTEMS_TOO_MANY on rtems_semaphore_create, which further results in failure of rtems_termios_open.

#1747 8 years ago fixed score Chris Johns Sebastian Huber 11 months ago
Summary

Heap extend allows discontinuous memory regions.

Description

The check in (cpukit/ChangeLog) states:

2010-06-07 Sebastian Huber <sebastian.huber@…>

  • score/src/heapextend.c: Implemented support for scattered heap areas.

The heap cannot support scattered blocks because the _Heap_Is_block_in_heap assumes the region is continuous between the first and last blocks of the heap. Making the gaps in the regions passed to the heap extend call used is questionable and makes the _Heap_Is_block_in_heap test not really perform the task it's name states. This is an issue because it is this check that determines if a heap free of NULL should proceed. This issue is covered in another PR.

I also wonder about a heap free call to an address that maps to one of the "in-use" gap regions. The previous heap code knew if an address was in the heap and therefore it was kind of safe to probe for a valid block. This assumption is now not valid.

The former heap extend code:

http://www.rtems.org/viewvc/rtems/cpukit/score/src/heapextend.c?revision=1.7&view=markup

clearly states the type of memory that can be added to an existing heap. The current code has no restrictions. The user manual is not great in this area. It would also be useful if comments are added to the heap extend code.

The heap extend code is used by the rtems_region_extend call and this call clearly states in the manual that the memory region must be continuous. If this has changed we should discuss the API change and make better note of it. I also suspect the testsuite will need additions to test any API changes.

#1971 7 years ago fixed fs nopscmn Chris Johns 8 months ago
Summary

Memory leak in tmpfile()

Description

Hello,

I use tmpfile() in my RTEMS application, and found that it has memory leak. I wrote small test application (see attachment), that output memory usage:

Memory usage before: Number of used blocks: 12 Largest used block: 1288 Total bytes used: 3628

Memory used after: Number of used blocks: 1013 Largest used block: 1288 Total bytes used: 112064

By 1000 iteration, each call tmpfile() cause memory leak about 108 bytes.

#2132 5 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

<rtems/score/basedefs.h> superfluously includes <limits.h>

Description

In older RTEMS versions <rtems.h> provided <limits.h> indirectly. The include of <limits.h> was added to not break application source files that relied on this accidentally.

We may remove this include in the future.

#2133 5 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

<rtems/score/basedefs.h> superfluously includes <string.h>

Description

In older RTEMS versions <rtems.h> provided <string.h> indirectly. The include of <string.h> was added to not break application source files that relied on this accidentally.

We may remove this include in the future.

#2135 5 years ago fixed posix Sebastian Huber Sebastian Huber 11 months ago
Summary

times() and _times() are subject to integer overflows

Description

The clock_t type is defined as unsigned long for RTEMS in Newlib. With a 1ms clock tick an overflow happens after 7 days on 32-bit long targets.

#2173 5 years ago fixed score Sebastian Huber Joel Sherrill 11 months ago
Summary

Potential integer overflow problem in EDF scheduler

Description

On 2014-03-21 14:46, Gedare Bloom wrote:> On Fri, Mar 21, 2014 at 9:43 AM, Sebastian Huber

<sebastian.huber@…> wrote:

[...]

I have another question regarding the EDF scheduler. Does this work in case _Watchdog_Ticks_since_boot overflows?

No. For this, I think we need to use "deadline folding" which is just modulo arithmetic.

void _Scheduler_EDF_Release_job(

Thread_Control *the_thread, uint32_t deadline

) {

Priority_Control new_priority;

if (deadline) {

/* Initializing or shifting deadline. */ new_priority = (_Watchdog_Ticks_since_boot + deadline)

& ~SCHEDULER_EDF_PRIO_MSB;

} else {

/* Switch back to background priority. */ new_priority = the_thread->Start.initial_priority;

}

the_thread->real_priority = new_priority; _Thread_Change_priority(the_thread, new_priority, true);

}

_Watchdog_Ticks_since_boot us uint32_t and overflows after 49 days with a one millisecond clock tick.

#2176 4 years ago wontfix score Jeffrey Hill Joel Sherrill 11 months ago
Summary

fishy behavior in termios tx task mode

Description

I have a look around in the drivers in the various BSPs and I notice that none of the termios drivers appear to transmit characters at task level even if they are running in termios task mode. Maybe all (most) of them send characters in the ISR. If there was a large frame of characters to send then this could lock out task activity for too long.

FWIW, I had a closer look at this today, and maybe something is fishy in the termios code when the TX part of termios runs in task driven mode. It seems that in task mode if the UART can accept characters immediately in the write routine then we wouldn’t need to turn on any interrupts at all. The write routine would need to somehow tell termios how many characters it sent; presumably this would occur by calling rtems_termios_dequeue_characters in the driver's write function. I see in the code that this tries to work, rtems_termios_dequeue_characters posts the semaphore of termios tx and increases the characters sent count of termios. However after the write routine returns it goes badly.

If the transmitter runs in termios TASK mode and the driver's write routine does not immediately enable an interrupt, then it returns to the code below in rtems_termios_puts and it sets the transmitter to rob_busy. After that the termios tx daemon proceeds to step through all of the characters remaining (I think that I see this in the debugger) and discards them because the transmitter stays in rob_busy state.

It's also probably odd that termios calls the write function with interrupts disabled when it is in task driven mode; we could loop outputting a large frame of characters in the write routine at task level with interrupts globally disabled.

if (tty->rawOutBufState == rob_idle) {

/* check, whether XOFF has been received */ if (!(tty->flow_ctrl & FL_ORCVXOF)) {

(*tty->device.write)(tty->minor,

(char *)&tty->rawOutBuf.theBuf[tty->rawOutBuf.Tail],1);

} else {

/* remember that output has been stopped due to flow ctrl*/ tty->flow_ctrl |= FL_OSTOP;

} tty->rawOutBufState = rob_busy;

}

[debug]#0 rtems_termios_puts (_buf=0x9ca60, len=1, tty=0x11509c) at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/libcsupport/src/termios.c:677 [debug]#1 0x00015c68 in oproc (c=99 'c', tty=0x11509c) at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/libcsupport/src/termios.c:748 [debug]#2 0x00015d9c in rtems_termios_write (arg=0x9cad8) at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/libcsupport/src/termios.c:770 [debug]#3 0x00002ef0 in console_write (major=0, minor=0, arg=0x9cad8) at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/lib/libbsp/nios2/altera-sys-config/./console/console.c:171 [debug]#4 0x0006c328 in rtems_io_write (major=0, minor=0, argument=0x9cad8) at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/sapi/src/iowrite.c:47 [debug]#5 0x00068044 in device_write (iop=0x114988, buffer=0x3366d4, count=44) at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/libfs/src/imfs/deviceio.c:160 [debug]#6 0x00017ef4 in write (fd=1, buffer=0x3366d4, count=44) at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/libcsupport/src/write.c:51 [debug]#7 0x0007f078 in _write_r (ptr=0x9d638, fd=1, buf=0x3366d4, nbytes=44) at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/libcsupport/src/write_r.c:38 [debug]#8 0x0006d488 in _fflush_r (ptr=0x9d638, fp=0x9d98c) at ../../../../../../nios2-rtems/altera/altera11.0/gnu-tools/rtems-patched/gcc-4.1/newlib/libc/stdio/fflush.c:214 [debug]#9 0x000754e8 in sfvwrite_r (ptr=0x9d638, fp=0x9d98c, uio=0x9cbe0) at ../../../../../../nios2-rtems/altera/altera11.0/gnu-tools/rtems-patched/gcc-4.1/newlib/libc/stdio/fvwrite.c:257 [debug]#10 0x0007830c in sprint_r (ptr=0x9d638, fp=0x20, uio=0x9cbe0) at ../../../../../../nios2-rtems/altera/altera11.0/gnu-tools/rtems-patched/gcc-4.1/newlib/libc/stdio/vfprintf.c:322 [debug]#11 0x00072fc8 in _vfprintf_r (data=0x9d638, fp=0x9d98c, fmt0=<value optimized out>, ap=0x0) at ../../../../../../nios2-rtems/altera/altera11.0/gnu-tools/rtems-patched/gcc-4.1/newlib/libc/stdio/vfprintf.c:1501 [debug]#12 0x0006dce8 in printf (fmt=0x1 "") at ../../../../../../nios2-rtems/altera/altera11.0/gnu-tools/rtems-patched/gcc-4.1/newlib/libc/stdio/printf.c:52 [debug]#13 0x00057de0 in bootpc_init (update_files=false, forever=true) at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/libnetworking/nfs/bootp_subr.c:997 [debug]#14 0x0002960c in rtems_bsdnet_do_bootp () at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/libnetworking/rtems/rtems_bootp.c:23 [debug]#15 0x0002b218 in rtems_bsdnet_initialize_network () at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/libnetworking/rtems/rtems_glue.c:980 [debug]#16 0x00001528 in Init (ignored=565432) at init.c:47 [debug]#17 0x0006ccb0 in _Thread_Handler () at /home/hill/nios2-rtems/rtems/rtems-git/rtems-4.10/c/src/../../cpukit/score/src/threadhandler.c:145 [debug]#18 0x0006cc28 in _Thread_Is_heir (the_thread=0x6cc28) at ../../cpukit/../../../altera-sys-config/lib/include/rtems/score/thread.inl:82 [debug]Backtrace stopped: frame did not save the PC

#2198 4 years ago fixed doc Gedare Chris Johns 3 months ago
Summary

Automate doxygen build

Description

The doxygen builds are no longer being generated nightly.

#2207 4 years ago fixed unspecified Chris Johns Chris Johns 11 months ago
Summary

RTEMS tar does not overwrite.

Description

A host tar by default will overwrite the contents of a directory. A sort of refresh. The RTEMS tar requires you remove the existing files rather than overwrite. This is dangerous because you have to remove files yet you do not know if the tar will be successful and moving and saving files assumes you know the contents of the tar file before hand.

Tar should be changed to overwrite and so allow files to be refreshed.

Consistence of files should be managed outside of tar via hashes or checksums.

#2213 4 years ago fixed tool/gcc daniel.cederman Daniel Hellstrom 11 months ago
Summary

Decreased performance for whetstone benchmark using GCC >=4.5

Description

Moving from GCC 4.4.2 to 4.9.2 increases the execution time of the whetstone benchmark on both SPARC and x86. The cause seems to be a single commit. I have submitted a bug report to the GCC bugzilla:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64193

#2261 4 years ago fixed unspecified Joel Sherrill 11 months ago
Summary

Add coverage report generation support to rtems-tools

Description

This ticket is to capture the current state of the project started by Krzysztof Mięsowicz <krzysztof.miesowicz@…>. The goals of the project were to:

  • replace the existing shell scripts in rtems-testing with Python code integrated into rtems-tools
  • add the capability to generate a report per directory. This is important because a large body of code with low coverage negatively impacts the overall coverage area and makes reports harder to read. Breaking the reports down by functional area lets us do coverage reporting on more code even when some of the areas are in need of testing improvement.

The remaining effort in conjunction with other activity related to coverage such as inclusion of gcov generated reports is a good "summer of code" type project. This is an important capability to add to the rtems-tools.

The attached tar file krzy-patches.tar.bz2 contains the current code. There may be other issues to resolve but writing from memory, the following are the highest priority ones:

  • no default setting for coverage enable/disable
  • configuration file has hard coded paths. This should be able to be a template which is adjusted by the tools at run-time.
  • variable naming and coding style does not match that used in other Python code in rtems-tools

Krzysztof wrote some in his blog about this (http://kmiesowicz.blogspot.com/p/esa-socis-2014.html). Ensure that your base RTEMS tools are built with the RTEMS Source Builder and check on the development list if it builds a qemu with coverage support. This may have changed since he blogged.

#2266 4 years ago invalid unspecified Joel Sherrill 11 months ago
Summary

Move bsp_pretasking_hook() into files named bsppretaskinghook.c

Description

Over the past few years, we have split out the BSP required methods into their own files with consistent names. bsp_pretasking_hook() is next on the list.

$ grep -rl bsp_pretasking_hook . ./sparc/shared/bsppretaskinghook.c ./powerpc/score603e/startup/bspstart.c ./powerpc/beatnik/startup/bspstart.c ./powerpc/virtex5/startup/bspstart.c ./powerpc/virtex5/start/start.S ./powerpc/shared/startup/pretaskinghook.c ./powerpc/virtex4/startup/bspstart.c ./powerpc/virtex4/start/start.S ./powerpc/ep1a/startup/bspstart.c ./arm/lpc176x/startup/bspstart.c ./arm/lpc24xx/startup/bspstart.c ./bfin/bf537Stamp/startup/bspstart.c ./bfin/TLL6527M/startup/bspstart.c ./bfin/eZKit533/startup/bspstart.c ./shared/include/bootcard.h ./shared/bsppretaskinghook.c ./shared/bootcard.c

#2284 4 years ago wontfix unspecified Joel Sherrill Chris Johns 11 months ago
Summary

h8300 gets error linking dl0* tests

Description

rtems-syms -e -c "-mh -mint32 -O2 -g -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs" -o dl-sym.o dl01.pre h8300-rtems4.11-gcc -B../../../../../h8sim/lib/ -specs bsp_specs -qrtems -mh -mint32 -O2 -g -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -mh -mint32 \

-o dl01.exe init.o dl-load.o dl-tar.o dl-sym.o

dl-sym.o: In function `rtems_rtl_base_global_syms_init': rld--gTgaaa.c:(.text+0xa): undefined reference to `rtemsrtl_base_globals_size' rld--gTgaaa.c:(.text+0x10): undefined reference to `rtemsrtl_base_globals' collect2: error: ld returned 1 exit status

#2289 4 years ago fixed tool/gcc Sebastian Huber Needs Funding 11 months ago
Summary

rtems_ada_self is broken on SMP

Description

The global variable rtems_ada_self is broken on SMP (similar to the task variables) and should be replaced with a function call or thread specific data.

#2305 4 years ago wontfix unspecified Joel Sherrill 11 months ago
Summary

sp07 needs to be split into an user extensions and a notepad test

Description

I was reviewing all code in the tree which uses deprecated methods. I will fix most of the cases. This is going to take a little more time. This test needs to be split apart. I think the notepad usage can go into a new test spnotepad02. It is primarily ensuring that two threads can exchange values through notepads.

The remaining use of notepads in sp07 can probably just be a count down on the priority.

I am starting to move code to spnotepad02 from sp07 that is not related to the tasks counting down.

Hopefully I can resolve this without much feedback.

#2306 4 years ago fixed arch/powerpc Joel Sherrill 11 months ago
Summary

powerpc/mvme5500/vectors/exceptionhandler.c uses task variables

Description

I am addressing almost all uses of deprecated methods. They are mostly calls to rtems_clock_get() which can be easily corrected or test code which will be removed when the deprecated feature is removed.

This BSP however has what appears to be a unique feature -- the ability for a thread to add a unique exception fault handler. My inclination is to rip this out but I am not doing it now. I am just turning off deprecated warnings for the file.

#2308 4 years ago fixed unspecified Chris Johns 11 months ago
Summary

Change uniprocessor INIT task mode to preempt.

Description

The current INIT task mode for a uni-processor build is NO_PREEMPT. This is not possible on an SMP system and so the default mode is PREEMPT. Both system should be the same and so the uniprocessor mode should be changed.

#2325 3 years ago fixed arch/sparc Sebastian Huber Daniel Hellstrom 11 months ago
Summary

Broken console driver infrastructure for SPARC

Description

The stuff in "c/src/lib/libbsp/sparc/shared/uart/cons.c" should get removed and the new Termios device API should be used instead (see also rtems_termios_device_install()).

#2344 3 years ago fixed unspecified Sebastian Huber Sebastian Huber 11 months ago
Summary

Second argument of ualarm() is ignored

Description

I don't think this is in line with POSIX.

#2350 3 years ago fixed score Sebastian Huber 11 months ago
Summary

One watchdog ticks header per scheduler instance

Description

Currently there is one watchdog header for all ticks based watchdogs. This is not scalable. For example on the Freescale T4240 platform with 24-processors we observe in the smptests/smpwakeafter01 test a maximum thread dispatch disabled time of 3.8ms on processor 0 and 1.7ms on the other processors.

<PerCPUProfilingReport processorIndex="0">
  <MaxThreadDispatchDisabledTime unit="ns">3807457</MaxThreadDispatchDisabledTime>
  <MeanThreadDispatchDisabledTime unit="ns">124091</MeanThreadDispatchDisabledTime>
  <TotalThreadDispatchDisabledTime unit="ns">1706880473</TotalThreadDispatchDisabledTime>
  <ThreadDispatchDisabledCount>13755</ThreadDispatchDisabledCount>
  <MaxInterruptDelay unit="ns">0</MaxInterruptDelay>
  <MaxInterruptTime unit="ns">24661</MaxInterruptTime>
  <MeanInterruptTime unit="ns">10148</MeanInterruptTime>
  <TotalInterruptTime unit="ns">127682501</TotalInterruptTime>
  <InterruptCount>12582</InterruptCount>
</PerCPUProfilingReport>
<PerCPUProfilingReport processorIndex="1">
  <MaxThreadDispatchDisabledTime unit="ns">1715826</MaxThreadDispatchDisabledTime>
  <MeanThreadDispatchDisabledTime unit="ns">102805</MeanThreadDispatchDisabledTime>
  <TotalThreadDispatchDisabledTime unit="ns">1884937615</TotalThreadDispatchDisabledTime>
  <ThreadDispatchDisabledCount>18335</ThreadDispatchDisabledCount>
  <MaxInterruptDelay unit="ns">0</MaxInterruptDelay>
  <MaxInterruptTime unit="ns">47</MaxInterruptTime>
  <MeanInterruptTime unit="ns">12</MeanInterruptTime>
  <TotalInterruptTime unit="ns">8299</TotalInterruptTime>
  <InterruptCount>664</InterruptCount>
</PerCPUProfilingReport>
<SMPLockProfilingReport name="Watchdog">
  <MaxAcquireTime unit="ns">47020</MaxAcquireTime>
  <MaxSectionTime unit="ns">2709</MaxSectionTime>
  <MeanAcquireTime unit="ns">31</MeanAcquireTime>
  <MeanSectionTime unit="ns">52</MeanSectionTime>
  <TotalAcquireTime unit="ns">990203330</TotalAcquireTime>
  <TotalSectionTime unit="ns">1674926849</TotalSectionTime>
  <UsageCount>31604848</UsageCount>
  <ContentionCount initialQueueLength="0">10574</ContentionCount>
  <ContentionCount initialQueueLength="1">8168</ContentionCount>
  <ContentionCount initialQueueLength="2">8578</ContentionCount>
  <ContentionCount initialQueueLength="3">31577528</ContentionCount>
</SMPLockProfilingReport>

The watchdog lock is highly contended and since the watchdog insert procedure acquires and releases the lock during the iteration of the watchdog chain several times, this yields the high thread dispatch disabled times.

To get rid of this bottleneck we should move the watchdog context into the scheduler context to use one watchdog context per scheduler instance. Take care that active watchdogs move in case of a scheduler change of a thread.

#2354 3 years ago fixed unspecified Sebastian Huber 11 months ago
Summary

Replace red-black tree implementation, change API

Description

The RTEMS red-black tree implementation is not as good as the BSD implementation which performs quite well in a benchmark:

https://github.com/sebhub/rb-bench

Proposal:

https://github.com/sebhub/rb-bench/blob/master/test-rbtree-bsd-for-rtems.c

One benefit is that the search/insert is done inline and the red-black tree fixup is done in a general purpose _BSD_RBTree_Insert_color() function (similar to the Linux red-black tree API).

This makes it possible to get rid of the red-black tree implementation used by the JFFS2 support.

#2355 3 years ago fixed arch/sparc Sebastian Huber Daniel Hellstrom 10 months ago
Summary

SPARC: Several shared drivers are not SMP ready

Description

Several drivers in c/src/lib/libbsp/sparc/shared/ use interrupt disable/enable for low-level mutual exclusion. This is not enough on SMP configurations.

#2363 3 years ago duplicate arch/sparc Sebastian Huber 8 months ago
Summary

SPARC: Silent FP context corruption possible

Description

On uni-processor configurations the post-switch actions (e.g. signal handlers) and context switch extensions may silently corrupt the floating point context. Set test sptests/spcontext01.

This problem exists for many years and might be working as intended. It is possible to fix this issue using the SPARC_USE_SAFE_FP_SUPPORT option. This is already used for the SMP configurations. The disadavantage is that this disables the deferred floating point support.

#2366 3 years ago wontfix score Joel Sherrill 11 months ago
Summary

Create a Public API for the Atomic Operations

Description

Ticket #2364 regarded use of a pthread mutex in three graphics driver as basically an atomic flag to ensure only one open() was active at a time. This created an unnecessary dependency on the POSIX API being enabled. I changed the code to use score Atomic flags.

This highlighted the need for a public Atomic API.

The existing tests could be converted to the public API, a macro wrapper written for Classic API Atomics, and documentation added. This may be enough to be a small GSOC project.

#2367 3 years ago fixed doc mw Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

Documentation of User Extensions needs more information

Description

The documentation for User Extension sets in the C User's Guide could use some clarification. It discusses the multiple sets of extensions, but it is unclear as to whether or not the extensions are added or replaced when rtems_extension_create() is called. There is a section - 22.2.4 (Order of Invocation) that does discuss the operation of the sets, but it only makes sense once the reader understands that the sets are, in fact, additive.

#2377 3 years ago wontfix tool Sebastian Huber 11 months ago
Summary

rtems_waf: Tools without a version are not supported

Description

waf configure --prefix=/opt/rtems --rtems=/opt/rtems --rtems-tools=/opt/rtems --rtems-bsps=i386/pc686 Setting top to : /scratch/git-rtems-libbsd Setting out to : /scratch/git-rtems-libbsd/build Could not find any architectures (complete log in /scratch/git-rtems-libbsd-upstream/build/config.log)

#2385 3 years ago fixed arch/arm Chris Johns Sebastian Huber 11 months ago
Summary

Warning from commit "bsps/arm: Do not use ARM_ARCH_7A"

Description

This change https://git.rtems.org/rtems/commit/?h=4.11&id=d0733bb8 generate a warning in user code. The warning is:

.../arm-errata.h:45:1: warning: 'in line' is not at beginning of declaration [-Wold-style-declaration]
 static bool inline arm_errata_is_applicable_processor_errata_764369(void)
 ^
#2407 3 years ago fixed build Sebastian Huber Joel Sherrill 11 months ago
Summary

Enable function and data sections

Description

In order to reduce the size of executables it is beneficial to put all global functions and data into separate sections. This enables the linker to perform a garbage collection which removes all items not directly referenced. The following steps are necessary:

  1. Modify the build system to use the following compiler and linker flags:

CFLAGS += -ffunction-sections -fdata-sections LDFLAGS += -Wl,--gc-sections

  1. Review all linker command files and ensure that linker sets and global constructor sections are not affected by the garbage collection (e.g. use the KEEP() directive of GNU ld).
#2408 3 years ago fixed unspecified Sebastian Huber Sebastian Huber 5 months ago
Summary

Linker set based initialization

Description

Linker sets are used for example in Linux, FreeBSD (they are used in the RTEMS port of the FreeBSD network stack, e.g. libbsd), eCos and for global C++ constructors. They provide a space efficient and flexible means to initialize modules. A linker set consists of

  • dedicated input sections for the linker (e.g. .ctors and .ctors.* in the case of global constructors),
  • a begin marker (e.g. provided by crtbegin.o, and
  • an end marker (e.g. provided by ctrend.o).

A module may place a certain data item into the dedicated input section. The linker will collect all such data items in this section and creates a begin and end marker. The initialization code can then use the begin and end markers to find all the collected data items (e.g. function pointers).

Lets look how this works using a simple example. For this we need three files myset.h,

#ifndef MYSET_H
#define MYSET_H

/* The linker set items */
typedef struct {
  void (*func)(void);
} item;

/*
 * Macro to create a linker set item.  The first parameter is
 * the designator of the item.  It must be unique within the
 * module scope.  The second parameter is the desired function.
 */
#define MYSET_ITEM(i, f) \
    __attribute__((used)) \
    __attribute__((section(".rtemsroset.myset.content"))) \
    static item i = { f }

#endif /* MYSET_H */

module.c

#include "myset.h"
#include <stdio.h>

/*
 * Some global function that needs a module specific
 * intialization done by f().
 */
void
g(void)
{

        printf("g()\n");
}

/* The module constructor */
static void
f(void)
{

        printf("f()\n");
}

/*
 * This registers the module constructor f()
 * in the linker set "myset".
 */
MYSET_ITEM(i, &f);

and init.c.

#include "myset.h"
#include <stddef.h>

/* Should be in a proper header file */
void g(void);

/* Define the start marker */
__attribute__((used))
__attribute__((section(".rtemsroset.myset.begin")))
static volatile const item begin[0];

/* Define the end marker */
__attribute__((used))
__attribute__((section(".rtemsroset.myset.end")))
static volatile const item end[0];

int main(void)
{
        size_t n = &end[0] - &begin[0];
        size_t i;

        /* Call all functions of the linker set */
        for (i = 0; i < n; ++i) {
                (*begin[i].func)();
        }

        /*
         * This will pull in the module.c and register its item in the
         * linker set "myset".  So g() can rely on f() being called first.
         */
        g();

        return (0);
}

In the linker command file of the GNU linker we need the following statement.

.rtemsroset : {
	KEEP (*(SORT(.rtemsroset.*)))

The KEEP() ensures that a garbage collection by the linker will not discard the content of this section. This would be normally the case since the linker set items are not referenced directly. The SORT() directive sorts the input sections lexicographically. Please note the lexicographical order of the .begin, .content and .end section name parts in the previous example which ensures that the position of the begin and end markers are right. The interesting part of linker map file of the previous example may look like this.

.rtemsroset     0x0000000001001990        0x4 load address 0x000000000002268c
 *(SORT(.rtemsroset.*))
 .rtemsroset.myset.begin
                0x0000000001001990        0x0 init.o
 .rtemsroset.myset.content
                0x0000000001001990        0x4 module.o
 .rtemsroset.myset.end
                0x0000000001001994        0x0 init.o

So what is the benefit of using linker sets to initialize modules? Currently in RTEMS all available managers (semaphore, message queue, barrier, etc.) are initialized since the initialization code doesn't know what is actually used by the application. With the linker set approach we need to initialize only those managers that are used by the application. In case an application uses message queues, then it must call rtems_message_queue_create(). In the module implementing this function we can place a linker set item and register the message queue handler constructor. Otherwise, in case the application doesn't use message queues, then there will be no reference to the rtems_message_queue_create() function and the constructor is not registered, thus nothing of the message queue handler will be in the final executable.

#2412 3 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Improved priority inheritance implementation

Description

Problem

The RTEMS mutexes implement only a very simple approximation of the priority inheritance protocol. The real priority of a thread is only restored once it releases its last mutex. Lets consider this scenario. We have a file system instance protected by one mutex (e.g. JFFS2) and a dynamic memory allocator protected by another mutex. A low priority thread performs writes some log data into a file, thus it acquires the file system instance mutex. The file system allocates dynamic memory. Now a high priority thread interrupts and tries to allocate dynamic memory. The allocator mutex is already owned, so the priority of the low priority thread is raised to the priority of the high priority thread. The memory allocation completes and the allocator mutex is released, since the low priority thread still owns the file system instance mutex it continues to execute with the high priority (the high priority thread is not scheduled). It may now perform complex and long file system operations (e.g. garbage collection, polled flash erase and write functions) with a high priority.

Functional requirements

  • The mutex shall use the priority inheritance protocol to prevent priority inversion. On SMP configurations OMIP shall be used.
  • The mutex shall allow vertical nesting (a thread owns multiple mutexes).
  • The mutex shall allow horizontal nesting (a thread waits for ownership of a mutex those owner waits for ownership of a mutex, and so on).
  • Threads from one scheduler instance shall wait in priority order. The highest priority thread shall be dequeued first.
  • The highest priority waiting thread of each scheduler instance shall wait in FIFO order.
  • The mutex shall provide an acquire operation with timeout.
  • In case a mutex is released, then the previous owner shall no longer use the priorities inherited by this mutex.
  • In case a mutex acquire operation timeout occurs, then the current owner of the mutex shall no longer use the priorities inherited by the acquiring thread.
  • The order of the mutex release operations may differ from the order of the mutex acquire operations.
  • Priority changes not originating due to the priority inheritance protocol shall take place immediately.
  • Deadlock shall be detected. In case a deadlock would occur an error status shall be returned or a fatal error shall be generated.
  • Deadlocks at application level shall not lead to a deadlock at operating system level.

Performance requirements

  • The mutex acquire operation shall use only object-specific locks in case the mutex is not owned currently.
  • The mutex release operation shall use only object-specific locks in case no threads wait for ownership of this mutex.

Invariants

  • A mutex shall be owned by at most one thread.
  • A thread shall wait for ownership of at most one mutex.

Possible implementation

Use a recursive data structure to determine the highest priority available to a thread for each scheduler instance, e.g.

typedef struct Thread_Priority_node {
  Priority_Control current_priority;
  Priority_Control real_priority;
  struct Thread_Priority_node *owner;
  RBTree_Node Node;
  RBTree_Control Inherited_priorities;
} Thread_Priority_node;

typedef struct {
  ...
  Thread_Priority_node *priority_nodes; /* One per scheduler instances */
  ...
} Thread_Control;

Initially a thread has a priority node reflecting its real priority. The Thread_Priority_node::owner is NULL. The Thread_Priority_node::current_priority is set to the real priority. The Thread_Priority_node::Inherited_priorities is empty.

In case the thread must wait for ownership of a mutex, then it enqueues its priority node in Thread_Priority_node::Inherited_priorities of the mutex owner.

In case the thread is dequeued from the wait queue of a mutex, then it dequeues its priority node in Thread_Priority_node::Inherited_priorities of the previous mutex owner (ownership transfer) or the current mutex owner (acquire timeout).

In case the minimum of Thread_Priority_node::real_priority and Thread_Priority_node::Inherited_priorities changes, then Thread_Priority_node::current_priority is updated. In case the Thread_Priority_node::owner its not NULL, the priority change propagates to the owner, and so on. In case Thread_Priority_node::current_priority changes, the corresponding scheduler is notified.

The biggest issue is the locking on SMP configurations in case of recursive minimum updates.

Somehow we must connect this to the scheduler helping protocol for OMIP. We may have to replace the return value based scheduler operations with a pre-context-switch action. Due to some recent implementation changes the run-time of the _Thread_Dispatch() function is no longer average-case performance critical.

#2423 3 years ago fixed unspecified Jeffrey Hill 11 months ago
Summary

rtems_iterate_over_all_threads lacks user callback private pointer pass through

Description

Typically when designing an API that calls a user callback there is a user private "void *" pointer transparently passed through to the user callback so that the user can access his private state inside of his callback without being forced to employ a global variable. A global variable doesnt work very well if there are multiple objects instances created each of them using the same method with rtems_iterate_over_all_threads. This type of "void *" private pointer is of course a standard approach allowing the users callback to behave much the same way as a virtual method in C++, but nevertheless retaining a compatible C based API.

An enhanced version of the API might look like this.

void rtems_iterate_over_all_threads_xxx( rtems_per_thread_routine routine, void * const pUserPrivatePassThrogh );

typedef void (*rtems_per_thread_routine_xxx)( Thread_Control *the_thread, void * const pUserPrivatePassThrogh );

The pUserPrivatePassThrogh is not used by the library; it is retained for the duration of the rtems_iterate_over_all_threads_xxx function only so that it can be passed through to the user's callback.

thanks for your consideration of this matter

#2428 3 years ago fixed tool/rsb Joel Sherrill Chris Johns 11 months ago
Summary

Add 4.12 Tool Target Configurations to RSB

Description

Even though so far the 4.11 and master tools don't need to be different, 4.12 configurations need to be added. This gives us space to:

+ (DONE) remove obsolete targets (avr, h8300, m32r) + (DONE) update versions + complete submission of patches and bump gdb + ...

#2441 3 years ago fixed unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

lpc1768 variants fail to build with error in gpio.c

Description

arm-lpc1768_mbed_ahb_ram_eth arm-lpc1768_mbed_ahb_ram arm-lpc1768_mbed

In file included from ../../../../../../../../rtems/c/src/lib/libbsp/arm/lpc176x/gpio/gpio.c:25:0: ../../../../../.././lpc1768_mbed_ahb_ram_eth/lib/include/bsp/gpio.h:28:4: error: #error "BSP_GPIO_PIN_COUNT or BSP_GPIO_PINS_PER_BANK is not defined."

#error "BSP_GPIO_PIN_COUNT or BSP_GPIO_PINS_PER_BANK is not defined."

../../../../../.././lpc1768_mbed_ahb_ram_eth/lib/include/bsp/gpio.h:32:4: error: #error "Invalid BSP_GPIO_PIN_COUNT or BSP_GPIO_PINS_PER_BANK."

#error "Invalid BSP_GPIO_PIN_COUNT or BSP_GPIO_PINS_PER_BANK."

../../../../../.././lpc1768_mbed_ahb_ram_eth/lib/include/bsp/gpio.h:41:5: error: division by zero in #if

#if GPIO_LAST_BANK_PINS > 0

../../../../../../../../rtems/c/src/lib/libbsp/arm/lpc176x/gpio/gpio.c:29:8: error: unknown type name 'lpc176x_registered_interrupt_function'

static lpc176x_registered_interrupt_function function_vector[

../../../../../../../../rtems/c/src/lib/libbsp/arm/lpc176x/gpio/gpio.c:30:3: error: 'LPC176X_RESERVED_ISR_FUNCT_SIZE' undeclared here (not in a function)

LPC176X_RESERVED_ISR_FUNCT_SIZE ];

../../../../../../../../rtems/c/src/lib/libbsp/arm/lpc176x/gpio/gpio.c:35:9: error: unknown type name 'lpc176x_gpio_direction'

const lpc176x_gpio_direction dir

#2442 3 years ago fixed bsps Joel Sherrill joel.sherrill@… 11 months ago
Summary

Remove avrtest BSP

Description

Remove the avr/avrtest BSP per the instructions at https://devel.rtems.org/wiki/Developer/Removing_a_BSP

#2443 3 years ago fixed unspecified Joel Sherrill Joel Sherrill <joel@…> 11 months ago
Summary

Remove AVR Architectural Port

Description

Remove the AVR port per the instructions at https://devel.rtems.org/wiki/Developer/Removing_a_Port.

All BSPa must be removed before the architectural port can be removed. These are tracked by the following tickets:

Rationale: The AVR port is incomplete and the largest AVR CPU models are just barely large enough to run RTEMS. This by itself is not enough to drop the port. However, the state of GCC for this target is poor. It is marginally maintained. Atmel maintains their own patch set independent of GCC. Plus they use their own small (and unique) C Library. This makes avr-rtems the only user of AVR+newlib. The target size is a challenge but that was why the port was initially interesting. It provided a real goal. But the tool state is painful for a port which is incomplete and has neither users nor anyone interested in actively maintaining it for GCC or RTEMS.

#2444 3 years ago fixed arch/m68k Joel Sherrill Aun-Ali Zaidi <admin@…> 11 months ago
Summary

Remove m68k/mvme136 BSP

Description

Remove the m68k/mvme136 BSP per the instructions at https://devel.rtems.org/wiki/Developer/Removing_a_BSP

Rationale: Although it is sad to see the BSP for the board that RTEMS was developed for be removed, this board was current in 1988-9. It has only 1MB RAM, 2 UARTS, and no NIC. It is unlikely to be available and without a NIC, isn't that useful.

#2445 3 years ago fixed arch/m68k Joel Sherrill Aun-Ali Zaidi <admin@…> 11 months ago
Summary

Remove m68k/sim68000 BSP

Description

Remove the m68k/sim68000 BSP per the instructions at ​https://devel.rtems.org/wiki/Developer/Removing_a_BSP

Rationale: This is a BSP for a simulator named BSVC (http://www4.ncsu.edu/~bwmott/bsvc/) that was never under a truly free license and has not been updated in a decade. Although a decent tool, it was extremely slow.

#2446 3 years ago fixed unspecified Joel Sherrill Joel Sherrill 11 months ago
Summary

Remove M32R Architectural Port

Description

Remove the M32R port per the instructions at ​https://devel.rtems.org/wiki/Developer/Removing_a_Port.

All BSPa must be removed before the architectural port can be removed. These are tracked by the following tickets:

#2447 - m32rsim

Rationale: The M32R port is incomplete, appears to have no users, and the CPU architecture is end-of-lifed.

#2447 3 years ago fixed bsps Joel Sherrill Aun-Ali Zaidi <admin@…> 11 months ago
Summary

Remove m32r/m32rsim

Description

Remove the m32r/m32rsim BSP per the instructions at https://devel.rtems.org/wiki/Developer/Removing_a_BSP

#2448 3 years ago fixed arch/mips Joel Sherrill 11 months ago
Summary

Remove mips/mongoose BSP

Description

Remove the m32r/m32rsim BSP per the instructions at ​https://devel.rtems.org/wiki/Developer/Removing_a_BSP

Rationale: This is a radiation hardened MIPS R3000 CPU that has only been used by a few missions. After discussions with various NASA and commercial engineers, we have learned that it is no longer considered an option for new missions and has not an option for a considerable length of time. The missions still underway (including New Horizons) are locked down on very old versions of their development infrastructure including hosts.

#2449 3 years ago fixed arch/arm Joel Sherrill Aun-Ali Zaidi <admin@…> 11 months ago
Summary

Remove arm/gba BSP

Description

Remove the arm/gba BSP per the instructions at ​​https://devel.rtems.org/wiki/Developer/Removing_a_BSP

Rationale: This BSP is for very old Nintendo hardware and required the use of either a simulator or hard to obtain programmable game cartridge. Nintendo was aggressive in shutting down resellers of those cartridges. There is no real console input and it is hard to automate testing. This was a useful BSP when there were few ARM BSPs but with the Pi, Beagle, etc. these days are long past.

#2450 3 years ago fixed arch/arm Joel Sherrill Aun-Ali Zaidi <admin@…> 11 months ago
Summary

Remove arm/nds

Description

Remove the arm/nds BSP per the instructions at ​​​https://devel.rtems.org/wiki/Developer/Removing_a_BSP

Rationale: This BSP is for very old Nintendo hardware and required the use of either a simulator or hard to obtain programmable game cartridge. Nintendo was aggressive in shutting down resellers of those cartridges. There is no real console input and it is hard to automate testing. This was a useful BSP when there were few ARM BSPs but with the Pi, Beagle, etc. these days are long past.

#2451 3 years ago fixed arch/arm Joel Sherrill Aun-Ali Zaidi <admin@…> 11 months ago
Summary

Remove arm/gp32 BSP

Description

Remove the arm/gp32 BSP per the instructions at ​​​​https://devel.rtems.org/wiki/Developer/Removing_a_BSP

Rationale: This BSP is for an open source alternative to the Gameboy Advance introduced in 2001. Wikipedia notes that 30K units were sold but it has been unavailable since 2007. This was a useful BSP when there were few ARM BSPs and the openness was interesting but with the Pi, Beagle, etc. these days are long past.

#2452 3 years ago fixed unspecified Joel Sherrill Joel Sherrill 11 months ago
Summary

Remove H8300 Architectual Port

Description

Remove the H8300 port per the instructions at ​https://devel.rtems.org/wiki/Developer/Removing_a_Port.

All BSPa must be removed before the architectural port can be removed. These are tracked by the following tickets:

#2453 - h8sim

Rationale: The h8 has been end of lifed. There do not appear to be any users based up questions and tickets filed. The architecture itself has issues which lead to breakages in gcc (which do get fixed though often slowly) and those same issues force us to disable some features like iconv in newlib. With no users, end of life, and tool issues, it is time to remove it.

#2453 3 years ago fixed bsps Joel Sherrill Aun-Ali Zaidi <admin@…> 11 months ago
Summary

Remove h8300/h8sim BSP

Description

Remove the h8300/h8sim BSP per the instructions at ​https://devel.rtems.org/wiki/Developer/Removing_a_BSP

#2454 3 years ago fixed unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

Warning in threadqops.c

Description

This may apply to the 4.11 branch as well. I am not sure.

../../../../../../rtems/c/src/../../cpukit/score/src/threadqops.c:202:29: warning: passing argument 1 of '_RBTree_Initialize_empty' from incompatible pointer type

This happens building many/all BSPs.

#2455 3 years ago fixed unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

Warning in spsimplesched02

Description

This may apply to the 4.11 branch as well. I am not sure.

../../../../../../../rtems/c/src/../../testsuites/sptests/spsimplesched02/init.c:84:5: warning: passing argument 1 of '_Objects_Name_to_id_u32' from incompatible pointer type

This happens building many/all BSPs.

#2457 3 years ago fixed arch/powerpc Joel Sherrill Aun-Ali Zaidi <admin@…> 11 months ago
Summary

Remove powerpc/ep1a BSP

Description

Remove the powerpc/ep1a BSP per the instructions at ​https://devel.rtems.org/wiki/Developer/Removing_a_BSP

Rationale: AFAIK this BSP was only used on a program supported by OAR. That program is no longer in active development and is completely frozen. If that situation changes, the BSP can be resurrected. It was introduced 10 years ago and has not has a modification other than general maintenance in the last four years.

#2458 3 years ago fixed arch/powerpc Joel Sherrill Ralph Holmes <ralph@…> 11 months ago
Summary

Remove powerpc/score603e BSP

Description

Remove the powerpc/score603e BSP per the instructions at ​https://devel.rtems.org/wiki/Developer/Removing_a_BSP

Rationale: AFAIK this BSP was only used on a program supported by OAR. That program is no longer in active development and is completely frozen. If that situation changes, the BSP can be resurrected. It was introduced in 1999 and has not has a modification other than general maintenance in the last six years.

#2459 3 years ago fixed rtems Sebastian Huber Sebastian Huber 11 months ago
Summary

Add rtems_chain_get_first_unprotected() to chain API

#2464 3 years ago wontfix tool Sebastian Huber 11 months ago
Summary

RSB: Tool patches use the RTEMS version

Description

In rtems/conifg/rtems-urls.bset the tool patches are set to an RTEMS version dependent directory. This makes re-use of the general purpose files quite difficult.

#2468 3 years ago fixed arch/i386 Joel Sherrill Sebastian Huber 11 months ago
Summary

Add Thread Local Storage (TLS) support on x86

Description

The x86 is one of the architectures which does not support Thread Local Storage. Each architecture requires target architecture specific support to provide this standard language feature.

Details on the implementation by the compiler may be found at http://wiki.osdev.org/Thread_Local_Storage.

Based on this information, I think a segment register needs to be added to the thread context and some hooks to the TLS implemented.

Architecture information on TLS implementation should be added to the CPU Supplement document as this is part of the ABI and context switch.

As part of effort, the documentation for the general procedure of adding target specific TLS support should be added to the porting guide or reviewed.

#2477 3 years ago fixed unspecified Sebastian Huber Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

Remove <rtems/debug.h>

Description

RTEMS has an API for dynamic debug support in <rtems/debug.h>. This feature is sparely used:

cpukit/sapi/src/debug.c:  rtems_debug_disable( RTEMS_DEBUG_ALL_MASK );
cpukit/sapi/src/debug.c:void rtems_debug_enable (
cpukit/sapi/src/debug.c:  rtems_debug_control  to_be_enabled
cpukit/sapi/src/debug.c:void rtems_debug_disable (
cpukit/sapi/src/debug.c:  rtems_debug_control  to_be_disabled
cpukit/sapi/src/debug.c:bool rtems_debug_is_enabled(
cpukit/sapi/src/debug.c:  rtems_debug_control  level
cpukit/rtems/include/rtems/rtems/regionimpl.h:    if ( rtems_debug_is_enabled( RTEMS_DEBUG_REGION ) ) \
cpukit/score/include/rtems/debug.h:typedef uint32_t   rtems_debug_control;
cpukit/score/include/rtems/debug.h:SCORE_EXTERN rtems_debug_control _Debug_Level;
cpukit/score/include/rtems/debug.h:void rtems_debug_enable(
cpukit/score/include/rtems/debug.h:  rtems_debug_control  to_be_enabled
cpukit/score/include/rtems/debug.h:void rtems_debug_disable(
cpukit/score/include/rtems/debug.h:  rtems_debug_control  to_be_disabled
cpukit/score/include/rtems/debug.h:bool rtems_debug_is_enabled(
cpukit/score/include/rtems/debug.h:  rtems_debug_control  level
c/src/lib/libbsp/shared/bootcard.c: *        - rtems_debug_enable( RTEMS_DEBUG_ALL_MASK );
c/src/lib/libbsp/shared/bootcard.c:    rtems_debug_enable( RTEMS_DEBUG_ALL_MASK );
c/src/lib/libbsp/shared/include/bootcard.h: *   - rtems_debug_enable( RTEMS_DEBUG_ALL_MASK )
testsuites/sptests/spregion_err01/init.c:  puts( "TA1 - rtems_debug_disable - RTEMS_DEBUG_REGION" );
testsuites/sptests/spregion_err01/init.c:  rtems_debug_disable( RTEMS_DEBUG_REGION );
testsuites/sptests/spregion_err01/init.c:  puts( "TA1 - rtems_debug_enable - RTEMS_DEBUG_REGION" );
testsuites/sptests/spregion_err01/init.c:  rtems_debug_enable( RTEMS_DEBUG_REGION );
testsuites/sptests/sp10/init.c:  puts( "Init - rtems_debug_is_enabled - is 0x1 set? No" );
testsuites/sptests/sp10/init.c:  is_set = rtems_debug_is_enabled( 0x1 );
testsuites/sptests/sp10/init.c:  puts( "Init - rtems_debug_enable - set 0x1" );
testsuites/sptests/sp10/init.c:  rtems_debug_enable(0x1);
testsuites/sptests/sp10/init.c:  puts( "Init - rtems_debug_is_enabled - is 0x1 set? Yes" );
testsuites/sptests/sp10/init.c:  is_set = rtems_debug_is_enabled( 0x1 );
testsuites/sptests/sp10/init.c:  puts( "Init - rtems_debug_disable - clear 0x1" );
testsuites/sptests/sp10/init.c:  rtems_debug_disable(0x1);
testsuites/sptests/sp10/init.c:  puts( "Init - rtems_debug_is_enabled - is 0x1 set? No" );
testsuites/sptests/sp10/init.c:  is_set = rtems_debug_is_enabled( 0x1 );

The only user is the Classic Region and it is only active in case RTEMS_DEBUG is defined. Due to the heap protection support which is also available in case RTEMS_DEBUG is defined, the expensive heap walks are superfluous.

We should remove this API entirely to simplify the code base.

#2487 3 years ago fixed tool/website Joel Sherrill Chris Johns 11 months ago
Summary

Should https://devel.rtems.org/wiki/TBR/Delete/SpecBuilder be Deleted?

Description

Chris.. you are the only one who knows if this tool is obsolete or not. Please do what you think is right with this page.

#2488 3 years ago fixed unspecified Joel Sherrill Ben Gras 11 months ago
Summary

Vagrant Scripts

Description

Ben.. someone posted on IRC that they used your scripts but the clones point to your personal repos which are out of date I am guessing.

Also is this discussed anywhere on the RTEMS wiki?

#2490 3 years ago wontfix tool/rsb Sebastian Huber Chris Johns 6 months ago
Summary

RSB: Use SHA512 instead of MD5

Description

Since MD5 is not a secure hash algorithm, we should change all hashes used by the RSB configuration files to use SHA512.

#2493 3 years ago fixed unspecified Sebastian Huber Joel Sherrill <joel.sherrill@…> 10 months ago
Summary

Remove notepads

Description

Notepads were marked as obsolete in #2265. Next step is to remove them. Documentation should mention that notepads are removed an list the alternatives, e.g. POSIX keys or thread local storage.

#2494 3 years ago fixed unspecified Sebastian Huber 11 months ago
Summary

Remove task variables

Description

Notepads were marked as obsolete in 4.11. Next step is to remove them. Documentation should mention that notepads are removed and list the alternatives, e.g. POSIX keys or thread local storage.

#2503 3 years ago fixed arch/powerpc Aun-Ali Zaidi joel.sherrill@… 11 months ago
Summary

mvme5500 BSP: Exception Handler uses deprecated Notepads.

Description

The MVME5500 BSP uses Notepads in its exception handler and #2493 removes them. This is obviously not portable and requires a rewrite.

#2509 3 years ago fixed tool/website Santosh Vattam Joel Sherrill 11 months ago
Summary

Should "https://devel.rtems.org/wiki/TBR/Delete/BSP_Template" be replaced?

Description

As part of the GCI Task https://codein.withgoogle.com/dashboard/task-instances/5106463810781184/?sp-page=1, the student has created a new page with a corrected template and placed it under "UserManual?" at: https://devel.rtems.org/wiki/TBR/UserManual/Submitting_a_BSP/BSP_Template Is it a good idea to replace the older page with the newly created page?

#2513 3 years ago fixed arch/m68k Joel Sherrill 11 months ago
Summary

Remove m68k/idp BSP

Description

Remove the m68k/idp BSP per the instructions at ​https://devel.rtems.org/wiki/Developer/Removing_a_BSP

#2515 3 years ago fixed unspecified Gedare Gedare 11 months ago
Summary

i386 score/libcpu API Layering Violation

Description

The file libcpu/i386/cpu.h provides functions referenced in rtems/score/i386.h Relatedly, libcpu/i386/cpu.h is the only other consumer than score/cpu.h of the score/interrupts.h. The libcpu/i386/cpu.h should be refactored into rtems/score/i386.h, which could also then subsume rtems/score/interrupts.h.

#2527 3 years ago wontfix tool Joel Sherrill Chris Johns 11 months ago
Summary

Move pc386/tools/bin2boot to rtems-tools

Description

Per discussion with Chris. Begin to eliminate BSP specific tools.

#2529 3 years ago fixed arch/arm Sebastian Huber Sebastian Huber 11 months ago
Summary

BSP for the Atmel SAM V71/V70/E70/S70 chip platform

Description

http://www.atmel.com/products/microcontrollers/arm/sam-v-mcus.aspx

#2536 3 years ago fixed tool/rsb Sebastian Huber Chris Johns <chrisj@…> 11 months ago
Summary

RSB allows use of insecure hash algorithms like MD5 and SHA1

Description

Support for these hashes should be removed. Hashes should be mandatory.

#2537 3 years ago fixed unspecified Joel Sherrill Joel Sherrill 11 months ago
Summary

Use Newlib exec*() variants and remove RTEMS versions

Description

In reviewing RTEMS+newlib POSIX conformance, I noticed that our newlib configuration does include the exec*() variants. All of these call _execve() which we already provided.

This ticket is just to explain the removal of the RTEMS copies. The functional behavior to the user is still to return ENOSYS.

#2542 3 years ago fixed bsps Joel Sherrill joel.sherrill@… 11 months ago
Summary

Review cxx_iostream size change per function-section changes

Description

It looks like some BSPs with their own linkcmds may have shrunk too much. Norm appears to be 50% while some went to 75-80%. A second look after catching the pattern indicates that the KEEP() section requirements in the linker scripts were not correct and it was missed.

Rather than reverting a bunch of patches, this ticket is to review all function-section patches from this one back in time for cxx_iostream shrinking too much.

commit 6d21c13e5094d490280a941cf0e8333f91f85715 Author: Ralph Holmes <ralph@…> Date: Sat Jan 23 21:15:40 2016 +0000

powerpc/gen5200: Add per-section compilation and linking support.

For the brs5l BSP variant:

#2543 3 years ago fixed unspecified Joel Sherrill Joel Sherrill 11 months ago
Summary

Obsolete gen68302 BSP

Description

Delete the gen68302 BSP after 4.11 and before 4.12.

#2544 3 years ago duplicate unspecified Joel Sherrill Joel Sherrill 11 months ago
Summary

Osolete m68k/ods68302

Description

Obsolete and remove the ods68302 BSP before 4.12.

#2545 3 years ago fixed unspecified Joel Sherrill Joel Sherrill 11 months ago
Summary

Obsolete mbx8xx BSP

Description

Obsolete and remove.

#2546 3 years ago fixed arch/m68k Joel Sherrill Joel Sherrill 11 months ago
Summary

Obsolete idp BSP

Description

Obsolete and remove the m68k/idp BSP before the 4.12 release.

#2553 3 years ago fixed arch/powerpc Nick Withers Sebastian Huber 11 months ago
Summary

[mvme3100] boot_card() broken by 37030e38

Description

Backtrace with 37030e38* (with a fatal exception handler installed):

#0  fatal_extension (the_source=INTERNAL_ERROR_CORE, is_internal=true, the_error=23) at init.c:425
#1  0x000a6d18 in _User_extensions_Iterate (arg=arg@entry=0x1ab6348, visitor=0xa6c70 <_User_extensions_Fatal_visitor>) at ../../../../../../../rtems/c/src/../../cpukit/score/src/userextiterate.c:155
#2  0x000a1c90 in _User_extensions_Fatal (error=23, is_internal=true, source=INTERNAL_ERROR_CORE) at ../../cpukit/../../../mvme3100/lib/include/rtems/score/userextimpl.h:254
#3  _Terminate (the_source=the_source@entry=INTERNAL_ERROR_CORE, is_internal=is_internal@entry=true, the_error=the_error@entry=23) at ../../../../../../../rtems/c/src/../../cpukit/score/src/interr.c:44
#4  0x0007ad40 in RTEMS_Malloc_Initialize (areas=areas@entry=0x1ab6398, area_count=area_count@entry=1, extend=extend@entry=0x0 <preload>)
    at ../../../../../../../rtems/c/src/../../cpukit/libcsupport/src/malloc_initialize.c:53
#5  0x0005cf84 in bsp_work_area_initialize_default (area_size=<optimized out>, area_begin=<optimized out>) at ../../../../../.././mvme3100/lib/include/bsp/bootcard.h:183
#6  bsp_work_area_initialize () at ../../../../../../../../../rtems/c/src/lib/libbsp/powerpc/mvme3100/../../powerpc/shared/startup/bspgetworkarea.c:23
#7  0x0005cec4 in boot_card (cmdline=<optimized out>) at ../../../../../../../../../rtems/c/src/lib/libbsp/powerpc/mvme3100/../../shared/bootcard.c:80
#8  0x00003294 in __rtems_entry_point () at ../../../../../../../../../rtems/c/src/lib/libbsp/powerpc/mvme3100/start/start.S:89

If I reverse the changes to c/src/lib/libbsp/shared/bootcard.c it works again.

* With RSB e3b9fb68 and the following RTEMS patches:

#2554 3 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

New watchdog handler implementation

Description

Background

The watchdog handler uses delta chains. The insert operation has a O(n) worst-case time complexity with n being the count of watchdogs in the delta chain. In each step of the insert operation, the SMP lock of the corresponding watchdog header is acquired and released. The profiling data obtain by test program smptests/smpwakeafter01 showed that the current implementation leads to unacceptable latencies, thus it should be replaced by something else.

The use cases for the watchdog handler fall roughly into two categories.

  • Timeouts - used to detect if some operations needs more time than expected. Since the unexpected happens hopefully rarely, timeout timers are usually removed before they expire. The critical operations are insert and removal. They are important for the performance of a network stack.
  • Timers - used to carry out some work in the future. They usually expire and need a high resolution. An example user is a time driven scheduler, e.g. rate-monotonic or EDF.

One approach is to use a red-black tree with the expiration time as the key. This leads to O(log(n)) worst-case insert and removal operations. For each operation it is sufficient to acquire and release the lock only once. The drawback is that a 64-bit integer type must be used for the intervals to avoid a potential overflow of the key values. With a system tick interval of 1ns the system could run more than 500 years before an overflow happens. The EDF scheduler would also profit from a 64-bit interval representation, see #2173.

An alternative is the use of a timer wheel based algorithm which is used in Linux and FreeBSD for example. A timer wheel based algorithm offers O(1) worst-case time complexity for insert and removal operations. The drawback is that the run-time of the watchdog tick procedure is somewhat unpredictable due to the use of a hash table or cascading.

Which approach should we choose? Since the watchdog serves the timeout and timer services in RTEMS we have to make some trade-offs. We recommend to use the red-black tree approach which offers a more predictable run-time behaviour and sacrifice the constant insert and removal operations offered by the timer wheel algorithms, see also https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf. We can reuse the red-black tree support already used for the thread priority queues.

The new watchdog handler implementation is a prerequisite to eliminate the Giant lock in the Classic Timer manager.

Implementation

Change the _Watchdog_Ticks_since_boot to a 64-bit integer type. Keep the Watchdog_Interval at 32-bit for backward compatibility. Replace the delta chains with a red-black tree. Use the ticks for timers with a relative expiration time. Use struct timespec or struct bintime for timers with an absolute expiration time. This has the benefit that we do not have to adjust the data structures in case the absolute time changes, e.g. due to NTP. It simplifies the POSIX timer services, since no conversion to ticks is necessary.

#2555 3 years ago fixed score Sebastian Huber Sebastian Huber 9 months ago
Summary

Eliminate the Giant lock

Description

Background

The standard approach to turn a uni-processor operating system into an SMP-capable operating system is to encapsulate virtually the complete operating system state and protect it by one global recursive lock - the Giant lock. Thus, at most one processor can modify the operating system state at a time. Under Giant lock protection interrupt disable/enable critical sections still work. This approach is easy to realize and leads to something that runs on SMP with a minimal effort. Unfortunately, such an operating system does not scale with the processor count and offers very poor performance. It is quite useless for real applications.

The first steps to get rid of the Giant lock are tackled with the introduction of fine grained locking for the scheduler, watchdog handler, timestamps, thread queues, events, semaphores and message queues. The Giant lock is still used in a couple of places, e.g. all other objects using thread queues, thread life cycle changes (termination, restart) and scheduler changes. It is a straight forward task to eliminate it entirely, but it is also somewhat labour intensive since a lot of code must be changed.

Implementation

Eliminate all remaining code areas that use

  • _ISR_Disable(),
  • _ISR_Enable(), and
  • _ISR_Flash().

Direct users of these macros are

  • _Chain_Append(),
  • _Chain_Extract(),
  • _Chain_Get(),
  • _Chain_Insert(), and
  • _Chain_Prepend().

Each spot must be dealt with individually. Once this is done, delete these macros since they are now superfluous. Rename _ISR_Disable_without_giant() into _ISR_Locale_disable(). Rename _ISR_Enable_without_giant() into _ISR_Locale_enable().

Eliminate all remaining code areas that use

  • _Thread_Disable_dispatch() and
  • _Thread_Enable_dispatch().

A prominent user of this functions is _Objects_Get(). The following components are affected by these functions

  • Classic barrier handler,
  • Classic dual-ported memory handler,
  • Classic message queue handler,
  • Classic partition handler,
  • Classic rate-monotonic handler,
  • Classic region handler,
  • Classic semaphore handler,
  • Classic timer handler,
  • extension handler,
  • IO manager,
  • multi-processing management,
  • objects management,
  • POSIX barrier handler,
  • POSIX condition handler,
  • POSIX key handler,
  • POSIX message queue handler,
  • POSIX mutex handler,
  • POSIX rwlock handler,
  • POSIX semaphore handler,
  • POSIX spinlock handler,
  • POSIX timer handler,
  • signals,
  • thread cancellation,
  • thread life-cycle changes, and
  • thread scheduler changes.

Once this is done, delete _Thread_Disable_dispatch() and _Thread_Enable_dispatch(). As a side-effect the Giant lock will be removed.

#2556 3 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Implement the O(m) Independence-Preserving Protocol (OMIP)

Description

Background

The O(m) Independence-Preserving Protocol (OMIP) is a generalization of the priority inheritance protocol to clustered scheduling which avoids the non-preemptive sections present with priority boosting. The m denotes the number of processors in the system. Its implementation requires an extension of the scheduler helping protocol already used for the MrsP semaphores. However, the current implementation of the scheduler helping protocol has two major issues, see Catellani, Sebastiano, Luca Bonato, Sebastian Huber, and Enrico Mezzetti: Challenges in the Imple- mentation of MrsP. In Reliable Software Technologies - Ada-Europe 2015, pages 179–195, 2015. Firstly, the run-time of some scheduler operations depend on the size of the resource dependency tree. Secondly, the scheduler operations of threads which don't use shared resources must deal with the scheduler helping protocol in case an owner of a shared resource is somehow involved.

To illustrate the second issue, let us look at the following example. We have a system with eight processors and two L2 caches. We assign processor 0 to a partition P for latency sensitive real-time tasks (e.g. sensor and actuator handling), processors 1, 2 and 3 are assigned to a cluster CA and the remaining processors are assigned to a cluster CB for soft real-time worker tasks. The worker tasks use a shared resource, e.g. a file system for data storage. Let us suppose a task R of partition P sends a message to the workers. This may make a waiting worker ready, which in turn pre-empts the owner of a shared resource. In this case the scheduler helping protocol takes action and is carried out by the task R. This contradicts the intended isolation of scheduler instances.

The reason for this unfortunate coupling is a design issue of the scheduler helping protocol implementation. Some scheduler operations may return a thread in need of help. For example, if a thread is unblocked which pre-empts an owner of a shared resource, then the pre-empted thread is returned. Once a thread in need of help is returned, the ask for help operation of the scheduler is executed. An alternative to this return value based approach is the introduction of a pre-emption intervention during thread dispatching. Threads taking part in the scheduler helping protocol indicate this with a positive resource count value. In case a thread dispatch occurs and pre-empts an owner of a shared resource, the scheduler ask for help operation is invoked. So, the work is carried out on behalf of the thread which takes part in the scheduler helping protocol.

To overcome the first issue, an improved resource dependency tracking is required. One approach is to use a recursive red-black tree based data structure, see #2412.

Implementation

There are several steps necessary to implement OMIP.

  • Introduce per-scheduler locks.
  • Enable context switches with interrupts enabled.
  • Add a pre-emption intervention to the thread dispatch.
  • Add a table for priority nodes to the thread control block. For each scheduler instance there is one priority node.
  • Update the table in case the thread blocks on a resource, a timeout while waiting for a resource occurs, or ownership of a resource is transferred to the thread.
  • Use this table in the pre-emption intervention.
  • Update the MrsP implementation to the new infrastructure.

Currently, only one scheduler lock for all scheduler instances is used. This simplified the MrsP implementation and due to the presence of a Giant lock, this was not an issue. With the elimination of the Giant lock, however, we need one scheduler lock per scheduler instance to really profit from a decoupled system due to clustered scheduling.

The current implementation of thread dispatching has some implications with respect to the interrupt latency. It is crucial to preserve the system invariant that a thread can execute on at most one processor in the system at a time. This is accomplished with a boolean indicator in the thread context. The processor architecture specific context switch code will mark that a thread context is no longer executing and waits that the heir context stopped execution before it restores the heir context and resumes execution of the heir thread (the boolean indicator is basically a TTAS lock). So, there is one point in time in which a processor is without a thread. This is essential to avoid cyclic dependencies in case multiple threads migrate at once. Otherwise some supervising entity is necessary to prevent deadlocks. Such a global supervisor would lead to scalability problems so this approach is not used. Currently the context switch is performed with interrupts disabled. Thus in case the heir thread is currently executing on another processor, the time of disabled interrupts is prolonged since one processor has to wait for another processor to make progress.

If we add pre-emption intervention to the thread dispatch sequence, then there is an even greater need to avoid this issue with the interrupt latency. Interrupts normally store the context of the interrupted thread on its stack. In case a thread is marked as not executing, we must not use its thread stack to store such an interrupt context. We cannot use the heir stack before it stopped execution on another processor. If we enable interrupts during this transition, then we have to provide an alternative thread independent stack for interrupts in this time frame.

The pre-emption intervention should be added to _Thread_Do_dispatch() before the heir is read and perform the following pseudo-code actions.

pre_emption_intervention(executing):
	if executing.resource_count > 0:
		executing.lock()
		if executing.is_ready():
			for scheduler in executing.schedulers:
				scheduler.lock()
			if !executing.is_scheduled():
				for scheduler in executing.schedulers:
					scheduler.ask_for_help(executing)
			for scheduler in executing.schedulers:
				scheduler.unlock()
		else if executing.active_help_level > 0:
			idle.use(executing.scheduler_node)
		executing.unlock()

The scheduler help operation affects multiple scheduler instances. In terms of locking we have only two options,

  • use a global scheduler lock, or
  • obtain multiple per-scheduler locks at once.

A global scheduler lock is not an option. To avoid deadlocks obtain the per-scheduler locks in a fixed order. However, in this case the per-scheduler locks will observe different worst-case and average-case acquire times (depending on the order).

Use a recursive data structure to determine the highest priority available to a thread for each scheduler instance, e.g.

typedef struct Thread_Priority_node {
	Priority_Control current_priority;
	Priority_Control real_priority;
	struct Thread_Priority_node *owner;
	RBTree_Node Node;
	RBTree_Control Inherited_priorities;
} Thread_Priority_node;

typedef struct {
	...
	Thread_Priority_node *priority_nodes; /* One per scheduler instances */
	...
} Thread_Control;

Initially a thread has a priority node reflecting its real priority. The Thread_Priority_node::owner is NULL. The Thread_Priority_node::current_priority is set to the real priority. The Thread_Priority_node::Inherited_priorities is empty.

In case the thread must wait for ownership of a mutex, then it enqueues its priority node in Thread_Priority_node::Inherited_priorities of the mutex owner.

In case the thread is dequeued from the wait queue of a mutex, then it dequeues its priority node in Thread_Priority_node::Inherited_priorities of the previous mutex owner (ownership transfer) or the current mutex owner (acquire timeout).

In case the minimum of the Thread_Priority_node::real_priority and the Thread_Priority_node::Inherited_priorities changes, then Thread_Priority_node::current_priority is updated. In case the Thread_Priority_node::owner its not NULL, the priority change propagates to the owner, and so on. In case Thread_Priority_node::current_priority changes, the corresponding scheduler is notified.

Use the thread lock to protect the priority nodes.

#2557 3 years ago fixed doc Amar Takhar Amar Takhar 11 months ago
Summary

Add word splitting to print output

#2559 3 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Delete the EXTERN pattern

Description

Change the following pattern: some.h:

#ifndef SOME_XYZ_EXTERN
#define SOME_XYZ_EXTERN extern
#endif
SOME_XYZ_EXTERN type xyz;

some_xyz.c:

#define SOME_XYZ_EXTERN
#include <some.h>

into: some.h:

extern type xyz;

some_xyz.c:

#include <some.h>
type xyz;

See discussion:

https://lists.rtems.org/pipermail/devel/2016-January/013506.html

Update Developer/Coding/Conventions accordingly.

#2560 3 years ago fixed arch/arm Sebastian Huber 11 months ago
Summary

smdk2410 is broken due to gp32 removal

Description

The smdk2410 BSPs use files of the removed gp32 BSP.

[f2a228b2cb5ce376c56ae8d767084b92f2822af0/rtems]

#2576 3 years ago fixed arch/arm Joel Sherrill Joel Sherrill <joel@…> 11 days ago
Summary

arm/lpc176x: linker script update (add KEEP() sections)

Description

This BSP's linker script does not include KEEP() directives and thus cannot have per-function and per-data element section support enabled.

The preferred solution is to convert the BSP to use a shared base linker script. The acceptable solution is to add the proper KEEP directives to the existing linker script(s).

Shared linker scripts for the arm, m68k, and sparc have the proper KEEP sections and can serve as examples.

#2606 3 years ago fixed posix Sebastian Huber Sebastian Huber 11 months ago
Summary

alarm() uses seconds watchdog and thus is affected by clock changes

Description

alarm() uses _Watchdog_Insert_seconds() and thus is affected by clock changes, e.g. via _TOD_Set(). This is wrong. The POSIX documentation is not that clear since it talks only about "realtime seconds". However, the FreeBSD implementation uses the uptime. This is also in line with the RTEMS ualarm() and nanosleep().

#2608 3 years ago fixed posix Joel Sherrill Gedare 10 months ago
Summary

POSIX Condition Variables Clock Attribute Support

Description

I am beginning to add support for the clock attribute to POSIX condition variables.

http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_condattr_getclock.html

Since the clock can't be a CPU time clock, that leaves CLOCK_MONOTONIC and CLOCK_REALTIME. The thread queue is based on CLOCK_MONOTONIC and does not have an option to use CLOCK_REALTIME. Threads and timers waiting on CLOCK_REALTIME should be impacted by time of day changes.

https://docs.google.com/document/d/1GsGer0t84p-nUfZFim4Ty0LTDYNhgKBvlwip_gLQjTY/edit?usp=sharing is a Google doc with my notes so far in it on POSIX clocks. I will move it to the Wiki as it turns into something more concrete than notes and reflects plans/code.

So the first issue is how best to alter the thread queue to support using either clock source? And what does that do to the current ticks based API since you proposed different time representations for the ticks (relative/monotonic) and seconds (absolute/realtime) structures?

#2617 3 years ago fixed score Joel Sherrill Sebastian Huber 11 months ago
Summary

rtems_heap_allocate_aligned_with_boundary() body and prototype inconsistent

Description

The first parameter is size_t in the .h and uintptr_t in the body. This resulted in a compiler error on the m32c. But it is an inconsistency which should be fixed even if no architecture complained.

The malloc.h header file has this:

void *rtems_heap_allocate_aligned_with_boundary(

size_t size, uintptr_t alignment, uintptr_t boundary

);

malloc_deferred.c has this:

void *rtems_heap_allocate_aligned_with_boundary(

uintptr_t size, uintptr_t alignment, uintptr_t boundary

)

#2624 3 years ago fixed tool/newlib Sebastian Huber Needs Funding 9 days ago
Summary

Fix the year 2038 problem

Description

RTEMS uses currently a signed 32-bit integer for time_t on Newlib. Thus, it is affected by the year 2038 problem. There are only 22 years left and this time span is within the realistic time frame of some RTEMS applications that are developed now.

The time_t should be changed to int64_t in Newlib. To make sure that all integer operations are carried out properly I suggest to temporarily do this

{{{#include <sys/_stdint.h>

typedef struct {

int64_t _val;

} time_t;

static inline time_t _time_add(time_t a, time_t b) {

time_t r = { a._val + b._val }; return r;

}

static inline time_t _time_sub(time_t a, time_t b) {

time_t r = { a._val - b._val }; return r;

}

static inline time_t _time_mul(time_t a, time_t b) {

time_t r = { a._val * b._val }; return r;

}

static inline time_t _time_div(time_t a, time_t b) {

time_t r = { a._val / b._val }; return r;

} }}}

Make sure that RTEMS and Newlib build with this. Add test cases to highlight the time_t integer limits.

#2625 3 years ago fixed posix Sebastian Huber Sebastian Huber 11 months ago
Summary

Use one lookup tree per-thread for the POSIX keys

Description

Currently a global lookup tree is used for all the POSIX key/value pairs. On SMP configurations this is a bottleneck. Use one lookup tree per thread instead.

#2626 3 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Unify thread cancel/join and delete

Description

The rtems_task_delete() is basically a pthread_cancel() plus pthread_join(). Unify the implementation and introduce a _Thread_Cancel() and _Thread_Join() to be used by both APIs. Get rid of the Giant lock for thread delete.

#2627 3 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Fix CPU time used for threads on SMP

Description

The CPU time used of a thread is currently maintained per-processor mostly during _Thread_Dispatch(). However, on SMP configurations the actual processor of a thread is difficult to figure out since thread dispatching is a highly asynchronous process (e.g. via inter-processor interrupts). Only the intended processor of a thread is known to the scheduler easily. Do the CPU usage accounting during thread heir updates in the context of the scheduler operations. Provide a function to get the CPU usage of a thread using proper locks to get a consistent value.

#2628 3 years ago wontfix score Sebastian Huber Sebastian Huber 10 months ago
Summary

Avoid home-grown condition variable implementation in the Classic Regions

Description

The Classic Region manager enables users to wait until memory is available to satisfy an allocation request. This is done through special purpose code that basically implements a condition variable.

#2631 3 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Use an ISR lock to protect the state of Classic Rate Monotonic objects

Description

The state of Classic Rate Monotonic is currently protected by the Giant lock and ISR disable sections. Use a per-object ISR lock to protect state changes instead.

#2632 3 years ago fixed tool/rsb Joel Sherrill Chris Johns 11 months ago
Summary

rtems-tester failure

Description

CentOS 7 on master

$ ../rtems-tools/tester/rtems-test --rtems-tools=/home/joel/rtems-4.11-work/tools/4.12 --rtems-bsp=sis find . -name "*hello.exe" RTEMS Testing - Tester, 4.12 (a5d243d3f8e2)

Command Line: ../rtems-tools/tester/rtems-test --rtems-tools=/home/joel/rtems-4.11-work/tools/4.12 --rtems-bsp=sis ./sparc-rtems4.12/c/sis/testsuites/samples/hello/hello.exe Python: 2.7.5 (default, Nov 20 2015, 02:00:19) [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)]

[1/1] p:0 f:0 t:0 i:0 | sparc/sis: hello.exe Traceback (most recent call last):

File "../rtems-tools/tester/rtems-test", line 40, in <module>

rt.test.run()

File "/data/home/joel/rtems-4.11-work/rtems-tools/tester/rt/test.py", line 287, in run

tst.reraise()

File "/data/home/joel/rtems-4.11-work/rtems-tools/tester/rt/test.py", line 123, in reraise

raise (self.result[0], self.result[1], self.result[2])

TypeError?: init() takes exactly 2 arguments (1 given)

#2633 3 years ago fixed network/legacy joguin Sebastian Huber 11 months ago
Summary

waf build failed for rtems-libbsd

Description

The rtems-libbsd failed when building with waf. Here is the output:

[488/845] Compiling freebsd/sys/kern/subr_taskqueue.c In file included from /home/josh/development/rtems/bsps/4.12/i386-rtems4.12/pc386/lib/include/rtems/score/threadimpl.h:36:0,

from ../../freebsd/sys/kern/subr_sleepqueue.c:91:

/home/josh/development/rtems/bsps/4.12/i386-rtems4.12/pc386/lib/include/rtems/score/watchdogimpl.h: In function '_Watchdog_Per_CPU_insert_relative': /home/josh/development/rtems/bsps/4.12/i386-rtems4.12/pc386/lib/include/rtems/score/watchdogimpl.h:356:18: error: 'struct <anonymous>' has no member named '_bsd_ticks'; did you mean 'ticks'?

cpu->Watchdog.ticks + ticks

In file included from ../../freebsd/sys/kern/subr_sleepqueue.c:62:0: ../../freebsd/sys/kern/subr_sleepqueue.c: In function 'sleepq_set_timeout': ../../freebsd/sys/kern/subr_sleepqueue.c:424:29: error: 'Thread_Timer_information {aka struct <anonymous>}' has no member named 'state'

BSD_ASSERT(executing->Timer.state == WATCHDOG_INACTIVE);

../../freebsd/sys/kern/subr_sleepqueue.c:424:2: note: in expansion of macro 'BSD_ASSERT'

BSD_ASSERT(executing->Timer.state == WATCHDOG_INACTIVE); ~

../../freebsd/sys/kern/subr_sleepqueue.c:425:2: error: too many arguments to function '_Watchdog_Initialize'

_Watchdog_Initialize(&executing->Timer, sleepq_timeout, ~

In file included from /home/josh/development/rtems/bsps/4.12/i386-rtems4.12/pc386/lib/include/rtems/score/threadimpl.h:36:0,

from ../../freebsd/sys/kern/subr_sleepqueue.c:91:

/home/josh/development/rtems/bsps/4.12/i386-rtems4.12/pc386/lib/include/rtems/score/watchdogimpl.h:178:27: note: declared here

RTEMS_INLINE_ROUTINE void _Watchdog_Initialize(

~

Waf: Leaving directory `/home/josh/development/rtems/rtems-libbsd/build/i386-rtems4.12-pc386' Build failed

#2634 3 years ago fixed arch/i386 Joel Sherrill Pavel Pisa <ppisa@…> 11 months ago
Summary

New warning in pc386 VESA driver

Description

Pavel.. can you look into this?

./../../../../../../../rtems/c/src/lib/libbsp/i386/pc386/console/fb_vesa_rm.c: In function 'find_mode_using_EDID': ../../../../../../../../rtems/c/src/lib/libbsp/i386/pc386/console/fb_vesa_rm.c:502:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]

if (*(uint16_t*)&edid.STI[index] == EDID_STI_DescriptorUnused) ~

#2638 3 years ago fixed unspecified Joel Sherrill Joel Sherrill <joel@…> 11 months ago
Summary

pc386: ld -r issue with per function sections

Description

The pc386 BSP has an issue with "ld -r" when function-sections is enabled which does not seem to occur on any other BSP. The same lines were added to the custom .cfg file as on other BSPs. It is unknown at this point whether this is an x86 specific "ld -r" issue or a pc386 build configuration issue.

Per-function-section linking is disabled until this is addressed.

i386-rtems4.12-gcc --pipe -B../../../../../.././lib/ -B../../../../../.././pc386/lib/ -specs bsp_specs -qrtems -mtune=i386 -O2 -g -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -qnolinkcmds -nostdlib -r -Wl,--gc-sections -Wl,-Ttext,0x00100000 -o ne2000.rel ne2000_rel-ne2000.o /data/home/joel/rtems-4.11-work/tools/4.12/bin/../lib/gcc/i386-rtems4.12/6.0.0/../../../../i386-rtems4.12/bin/ld: gc-sections requires either an entry or an undefined symbol collect2: error: ld returned 1 exit status

#2641 3 years ago fixed build aurelio Chris Johns 6 months ago
Summary

configure: enable-rtemsbsp doesn't warn if bsp does not exist

Description

When running configure with an incorrect bsp name the script does not cause an error. You can ever run make without getting any warning message.

The script should check the name of the bsp and continue only if it is a valid bsp. On the other hand if the bsp name given by the user is invalid the script should prompt a message.

#2644 3 years ago fixed tool/rsb Joel Sherrill 11 months ago
Summary

sis does not run on gdb 7.11 but does on gdb 7.9

Description

I know we reported this on the gdb list but we should have a ticket.

Neither gdb nor run works for sis on gdb 4.11. Checked against RTEMS 4.11 tools (gdb 4.9) and it will run sis.

Not sure about other simulators.

#2649 3 years ago fixed tool/rsb Chris Johns Chris Johns 11 months ago
Summary

RSB remove 4.11, 4.10 and 4.9 from the master branch.

Description

Having 4.11 on master is confusing users as they build 4.11 tool on master and there may be issues in 4.11 configurations fixed on the 4.11 branch.

Leave 4.9 and 4.10 until they are branched off master. We will make these branches once 4.12 is stable again.

#2663 3 years ago wontfix arch/i386 Joel Sherrill Sebastian Huber 11 months ago
Summary

pc386 BSP has complex dependencies

Description

In 4.11, the minimum executable did not include open() and close() because the methods rtems_libio_post_driver() and rtems_libio_exit() were not included in the executable. On the master, these two methods are showing up in minimum and pulling in these methods.

The dependency chain used to be if the console driver was installed, we needed to open and close stdin, stdout, and stderr. Now even without the console configured these are included.

FWIW the minimum size looks pretty good on the master for sis. Fixing this would likely drop it at least another 5%.

#2664 3 years ago duplicate score Joel Sherrill Sebastian Huber 11 months ago
Summary

spclock_err02

Description

New test failure on sis but likely all targets.

* BEGIN OF TEST SPCLOCK_ERR 2 * TA1 - rtems_io_close - RTEMS_INVALID_NUMBER TA1 - rtems_io_control - RTEMS_INVALID_NUMBER TA1 - rtems_io_initialize - RTEMS_INVALID_NUMBER TA1 - rtems_io_open - RTEMS_INVALID_NUMBER TA1 - rtems_io_read - RTEMS_INVALID_NUMBER TA1 - rtems_io_write - RTEMS_INVALID_NUMBER TA1 - rtems_clock_set - 23:59:59 12/31/2000 - RTEMS_SUCCESSFUL TA1 - rtems_clock_get_tod - 00:00:00 01/01/2001 - RTEMS_SUCCESSFUL TA1 - rtems_clock_set - 23:59:59 12/31/1999 - RTEMS_SUCCESSFUL TA1 - rtems_clock_get_tod - 00:00:00 01/01/2000 - RTEMS_SUCCESSFUL assertion "ticks < 0x400000000" failed: file "../../cpukit/../../../sis/lib/include/rtems/score/watchdogimpl.h", line 316, function: _Watchdog_Ticks_from_timespec

Breakpoint 1, _Terminate (the_source=the_source@entry=RTEMS_FATAL_SOURCE_ASSERT,

is_internal=is_internal@entry=false, the_error=the_error@entry=33694096) at ../../../../../../rtems/c/src/../../cpukit/score/src/interr.c:36

36 { (gdb) bt #0 _Terminate (the_source=the_source@entry=RTEMS_FATAL_SOURCE_ASSERT,

is_internal=is_internal@entry=false, the_error=the_error@entry=33694096) at ../../../../../../rtems/c/src/../../cpukit/score/src/interr.c:36

#1 0x0200aed4 in rtems_fatal (source=source@entry=RTEMS_FATAL_SOURCE_ASSERT,

error=error@entry=33694096) at ../../../../../../rtems/c/src/../../cpukit/sapi/src/fatal2.c:34

#2 0x02004a9c in assert_func (

file=file@entry=0x201a650 "../../cpukit/../../../sis/lib/include/rtems/score/watchdogimpl.h", line=line@entry=316, func=func@entry=0x201a6d0 <func.3277> "_Watchdog_Ticks_from_timespec", failedexpr=failedexpr@entry=0x201a638 "ticks < 0x400000000") at ../../../../../../rtems/c/src/../../cpukit/libcsupport/src/assert.c:52

#3 0x0200bbf8 in _Watchdog_Ticks_from_timespec (ts=0x2022210)

at ../../cpukit/../../../sis/lib/include/rtems/score/watchdogimpl.h:316

#4 _TOD_Set_with_timestamp (tod_as_timestamp=tod_as_timestamp@entry=0x2022280)

at ../../../../../../rtems/c/src/../../cpukit/score/src/coretodset.c:40

#5 0x02009880 in rtems_clock_set (tod=tod@entry=0x2022304)

at ../../../../../../rtems/c/src/../../cpukit/rtems/src/clockset.c:42

#6 0x02001818 in Init (argument=<optimized out>)

at ../../../../../../../rtems/c/src/../../testsuites/sptests/spclock_err02/init.c:93

#7 0x0200fcbc in _Thread_Entry_adaptor_numeric (executing=0x201fb90)

at ../../../../../../rtems/c/src/../../cpukit/score/src/threadentryadaptornumeric---Type <return> to continue, or q <return> to quit---

.c:25 #8 0x02012e0c in _Thread_Handler ()

at ../../../../../../rtems/c/src/../../cpukit/score/src/threadhandler.c:93

#9 0x02012d60 in _Thread_Handler ()

at ../../../../../../rtems/c/src/../../cpukit/score/src/threadhandler.c:29

(gdb) l init.c:93 88 status = rtems_clock_get_tod( &time ); 89 directive_failed( status, "rtems_clock_get_tod" ); 90 print_time( "TA1 - rtems_clock_get_tod - ", &time, " - RTEMS_SUCCESSFUL\n" ); 91 92 build_time( &time, 12, 31, 2100, 23, 59, 59, 0 ); 93 status = rtems_clock_set( &time ); 94 directive_failed( status, "rtems_clock_set" ); 95 print_time( "TA1 - rtems_clock_set - ", &time, " - RTEMS_SUCCESSFUL\n" ); 96 status = rtems_task_wake_after( rtems_clock_get_ticks_per_second() ); 97 status = rtems_clock_get_tod( &time ); (gdb)

#2669 3 years ago fixed tool/rsb Stefan Wallentowitz 11 months ago
Summary

Update OpenRISC toolchain in 4.12

Description

Bump the OpenRISC toolchain to newer versions:

  • Binutils to 2.26
  • GCC to 4.9.3
  • GDB to 7.11
#2672 3 years ago fixed unspecified Serg Kruglov Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

After latest patches with Objects_Get_by_name rtems-master not compiling without --enable-posix

Description

After latest patches with Objects_Get_by_name rtems-master not compiling if i use --disable-posix. Type "Objects_Get_by_name_error" not resolved in posixapi.h in sapi folder. If --enable-posix - all OK.

#2674 3 years ago fixed posix Sebastian Huber Sebastian Huber 11 months ago
Summary

CORE spinlock implementation is next to be useless

Description

Lets assume we have two tasks A and B. Task A acquires a CORE spinlock. Now B somehow executes and tries to acquire the same CORE spinlock, then no progress can be made.

Alternative implementation:

Disable thread dispatching and interrupts while owning the spinlock. Forbid blocking calls while owning the spinlock.

Drawback: The test cases of the Linux Test Project would fail:

https://github.com/linux-test-project/ltp/blob/master/testcases/open_posix_testsuite/conformance/interfaces/pthread_spin_lock/1-2.c

Optimization: User provided storage space for pthread_spin_t. In line with POSIX:

"Only the object referenced by lock may be used for performing synchronization."

http://pubs.opengroup.org/onlinepubs/009695399/functions/pthread_spin_destroy.html

#2676 3 years ago fixed unspecified Joel Sherrill Joel Sherrill <joel@…> 10 months ago
Summary

Obsolete clock_get() directive

Description

This is deprecated on the 4.11 branch and its use has been isolated in the source tree.

  • Remove clock_get()
  • Should allow deletion of rtems_clock_get_options

$ grep -rl "clock_get(" . ./doc/user/clock.t ./testsuites/tmtests/tmoverhd/testtask.c ./testsuites/tmtests/tmoverhd/dumrtems.h ./testsuites/sptests/spclockget/init.c ./testsuites/sptests/spclockget/spclockget.doc ./cpukit/rtems/include/rtems/rtems/clock.h ./cpukit/rtems/src/clockget.c

#2680 2 years ago fixed doc Joel Sherrill Chris Johns 11 months ago
Summary

Add pthread_setconcurrency() and pthread_getconcurrency()

Description

* Code merged. Ticket changed to documentation to remind us to add documentation when master documentation reopens in new format.

We only require the simple implementation documented here:

http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_getconcurrency.html

This is required for FACE Conformance.

#2684 2 years ago fixed arch/sparc David Binderman Sebastian Huber 11 months ago
Summary

rtems/c/src/lib/libbsp/sparc/leon3/clock/ckinit.c:122: duplicate if

Description

rtems/c/src/lib/libbsp/sparc/leon3/clock/ckinit.c:122]: (style) Expression is always false because 'else if' condition matches previous condition at line 116.

Source code is

} else if (state == 1) {

unsigned int ks = 1U << 5;

state = 0;

irqmp_ts->control = ks | s1_s2 | (unsigned int) clkirq;

} else if (state == 1) {

#2685 2 years ago fixed arch/arm David Binderman Sebastian Huber 11 months ago
Summary

c/src/lib/libbsp/arm/atsam/network/if_atsam.c:409: possible bad if statement

Description

rtems/c/src/lib/libbsp/arm/atsam/network/if_atsam.c:409]: (style) Redundant condition: If 'phy <= 0', the comparison 'phy <= 31' is always true.

Source code is

if ((phy <= 0) && (phy <= 31)) {

/*

  • invalid phy number */

Maybe better code

if ((phy <= 0)
(phy >= 31)) {

/*

  • invalid phy number */
#2689 2 years ago fixed posix Sebastian Huber Sebastian Huber 11 months ago
Summary

POSIX key destructors must be called during thread restart

Description

POSIX key destructors must be called during thread restart. Just like the POSIX cleanup handlers. This ensures that the TLS object destructors are called during thread restart for example. It is important for the global construction, which uses a thread restart to run the Init task in a clean environment.

#2692 2 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

User extensions execution order must be clarified

Description

The implemented and documented execution order of some user extensions disagree. Intended behaviour must be tested. Documentation must be updated accordingly.

#2693 2 years ago fixed doc Joel Sherrill Chris Johns 11 months ago
Summary

Update doc to reflect obsoleting rtems_clock_get()

Description

Ticket to reflect documentation change needed on the master but not on 4.11. When new documentation format is available for master, this needs to be accounted for.

#2694 2 years ago worksforme network/legacy Joel Sherrill Sebastian Huber 11 months ago
Summary

linking issue for htonl, etc when using -std=c99

Description

When -std=c99 is on the compile line, there is a linking error for undefined references to htonl, htons, ntohl, and ntohs. This test case is just for htonl but others should be similar.

This likely impacts the 4.11 branch of rtems-libbsd as well but I was testing on master.

Test case ====================== #include <arpa/inet.h>

int main(

int argc, char argv

) {

uint32_t v = (uint32_t) argc; uint32_t rc = htonl(v); return v;

} ======================

This script was what I used to find what caused the linking error to go away.

====================== RTEMS_MAKEFILE_PATH=/home/joel/rtems-4.11-work/tools/4.12/i386-rtems4.12/pc586/

i386-rtems4.12-gcc -std=c99 \

-B${RTEMS_MAKEFILE_PATH}/lib -specs bsp_specs -qrtems \ -D_XOPEN_SOURCE=600 -DUSE_SVID main.c -lbsd -lm -lbsd

i386-rtems4.12-gcc -std=c99 \

-B${RTEMS_MAKEFILE_PATH}/lib -specs bsp_specs -qrtems \ -DUSE_SVID main.c -lbsd -lm -lbsd

i386-rtems4.12-gcc -std=c99 \

-B${RTEMS_MAKEFILE_PATH}/lib -specs bsp_specs -qrtems \ main.c -lbsd -lm -lbsd

i386-rtems4.12-gcc \

-B${RTEMS_MAKEFILE_PATH}/lib -specs bsp_specs -qrtems \ main.c -lbsd -lm -lbsd

======================

#2695 2 years ago fixed tool/gcc Sebastian Huber Sebastian Huber 11 months ago
Summary

Add libatomic for RTEMS

#2696 2 years ago fixed unspecified Sebastian Huber Sebastian Huber 11 months ago
Summary

Unpredictable errno value returned by sem_wait() in case of semaphore deletion

Description

_POSIX_Semaphore_Delete() used -1 for the thread queue flush status which in turn resulted in an invalid memory access in _POSIX_Semaphore_Translate_core_semaphore_return_code().

#2698 2 years ago fixed tool/gcc Sebastian Huber 11 months ago
Summary

GCC 6.1 is broken for microblaze

Description

The enabled libatomic reveals a bug in the microblaze RTEMS configuration:

configure:3566: checking for C compiler default output file name configure:3588: /scratch/git-rtems-source-builder/rtems/build/microblaze-rtems4.12-gcc-6.0.1-RC-20160415-newlib-6ee81f44e04848901c7b05c968564d34a7ceed06-x86_64-linux-gnu-1/build/./gcc/xgcc -B/scratch/git-rtems-source-builder/rtems/build/microblaze-rtems4.12-gcc-6.0.1-RC-20160415-newlib-6ee81f44e04848901c7b05c968564d34a7ceed06-x86_64-linux-gnu-1/build/./gcc/ -nostdinc -B/scratch/git-rtems-source-builder/rtems/build/microblaze-rtems4.12-gcc-6.0.1-RC-20160415-newlib-6ee81f44e04848901c7b05c968564d34a7ceed06-x86_64-linux-gnu-1/build/microblaze-rtems4.12/newlib/ -isystem /scratch/git-rtems-source-builder/rtems/build/microblaze-rtems4.12-gcc-6.0.1-RC-20160415-newlib-6ee81f44e04848901c7b05c968564d34a7ceed06-x86_64-linux-gnu-1/build/microblaze-rtems4.12/newlib/targ-include -isystem /scratch/git-rtems-source-builder/rtems/build/microblaze-rtems4.12-gcc-6.0.1-RC-20160415-newlib-6ee81f44e04848901c7b05c968564d34a7ceed06-x86_64-linux-gnu-1/gcc-6.0.1-RC-20160415/newlib/libc/include -B/build/rtems-4.12/microblaze-rtems4.12/bin/ -B/build/rtems-4.12/microblaze-rtems4.12/lib/ -isystem /build/rtems-4.12/microblaze-rtems4.12/include -isystem /build/rtems-4.12/microblaze-rtems4.12/sys-include -g -O2 conftest.c >&5 /build/rtems-4.12/microblaze-rtems4.12/bin/ld: cannot open linker script file xilinx.ld: No such file or directory collect2: error: ld returned 1 exit status

Reason:

gcc/config/microblaze/microblaze.h: %{!T*: -dT xilinx.ld%s}"

This should be somehow fixed in the RTEMS GCC configuration for microblaze.

#2700 2 years ago fixed unspecified David Binderman Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

cpukit/libfs/src/nfsclient/src/rpcio.c:524]: (style) Suspicious condition

Description

cpukit/libfs/src/nfsclient/src/rpcio.c:524]: (style) Suspicious condition (assignment + comparison); Clarify expression with parentheses.

Source code is

if ( (len = getgroups(NGROUPS, gids) < 0 ) ) {

maybe better code

if ( (len = getgroups(NGROUPS, gids)) < 0 ) {

#2701 2 years ago fixed build printk Amar Takhar 11 months ago
Summary

Rename asm file with .S(upper case) ext. name

Description

The are some asm file with .s ext. name, .s and .S is different for gnu as, the pre processed produce .s file from .S. In a word, .S can use #define .s can not. KBuild clean .s files when make clean. I have submit a patch to devel, but blocked. Too big patch.

#2702 2 years ago fixed posix Sebastian Huber Sebastian Huber 9 months ago
Summary

Remove descriptor objects for POSIX message queues

Description

The mq_open() function returns a descriptor to a POSIX message queue object identified by a name. This is similar to sem_open(). In contrast to the POSIX semaphore the POSIX message queues use a separate object for the descriptor. This extra object is superfluous, since the object identifier can be used directly for this purpose, just like for the semaphores.

#2706 2 years ago fixed unspecified Sebastian Huber Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

Buffer allocation of capture engine is broken on SMP configurations

Description

The capture engine uses function static variables.

#2707 2 years ago fixed unspecified Sebastian Huber Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

Unsafe use of current processor index in capture engine

Description

The current processor index is used outside a thread dispatch disabled section.

#2714 2 years ago fixed posix Sebastian Huber Sebastian Huber 11 months ago
Summary

A pthread_detach() does not lead to a resource reclamation

Description

According to POSIX a pthread_detach() should lead to a resource reclamation if the thread is already cancelled.

#2718 2 years ago fixed unspecified Sebastian Huber Sebastian Huber 11 months ago
Summary

Blocking _CORE_message_queue_Submit() may lead to unpredictable results

Description

The thread wait return code is not properly initialized before the thread queue enqueue.

#2722 2 years ago fixed tool/newlib Sebastian Huber Sebastian Huber 11 months ago
Summary

SEM_VALUE_MAX is unusually small on RTEMS

Description

RTEMS defines SEM_VALUE_MAX to 32767 in Newlib

newlib/libc/sys/rtems/include/limits.h

Other systems use INT_MAX or 2147483647.

#2723 2 years ago fixed unspecified Sebastian Huber Sebastian Huber 11 months ago
Summary

CPUINFO command to report per-processor information

Description

Add a CPUINFO command to report per-processor information, e.g. processor index, online state and scheduler assignment.

[/] # cpuinfo
-------------------------------------------------------------------------------
                            PER PROCESSOR INFORMATION
-------+--------+--------------+-----------------------------------------------
 INDEX | ONLINE | SCHEDULER ID | SCHEDULER NAME
-------+--------+--------------+-----------------------------------------------
     0 |      1 |   0x0f010001 | MPS 
     1 |      1 |   0x0f010001 | MPS 
     2 |      1 |   0x0f010001 | MPS 
     3 |      1 |   0x0f010001 | MPS 
     4 |      1 |   0x0f010001 | MPS 
     5 |      1 |   0x0f010001 | MPS 
     6 |      1 |   0x0f010001 | MPS 
     7 |      1 |   0x0f010001 | MPS 
     8 |      1 |   0x0f010001 | MPS 
     9 |      1 |   0x0f010001 | MPS 
    10 |      1 |   0x0f010001 | MPS 
    11 |      1 |   0x0f010001 | MPS 
    12 |      1 |   0x0f010001 | MPS 
    13 |      1 |   0x0f010001 | MPS 
    14 |      1 |   0x0f010001 | MPS 
    15 |      1 |   0x0f010001 | MPS 
    16 |      1 |   0x0f010001 | MPS 
    17 |      1 |   0x0f010001 | MPS 
    18 |      1 |   0x0f010001 | MPS 
    19 |      1 |   0x0f010001 | MPS 
    20 |      1 |   0x0f010001 | MPS 
    21 |      1 |   0x0f010001 | MPS 
    22 |      1 |   0x0f010001 | MPS 
    23 |      1 |   0x0f010001 | MPS
#2725 2 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Classic binary semaphores without a locking protocol can be released by everyone

Description

The Classic binary semaphores without a locking protocol can be released by everyone, e.g. in contrast to the POSIX mutexes (all variants) or the Classic binary semphores with priority inheritance or ceiling, there is no owner check in the release path.

This behaviour is a bit unexpected and not documented.

The following test case fails in case an owner check is added:

*** BEGIN OF TEST SP 42 ***
Exercising blocking discipline w/extract in FIFO order 
Exercising blocking discipline w/unblock in FIFO order
TA00 - unblocked - OK

rtems_semaphore_delete FAILED -- expected (RTEMS_SUCCESSFUL) got (RTEMS_RESOURCE_IN_USE)

This is actually a bug in the test, since an available mutex is released again.

#2726 2 years ago fixed arch/sparc Sebastian Huber Daniel Hellstrom 11 months ago
Summary

grascs.c: Questionable use of binary semaphore

Description

Use a simple binary semaphore or binary semaphore with inherit priority instead.

c/src/lib/libbsp/sparc/shared/ascs/grascs.c-    
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-  /* Create semaphores for blocking ASCS_TC/TM functions */
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-  if(rtems_semaphore_create(rtems_build_name('A','S','C','0'),1,
c/src/lib/libbsp/sparc/shared/ascs/grascs.c:                        (RTEMS_FIFO|RTEMS_BINARY_SEMAPHORE|
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-                         RTEMS_NO_INHERIT_PRIORITY|RTEMS_LOCAL|
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-                         RTEMS_NO_PRIORITY_CEILING), 0,
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-                        &cfg->tcsem1) != RTEMS_SUCCESSFUL) {
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-    goto init_error2;
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-  }
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-  if(rtems_semaphore_create(rtems_build_name('A','S','C','2'),0,
c/src/lib/libbsp/sparc/shared/ascs/grascs.c:                        (RTEMS_FIFO|RTEMS_BINARY_SEMAPHORE|
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-                         RTEMS_NO_INHERIT_PRIORITY|RTEMS_LOCAL|
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-                         RTEMS_NO_PRIORITY_CEILING), 0,
c/src/lib/libbsp/sparc/shared/ascs/grascs.c-                        &cfg->tcsem2) != RTEMS_SUCCESSFUL) {
#2727 2 years ago fixed fs/fat Sebastian Huber Sebastian Huber 11 months ago
Summary

FAT file systems use wrong semaphore for mutual exclusion

Description
cpukit/libfs/src/dosfs/msdos_initsupp.c-
cpukit/libfs/src/dosfs/msdos_initsupp.c-    sc = rtems_semaphore_create(3,
cpukit/libfs/src/dosfs/msdos_initsupp.c-                                1,
cpukit/libfs/src/dosfs/msdos_initsupp.c:                                RTEMS_BINARY_SEMAPHORE | RTEMS_FIFO,
cpukit/libfs/src/dosfs/msdos_initsupp.c-                                0,
cpukit/libfs/src/dosfs/msdos_initsupp.c-                                &fs_info->vol_sema);
cpukit/libfs/src/dosfs/msdos_initsupp.c

Should use a binary semaphore with inherit priority.

#2728 2 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Pipes use wrong semaphore for mutual exclusion

Description
cpukit/libfs/src/pipe/fifo.c-      sc = rtems_semaphore_create(
cpukit/libfs/src/pipe/fifo.c-        rtems_build_name('P', 'I', 'P', 'E'),
cpukit/libfs/src/pipe/fifo.c-        1,
cpukit/libfs/src/pipe/fifo.c:        RTEMS_BINARY_SEMAPHORE | RTEMS_INHERIT_PRIORITY | RTEMS_PRIORITY,
cpukit/libfs/src/pipe/fifo.c-        RTEMS_NO_PRIORITY,
cpukit/libfs/src/pipe/fifo.c-        &pipe_semaphore
cpukit/libfs/src/pipe/fifo.c-      );

Should use a binary semaphore with inherit priority instead.

#2729 2 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

TFTP client uses wrong semaphore for mutual exclusion

Description
cpukit/libnetworking/lib/tftpDriver.c-    rtems_build_name('T', 'F', 'T', 'P'),
cpukit/libnetworking/lib/tftpDriver.c-    1,
cpukit/libnetworking/lib/tftpDriver.c-    RTEMS_FIFO |
cpukit/libnetworking/lib/tftpDriver.c:    RTEMS_BINARY_SEMAPHORE |
cpukit/libnetworking/lib/tftpDriver.c-    RTEMS_NO_INHERIT_PRIORITY |
cpukit/libnetworking/lib/tftpDriver.c-    RTEMS_NO_PRIORITY_CEILING |
cpukit/libnetworking/lib/tftpDriver.c-    RTEMS_LOCAL,

Should use a binary semaphore with inherit priority.

#2732 2 years ago fixed posix Gedare Gedare 11 months ago
Summary

Add clock_nanosleep()

Description

The clock_nanosleep function is provided to enable specifying the clock source (CLOCK_REALTIME or CLOCK_MONOTONIC) and to control whether or not to use an absolute or relative reference point via TIMER_ABSTIME flag.

See also: http://pubs.opengroup.org/onlinepubs/009695399/functions/clock_nanosleep.html

#2734 2 years ago fixed posix Sebastian Huber Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

pthread_setschedprio() is missing

Description

See also

http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_setschedprio.html

and

http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_08_04_01

In particular the distinction to pthread_setschedparam() (SCHED_FIFO, item 7.).

Prototype is defined in Newlib provide <pthread.h>.

#2735 2 years ago fixed posix Sebastian Huber Sebastian Huber 11 months ago
Summary

pthread_setschedparam() sets the priority not according to POSIX

Description

See also

http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_08_04_01

In particular the distinction to pthread_setschedprio() (SCHED_FIFO, item 7.).

#2736 2 years ago fixed posix Sebastian Huber Sebastian Huber 11 months ago
Summary

pthread_getschedparam() returns wrong priority values

Description

See also

http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_getschedparam.html

"The priority value returned from pthread_getschedparam() shall be the value specified by the most recent pthread_setschedparam(), pthread_setschedprio(), or pthread_create() call affecting the target thread. It shall not reflect any temporary adjustments to its priority as a result of any priority inheritance or ceiling functions."

#2737 2 years ago fixed bsps Sebastian Huber Sebastian Huber 11 months ago
Summary

Add CLOCK_DRIVER_USE_ONLY_BOOT_PROCESSOR

Description

Add CLOCK_DRIVER_USE_ONLY_BOOT_PROCESSOR clock driver option. If defined, then do the clock tick processing on the boot processor on behalf of all other processors. Currently, this is intended as a workaround for a Qemu shortcoming on ARM.

#2740 2 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Suboptimal type for Timestamp_Control

Description

Currently we have

typedef struct bintime Timestamp_Control;

this type offers more precision than needed. Maybe use sbintime_t (also known as int64_t) instead to simplify computations.

#2741 2 years ago fixed bsps Joel Sherrill Chris Johns 11 months ago
Summary

New warning from printf plugin changes

Description

../../../../../../../rtems/c/src/lib/libcpu/powerpc/mpc6xx/mmu/pte121.c: In function 'whatPrintf': ../../../../../../../rtems/c/src/lib/libcpu/powerpc/mpc6xx/mmu/pte121.c:189:46: warning: pointer type mismatch in conditional expression

return _Thread_Executing ? (PrintF) printf : printk;

#2742 2 years ago fixed unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

New warning in SHM driver

Description

Not sure how to fix this one

../../../../../rtems/c/src/libchip/shmdr/init.c:241:29: warning: assignment from incompatible pointer type [-Wincompatible-pointer-types]

MPCI_Shm_extensions.fatal = MPCI_Fatal;

PowerPC/psim with multiprocessing enabled.

#2745 2 years ago fixed posix Gedare Gedare 11 months ago
Summary

Use clock from pthread_condattr in pthread_cond_timedwait

Description

For pthread_cond_timedwait, the condition variable shall have a clock attribute which specifies the clock that shall be used to measure the time specified by the abstime argument. RTEMS currently does not honor the clock attribute.

See http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_cond_timedwait.html

#2748 2 years ago fixed network/legacy Sebastian Huber Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

Move RTEMS-specific socket wake-up to RTEMS-specific <rtems/rtems_bsdnet.h>

Description

The <sys/socket.h> contains definitions for the RTEMS-specific socket wake-up support. Move this stuff to <rtems/rtems_bsdnet.h> since this feature is not present in standard network stacks. Portable applications should not use it.

#2749 2 years ago fixed rtems Sebastian Huber Sebastian Huber 11 months ago
Summary

rtems_task_set_scheduler() has insufficient parameters

Description

Task priorities are only valid within a scheduler instance. The rtems_task_set_scheduler() directive moves a task from one scheduler instance to another using the current priority of the thread. However, the current task priority of the source scheduler instance is undefined in the target scheduler instance. Add a third parameter to specify the priority.

/**
 * @brief Sets the scheduler instance of a task.
 *
 * Initially, the scheduler instance of a task is set to the scheduler instance
 * of the task that created it.  This directive allows to move a task from its
 * current scheduler instance to another specified by the scheduler identifier.
 *
 * @param[in] task_id Identifier of the task.  Use @ref RTEMS_SELF to select
 *   the executing task.
 * @param[in] scheduler_id Identifier of the scheduler instance.
 * @param[in] priority The task priority with respect to the new scheduler
 *   instance.  The real and initial priority of the task is set to this value.
 *   The initial priority is used by rtems_task_restart() for example.
 *
 * @retval RTEMS_SUCCESSFUL Successful operation.
 * @retval RTEMS_ILLEGAL_ON_REMOTE_OBJECT Directive is illegal on remote tasks.
 * @retval RTEMS_INVALID_ID Invalid task or scheduler identifier.
 * @retval RTEMS_INVALID_PRIORITY Invalid priority.
 * @retval RTEMS_RESOURCE_IN_USE The task owns resources which deny a scheduler
 *   change.
 *
 * @see rtems_scheduler_ident().
 */
rtems_status_code rtems_task_set_scheduler(
  rtems_id            task_id,
  rtems_id            scheduler_id,
  rtems_task_priority priority
);
#2750 2 years ago fixed unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

Compile Error When Multiprocessing Enabled

Description

This should impact every BSP with multiprocessing enabled but I saw it on the sparc/leon3 and powerpc/psim

../../cpukit/../../../psim/lib/include/rtems/score/basedefs.h:229:5: error: static assertion failed: "Message_queue_MP_Packet"

_Static_assert(cond, # msg)

../../../../../../rtems/c/src/../../cpukit/rtems/src/msgmp.c:28:1: note: in expansion of macro 'RTEMS_STATIC_ASSERT'

RTEMS_STATIC_ASSERT(

#2751 2 years ago fixed score Sebastian Huber Sebastian Huber 3 months ago
Summary

Thread dispatch via interrupt is broken at least on ARM and PowerPC

Description

The ARM and PowerPC interrupt epilogues call _Thread_Dispatch() with interrupts disabled (counter example: SPARC).

On SMP configurations, since inter-processor interrupts set the thread dispatch necessary indicator this prevents a thread dispatch notification in post-switch handlers (which all run with interrupts disabled).

On all configurations, this is a serious issue for the interrupt latency.

#2752 2 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Relax execution enviroment for thread begin extensions

Description

Currently, the thread begin extensions are invoked with thread dispatching disabled. There is an explanation for this in the code

  /*
   * Take care that 'begin' extensions get to complete before
   * 'switch' extensions can run.  This means must keep dispatch
   * disabled until all 'begin' extensions complete.
   */
  _User_extensions_Thread_begin( executing );

However, the switch extension is always invoked before the thread begin extension for all threads except the initialization thread. A thread dispatch disabled contexts drastically limits the work which can be carried out in the thread begin extensions. It is for example not possible to call malloc(), create POSIX keys or access C++ thread local storage.

The thread begin extension should execute in a normal thread context. Thread begin extensions that are disturbed by a thread dispatch should deal with this locally.

With the availability of C++ thread local storage in RTEMS being able to pre-initialize such objects in the thread begin extension would be quite handy.

#2754 2 years ago fixed lib/dl Patrick Gauvin Chris Johns 11 months ago
Summary

no .strtab section

Description

dlopen on the object generated by libfoo.cpp in the attached test case fails and results in the error no .strtab section. readelf shows that the section is present, though:

readelf -S libfoo.o | grep strtab
(standard input):97:  [92] .shstrtab         STRTAB          00000000 001fb0 00040c 00      0   0  1
(standard input):99:  [94] .strtab           STRTAB          00000000 0018b0 00019e 00      0   0  1

Steps to Reproduce (you may have to edit BSP_DIR in the Makefile):

make clean all
qemu-system-arm -m 256M -M xilinx-zynq-a9 -serial null -serial mon:stdio \
    -nographic -no-reboot -kernel libdl-strtab-test.exe

Expected Output:

TEST BEGIN
dlopen: no .strtab section
assertion "handle != NULL" failed: file "libdl-strtab-test.c", line 46, function: POSIX_Init

Development Environment:

  • RTEMS Version: 4.11 (Branch "4.11", commit 3f72dda6ee518d3ea04341ad4df079ecb1895ef7) with the dlerror patches from #2747, and the attached ARM PREL31 support patch (I will be making a separate ticket for this with test code soon).
  • System Type: ARM Cortex-A9, xilinx_zynq_a9_qemu BSP
  • GCC Version:

arm-rtems4.11-gcc (GCC) 4.9.3 20150626 (RTEMS 4.11, RSB 1675a733536d1aec2020011e5e522497a442561a (HEAD, origin/4.11, 4.11), Newlib 2.2.0.20150423)

  • RTEMS Configure Options:

--target=arm-rtems4.11 --enable-rtemsbsp="xilinx_zynq_a9_qemu xilinx_zynq_zedboard xilinx_zynq_csp_cots xilinx_zynq_csp_hybrid" --enable-tests=samples --enable-posix --prefix=$HOME/development/rtems/4.11 --disable-networking

#2765 2 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Application level deadlocks may lead to SMP lock level deadlocks

Description

Due to a missing deadlock detection application level deadlocks may lead to SMP lock level deadlocks.

#2768 2 years ago fixed unspecified Chris Johns Chris Johns 11 months ago
Summary

untar does not keep permissions correctly.

Description

On disk I have 'x' with:

$ ls -las x
4 -rwxr-xr-x  1 chris  caeng  48 Jul 14 11:46 x

the tar file shows:

$ tar tvf rootfs.tar 
-rwxr-xr-x  0 chris  caeng      48 Jul 14 11:46 x

and in the IMFS it shows:

[/] # ls -las x
0 -rw-r--r--  1 root  root  48 Jan  1 00:00 x

The makes adding 'joel' scripts difficult.

#2769 2 years ago invalid unspecified Chris Johns Chris Johns 6 months ago
Summary

rtems-syms does not clean up temp files.

Description

I am seeing temps files such as:

$ ls -las /tmp/rld-*
 0 -rw-------  1 chris  wheel      0 Jul 27 18:16 /tmp/rld--04lbaa.rldxx
 0 -rw-------  1 chris  wheel      0 Jul 27 18:42 /tmp/rld--0niaaa.rldxx
 0 -rw-------  1 chris  wheel      0 Jul 27 18:39 /tmp/rld--0viaaa.rldxx
 0 -rw-------  1 chris  wheel      0 Jul 27 18:38 /tmp/rld--1Hhaaa.rldxx
88 -rw-------  1 chris  wheel  87426 Jul 27 18:30 /tmp/rld--1ibaaa.c
 0 -rw-------  1 chris  wheel      0 Jul 27 18:24 /tmp/rld--2EZaaa.rldxx
 0 -rw-------  1 chris  wheel      0 Jul 29 17:11 /tmp/rld--2rwaaa.rldxx
 0 -rw-------  1 chris  wheel      0 Jul 29 18:14 /tmp/rld--2sBaaa.rldxx
88 -rw-------  1 chris  wheel  88148 Jul 29 17:40 /tmp/rld--2umaaa.c
88 -rw-------  1 chris  wheel  87426 Jul 27 18:25 /tmp/rld--3baaaa.c
88 -rw-------  1 chris  wheel  87426 Jul 27 18:27 /tmp/rld--4Jaaaa.c
 0 -rw-------  1 chris  wheel      0 Jul 27 18:52 /tmp/rld--4Wiaaa.rldxx
 0 -rw-------  1 chris  wheel      0 Jul 27 18:38 /tmp/rld--4bfaaa.rldxx

left in /tmp. They look like symbols and so I suspect rtems-syms when building the testsuite with 4.12 (master). This is on FreeBSD.

#2770 2 years ago fixed doc Christian Mauderer Sebastian Huber 11 months ago
Summary

Missing documentation for RTEMS_LINKER_ROSET_CONTENT and RTEMS_LINKER_RWSET_CONTENT

Description

Currently the two macros

RTEMS_LINKER_ROSET_CONTENT RTEMS_LINKER_RWSET_CONTENT

are not documented. This should be added as soon as the doc repo is ready for it.

The macros have been introduced in this commit:

https://git.rtems.org/rtems/commit/?id=5fe6d07ad5690e3d9c6445ca3a465a700a5a5015

#2771 2 years ago wontfix score Chris Johns 11 months ago
Summary

Empty C++ file with just <rtems.h> does not compile with HEAD.

Description

I have an application that does not build.

The following C++ file:

$ cat t1.cpp
#include <rtems.h>

does not compile with git head 5fe6d07ad5690e3d9c6445ca3a465a700a5a5015 on Zynq ARM. Build with:

$ /opt/work/rtems/4.12/bin/arm-rtems4.12-g++ \
  -B/opt/work/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib \
  -B/opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib \
  -specs bsp_specs -qrtems \
  -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard -mtune=cortex-a9 \
  -g -O2 -DNDEBUG -std=c++11 \
  -Werror -Wall -Wextra \
  -o t1.o \
  -c t1.cpp

Some (too much to post) of the output is:

In file included from /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/score/thread.h:36:0,
                 from /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/score/heap.h:22,
                 from /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/rtems/types.h:26,
                 from /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems.h:31,
                 from t1.cpp:1:
/opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/score/timestamp.h: In function 'void _Timestamp_Set(Timestamp_Control*, time_t, long int)':
/opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/score/timestamp.h:78:33: error: 'timespec2bintime' was not declared in this scope
   timespec2bintime( &_ts, _time );
                                 ^
/opt/work/si/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/score/timestamp.h: In function 'void _Timestamp_Set_to_zero(Timestamp_Control*)':
/opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/score/timestamp.h:94:8: error: invalid use of incomplete type 'Timestamp_Control {aka struct bintime}'
   _time->sec = 0;
        ^~
In file included from /opt/work/rtems/4.12/arm-rtems4.12/include/sys/time.h:299:0,
                 from /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/score/timestamp.h:43,
                 from /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/score/thread.h:36,
                 from /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/score/heap.h:22,
                 from /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems/rtems/types.h:26,
                 from /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/include/rtems.h:31,
                 from t1.cpp:1:
/opt/work/rtems/4.12/arm-rtems4.12/include/machine/_time.h:40:15: note: forward declaration of 'Timestamp_Control {aka struct bintime}'
 extern struct bintime _Timecounter_Boottimebin;
               ^~~~~~~

If '-std=c++11' is removed or replaced with '-std=gnu++11' the error becomes:

arm-rtems4.12-g++: fatal error: /opt/work/bsps/rtems/4.12/arm-rtems4.12/xilinx_zynq_zc706/lib/bsp_specs: attempt to rename spec 'endfile' to already defined spec 'old_endfile'
#2775 2 years ago fixed arch/arm Chris Johns Chris Johns <chrisj@…> 11 months ago
Summary

ARM CP15 arm_cp15_set_translation_table_entries fails if TTB in read-only memory

Description

If the TTB is held in the text section and the section is set to read-only, and cached when booting no section change happen at run time because the table cannot be written too to change. The table cannot be changed unless the MMU is disabled.

I suggest the MMU be disabled, the table updated and then the MMU enabled.

Note, the issue only shows up on real hardware, qemu does not complain.

#2776 2 years ago fixed score Alexander Krutwig Sebastian Huber 11 months ago
Summary

SPI Framework

Description

Development of a SPI framework which shall be used for further SPI bus and device drivers. The framework shall be developed using the i2c framework as a template. It shall export the Linux Userspace SPI API.

#2777 2 years ago fixed unspecified Chris Johns Chris Johns 11 months ago
Summary

Remove librtems++

Description

This is old and there are better design patterns for threading and C++. We recommend you use the new C++ standards based support.

#2784 2 years ago fixed rtems Sebastian Huber Sebastian Huber 11 months ago
Summary

Add function to get the current priority of a task by scheduler instance

Description
/**
 * @brief Gets the current priority of the specified task with respect to the
 * specified scheduler instance.
 *
 * The current priority reflects temporary priority adjustments due to locking
 * protocols, the rate-monotonic objects on some schedulers and other
 * mechnisms.
 *
 * @param[in] task_id Identifier of the task.  Use @ref RTEMS_SELF to select
 *   the executing task.
 * @param[in] scheduler_id Identifier of the scheduler instance.
 * @param[out] priority Returns the current priority of the specified task with
 *   respect to the specified scheduler instance.
 *
 * @retval RTEMS_SUCCESSFUL Successful operation.
 * @retval RTEMS_ILLEGAL_ON_REMOTE_OBJECT Directive is illegal on remote tasks.
 * @retval RTEMS_INVALID_ADDRESS The priority parameter is @c NULL.
 * @retval RTEMS_INVALID_ID Invalid task or scheduler identifier.
 * @retval RTEMS_NOT_DEFINED The task has no priority within the specified
 *   scheduler instance.
 *
 * @see rtems_scheduler_ident().
 */
rtems_status_code rtems_task_get_priority(
  rtems_id             task_id,
  rtems_id             scheduler_id,
  rtems_task_priority *priority
);
#2788 2 years ago wontfix score Chris Johns Chris Johns 11 months ago
Summary

RTEMS I2C API only defines Standard-mode (Sm) speed as a default.

Description

The RTEMS I2C API as defined in cpukit/dev/include/dev/i2c/i2c.h only defines the bus speed as Standard-mode (Sm) as defined by the I2C standard. This is set as I2C_BUS_CLOCK_DEFAULT. The default speed is defined by the hardware, ie the devices connected, and not this API.

The API should define the speeds as defined in the I2C standard and there should be no default. Drivers like the Cadence driver for the Zynq should be modified to require the bus speed be provided and all future drivers need to provide the speed.

#2790 2 years ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Linker sets broken with GCC 7

Description

See also:

https://gcc.gnu.org/ml/gcc/2016-09/msg00114.html

The

#define MAKEGCCNOTKNOWTHEADDRESS(ptr) asm("":"+r"(ptr))

is probably the best option. It works probably also with link-time optimization.

#2795 2 years ago fixed score Kuan Gedare Bloom <gedare@…> 11 months ago
Summary

Overrun Handling for general real-time models

Description

In the current implementation, if a task period is time out, the next call of rtems_rate_monotonic_period() will only release one following job and manipulate the task period with the calling moment + the next length of period. With the assumption that implicit/constraint deadline and hard real-time model, the above mechanism is okay.

However, it may not be applicable for general task models, e.g., soft real-time task, arbitrary deadline, mixed-criticality system [1-4]. It is usually assumed that multiple task jobs of a task are executed in a first-come-first-serve manner. Thus, it is sufficient to release the second task job at the moment the first task job finishes according to a strictly periodic release pattern. The current design in fact shifts the release pattern of periodic/sporadic tasks. Since there maybe more than one postponed jobs due to the preemption, these postponed jobs that should be released are never released to the system.

Although there is no standard requirement in reality for deadline misses, with this enhancement, the postponed jobs will be released with the correct number without periodic release shifting. This way of handling is already widely considered in academia from 90s [2] until now [3] or even on multicores as well [4].

I refine the following four files and handle this requirement individually. The overhead seems to me negligible. cpukit/rtems/include/rtems/rtems/ratemon.h cpukit/rtems/include/rtems/rtems/ratemonimpl.h cpukit/rtems/src/ratemontimeout.c cpukit/rtems/src/ratemonperiod.c I have tested the enhancement on Qemu and Raspberry Pi Model B+ with corresponding BSPs.

I believe this patch as a basis is required for further use for more general real-time task models. This enhancement only affect those timeout cases without changing any behaviour in normal cases. This enhancement is accepted in workshop mixed-criticality (WMC 2016) along with RTSS'16 this year [5].

To demonstrate the differences, a heuristic example is prepared in testsuites/sptests/sprmsched01 to show the benefit of the enhancement: Given two tasks with implicit deadline that task deadline is equal to its period. Task 1 period is 10000 ticks, whereas task 2 is 2000 ticks. Task 1 has the execution time 6000 ticks, and task 2 has 1000 ticks. Assume Task 1 has a higher priority than task 2. Task 1 only executes 2 times. In the expected result, we can observe that the postponed jobs are continuously released till there is no postponed job left, and the task period will still keep as it is. (Job 3-7 in task 2 are postponed jobs)

[1] Buttazzo et al., Soft Real-Time Systems: Predictability vs. Efficiency, Springer 2005, ​http://www.springer.com/gp/book/9780387237015 [2] Lehoczky et al., Fixed priority scheduling of periodic task sets with arbitrary deadlines, RTSS 1990, ​http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=128748 [3] Georg von der Brüggen et al., Systems with Dynamic Real-Time Guarantees in Uncertain and Faulty Execution Environments, RTSS'16, accepted. [4] Huang et al., Response time bounds for sporadic arbitrary-deadline tasks under global fixed-priority scheduling on multiprocessors, RTNS 2015, ​http://dl.acm.org/citation.cfm?doid=2597457.2597459 [5] Chen et al., Overrun Handling for Mixed-Criticality Support in RTEMS, WMC 2016, accepted.

#2797 2 years ago fixed rtems Sebastian Huber Sebastian Huber 11 months ago
Summary

Add ability to add/remove processors to/from a scheduler instance

Description

The scheduler configuration is done at link-time. In order to support run-time re-configuration add functions to dd/remove processors to/from a scheduler instance.

/**
 * @brief Adds a processor the set of processors owned by the scheduler.
 *
 * Must be called from task context.  This operation obtains and releases the
 * objects allocator lock.
 *
 * @param[in] scheduler_id Identifier of the scheduler.
 * @param[in] cpu_index Index of the processor to add.
 *
 * @retval RTEMS_SUCCESSFUL Successful operation.
 * @retval RTEMS_INVALID_ID Invalid scheduler identifier.
 * @retval RTEMS_NOT_CONFIGURED The processor is not configured to be used by
 *   the application.
 * @retval RTEMS_INCORRECT_STATE The processor is configured to be used by
 *   the application, however, it is not available.
 */
rtems_status_code rtems_scheduler_add_processor(
  rtems_id scheduler_id,
  uint32_t cpu_index
);

/**
 * @brief Removes a processor from set of processors owned by the scheduler.
 *
 * Must be called from task context.  This operation obtains and releases the
 * objects allocator lock.  Removing a processor from a scheduler is a complex
 * operation that involves all tasks in the system.
 *
 * @param[in] scheduler_id Identifier of the scheduler.
 * @param[in] cpu_index Index of the processor to add.
 *
 * @retval RTEMS_SUCCESSFUL Successful operation.
 * @retval RTEMS_INVALID_ID Invalid scheduler identifier.
 * @retval RTEMS_INVALID_NUMBER The processor is not owned by the scheduler.
 * @retval RTEMS_RESOURCE_IN_USE The set of processors owned by the scheduler
 *   would be empty after the processor removal and there exists a non-idle
 *   task that uses this scheduler as its home scheduler.
 */
rtems_status_code rtems_scheduler_remove_processor(
  rtems_id scheduler_id,
  uint32_t cpu_index
);
#2798 2 years ago fixed posix Sebastian Huber Sebastian Huber 11 months ago
Summary

Fix POSIX timer interval

Description

See also:

https://lists.rtems.org/pipermail/users/2016-October/030714.html

Just back to RTEMS after a long time. I've build the last version (Git) 
with last compiler (4.12) and looks like a simple POSIX timer  doen't 
work anymore... It should display "Signal 14" every second but period is 
veryyyy short...and display very fast :(

Any idea? any change in the way to use POSIX with RTEMS?

See my program attached (it works fine with Linux).

I have tested with Raspberry Pi and QEMU/i386.

thx by advance
#2800 23 months ago fixed arch/powerpc Joel Sherrill Sebastian Huber 11 months ago
Summary

qoriq variants failing to build

Description

The following qoriq variants fail to build:

powerpc-qoriq_core_0 powerpc-qoriq_core_1 powerpc-qoriq_p1020rdb

All fail with this error:

../../../../../.././qoriq_core_0/lib/include/bsp/qoriq.h:407:3: error: conflicting types for 'qoriq_gpio'
 } qoriq_gpio;
   ^~~~~~~~~~
../../../../../.././qoriq_core_0/lib/include/bsp/qoriq.h:184:3: note: previous declaration of 'qoriq_gpio' was here
 } qoriq_gpio;
   ^~~~~~~~~~

Found during full build sweep based on this commit:

commit bb9f09f34c9bdcf4d2631a1fd317bcefd8426efb
Author: Sebastian Huber <sebastian.huber@embedded-brains.de>
Date:   Mon Oct 31 13:07:34 2016 +0100

    posix: Fix timer interval
    
    Do not overwrite timer interval with initial interval in
    _POSIX_Timer_Insert().
    
    Close #2798.

#2802 23 months ago fixed lib/dl Sebastian Huber Chris Johns 11 months ago
Summary

Test "libdl (RTL) 5" fails on SPARC targets

Description

On GR740 I get:

rtl: RELOC_32 0x60ae8 @ 0x86edc in /dl-o5.o
rtl: relocation: .rela.eh_frame, syms:.symtab
rtl: rela: sym:__gxx_personality_v0(20)=00001dec type:3  off:00000013 addend:0

CPU 0:  IU in error mode (tt = 0x07, mem address not aligned)
        0x0001fa9c: c4040000  ld  [%l0], %g2  <rtems_rtl_elf_relocate_rela+204>
CPU 1:  Power down mode
CPU 2:  Power down mode
CPU 3:  Power down mode

On GR712RC I get:

rtl: WDISP_30 0x7ffe2ccd @ 0x40087108 in /dl-o5.o
rtl: relocation: .rela.gcc_except_table.exception_dl, syms:.symtab
rtl: rela: sym:_ZTISt9exception(32)=40060ae8 type:3  off:00000034 addend:0
rtl: RELOC_32 0x40060ae8 @ 0x400871b4 in /dl-o5.o
rtl: relocation: .rela.eh_frame, syms:.symtab
rtl: rela: sym:__gxx_personality_v0(20)=40001dec type:3  off:00000013 addend:0

Target resets now.

#2803 23 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Get rid of CPU_BIG_ENDIAN and CPU_LITTLE_ENDIAN

Description

The remaining uses of the CPU port defines CPU_BIG_ENDIAN and CPU_LITTLE_ENDIAN should be replaced by the BSD (also available in glibc) BYTE_ORDER.

#2805 23 months ago fixed arch/powerpc Sebastian Huber Sebastian Huber 11 months ago
Summary

Use SPRG0 on PowerPC for current per-CPU control (SMP only)

Description

Add _CPU_Get_current_per_CPU_control() on SMP configurations as an optimization for PowerPC. Use SPRG0 for the current per-CPU control. This reduces the code size a bit and is slightly faster in some benchmarks.

#2807 23 months ago fixed admin Sebastian Huber Amar Takhar 11 months ago
Summary

rtems-docs repository is not known to trac

#2808 23 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Conditionally provide rtems_interrupt_frame

Description

Provide rtems_interrupt_frame only if CPU_ISR_PASSES_FRAME_POINTER is defined to TRUE.

#2809 23 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Reduce interrupt latency on SMP configurations during thread dispatch

Description

Currently we have this situation:

https://docs.rtems.org/doc-current/share/rtems/html/c_user/Symmetric-Multiprocessing-Services-Thread-Dispatch-Details.html#Symmetric-Multiprocessing-Services-Thread-Dispatch-Details

"On SMP systems, scheduling decisions on one processor must be propagated to other processors through inter-processor interrupts. So, a thread dispatch which must be carried out on another processor happens not instantaneous. Thus several thread dispatch requests might be in the air and it is possible that some of them may be out of date before the corresponding processor has time to deal with them. The thread dispatch mechanism uses three per-processor variables,

  • the executing thread,
  • the heir thread, and
  • an boolean flag indicating if a thread dispatch is necessary or not.

Updates of the heir thread and the thread dispatch necessary indicator are synchronized via explicit memory barriers without the use of locks. A thread can be an heir thread on at most one processor in the system. The thread context is protected by a TTAS lock embedded in the context to ensure that it is used on at most one processor at a time. The thread post-switch actions use a per-processor lock. This implementation turned out to be quite efficient and no lock contention was observed in the test suite.

The current implementation of thread dispatching has some implications with respect to the interrupt latency. It is crucial to preserve the system invariant that a thread can execute on at most one processor in the system at a time. This is accomplished with a boolean indicator in the thread context. The processor architecture specific context switch code will mark that a thread context is no longer executing and waits that the heir context stopped execution before it restores the heir context and resumes execution of the heir thread (the boolean indicator is basically a TTAS lock). So, there is one point in time in which a processor is without a thread. This is essential to avoid cyclic dependencies in case multiple threads migrate at once. Otherwise some supervising entity is necessary to prevent deadlocks. Such a global supervisor would lead to scalability problems so this approach is not used. Currently the context switch is performed with interrupts disabled. Thus in case the heir thread is currently executing on another processor, the time of disabled interrupts is prolonged since one processor has to wait for another processor to make progress.

It is difficult to avoid this issue with the interrupt latency since interrupts normally store the context of the interrupted thread on its stack. In case a thread is marked as not executing, we must not use its thread stack to store such an interrupt context. We cannot use the heir stack before it stopped execution on another processor. If we enable interrupts during this transition, then we have to provide an alternative thread independent stack for interrupts in this time frame. This issue needs further investigation.

The problematic situation occurs in case we have a thread which executes with thread dispatching disabled and should execute on another processor (e.g. it is an heir thread on another processor). In this case the interrupts on this other processor are disabled until the thread enables thread dispatching and starts the thread dispatch sequence. The scheduler (an exception is the scheduler with thread processor affinity support) tries to avoid such a situation and checks if a new scheduled thread already executes on a processor. In case the assigned processor differs from the processor on which the thread already executes and this processor is a member of the processor set managed by this scheduler instance, it will reassign the processors to keep the already executing thread in place. Therefore normal scheduler requests will not lead to such a situation. Explicit thread migration requests, however, can lead to this situation. Explicit thread migrations may occur due to the scheduler helping protocol or explicit scheduler instance changes. The situation can also be provoked by interrupts which suspend and resume threads multiple times and produce stale asynchronous thread dispatch requests in the system."

Add an interrupt frame to the per-CPU control which can be used during context switches on SMP configurations.

#2810 23 months ago fixed arch/sparc Joel Sherrill Joel Sherrill 11 months ago
Summary

Remove sparc/sis BSP variant

Description

As discussed in the following thread, the sparc/sis BSP variant is no longer necessary and can be removed.

https://lists.rtems.org/pipermail/devel/2016-November/016383.html

This ticket is to track that removal.

#2811 23 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

More robust thread dispatching on SMP and ARM Cortex-M

Description

On SMP configurations, it is a fatal error to call blocking operating system with interrupts disabled, since this prevents delivery of inter-processor interrupts. This could lead to executing threads which are not allowed to execute resulting in undefined behaviour.

The ARM Cortex-M port has a similar problem, since the interrupt state is not a part of the thread context.

Add a new CPU port function:

/**
 * @brief Returns true if interrupts are enabled in the specified ISR level,
 * otherwise returns false.
 *
 * @param[in] level The ISR level.
 *
 * @retval true Interrupts are enabled in the ISR level.
 * @retval false Otherwise.
 */
RTEMS_INLINE_ROUTINE bool _CPU_ISR_Is_enabled( uint32_t level )
{
  return false;
}

Use this function to ensure that _Thread_Do_dispatch() is called with an interrupt level with enabled interrupts, otherwise call _Terminate().

#2816 23 months ago fixed arch/arm Joel Sherrill Sebastian Huber 11 months ago
Summary

Many ARM BSPs have Static Assert

Description

Hi

With the recent commits, many BSPs on the master do not build. They error out with this static assert:

In file included from ../../../../cpukit/../../../gumstix/lib/include/rtems/score/types.h:23:0,

from ../../../../cpukit/../../../gumstix/lib/include/rtems/score/cpu.h:32, from ../../../../cpukit/../../../gumstix/lib/include/rtems/system.h:23, from ../../../../../../../../rtems/c/src/../../cpukit/score/cpu/arm/cpu.c:29:

../../../../cpukit/../../../gumstix/lib/include/rtems/score/basedefs.h:241:5: error: static assertion failed: "ARM_CONTEXT_CONTROL_ISR_DISPATCH_DISABLE"

_Static_assert(cond, # msg)

../../../../../../../../rtems/c/src/../../cpukit/score/cpu/arm/cpu.c:54:3: note: in expansion of macro 'RTEMS_STATIC_ASSERT'

RTEMS_STATIC_ASSERT(

The list of BSPs is:

arm1136jfs arm1136js arm7tdmi arm920 csb336 csb337 csb637 edb7312 gumstix kit637_v6 lpc2362 lpc23xx_tli800 lpc24xx_ea lpc24xx_ncs_ram lpc24xx_ncs_rom_ext lpc24xx_ncs_rom_int lpc24xx_plx800_ram lpc24xx_plx800_rom_int lpc32xx_mzx lpc32xx_mzx_stage_1 lpc32xx_mzx_stage_2 lpc32xx_phycore raspberrypi rtl22xx rtl22xx_t smdk2410

#2817 23 months ago fixed unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

All Blackfin BSPs do not Compile on Master

Description

Recent changes to master resulted in this:

bfin-rtems4.12-gcc --pipe -DHAVE_CONFIG_H -I../../.. -I../../../../cpukit/../../../bf537Stamp/lib/include -O2 -g -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -MT libscorecpu_a-cpu.o -MD -MP -MF .deps/libscorecpu_a-cpu.Tpo -c -o libscorecpu_a-cpu.o test -f 'cpu.c' || echo '../../../../../../../../rtems/c/src/../../cpukit/score/cpu/bfin/'cpu.c bfin-rtems4.12-gcc --pipe -DHAVE_CONFIG_H -I../../.. -I../../../../cpukit/../../../bf537Stamp/lib/include -DASM -O2 -g -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -O2 -g -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -MT libscorecpu_a-cpu_asm.o -MD -MP -MF .deps/libscorecpu_a-cpu_asm.Tpo -c -o libscorecpu_a-cpu_asm.o test -f 'cpu_asm.S' || echo '../../../../../../../../rtems/c/src/../../cpukit/score/cpu/bfin/'cpu_asm.S ../../../../cpukit/../../../bf537Stamp/lib/include/rtems/score/cpu.h: Assembler messages: ../../../../cpukit/../../../bf537Stamp/lib/include/rtems/score/cpu.h:670: Error: syntax error. Input text was static. ../../../../cpukit/../../../bf537Stamp/lib/include/rtems/score/cpu.h:670: Error: ../../../../cpukit/../../../bf537Stamp/lib/include/rtems/score/cpu.h:671: Error: syntax error. Input text was {. ../../../../cpukit/../../../bf537Stamp/lib/include/rtems/score/cpu.h:671: Error: ../../../../cpukit/../../../bf537Stamp/lib/include/rtems/score/cpu.h:672: Error: syntax error. Input text was return. ../../../../cpukit/../../../bf537Stamp/lib/include/rtems/score/cpu.h:672: Error: ../../../../cpukit/../../../bf537Stamp/lib/include/rtems/score/cpu.h:673: Error: syntax error. Input text was }. ../../../../cpukit/../../../bf537Stamp/lib/include/rtems/score/cpu.h:673: Error: gmake[7]: * [libscorecpu_a-cpu_asm.o] Error 1

#2818 23 months ago fixed unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

NIOS2 Does Not Compile on Master

Description

../../../../../../../../rtems/c/src/../../cpukit/score/cpu/nios2/nios2-isr-get-level.c: In function '_CPU_ISR_Is_enabled': ../../../../../../../../rtems/c/src/../../cpukit/score/cpu/nios2/nios2-isr-get-level.c:26:16: error: 'status' undeclared (first use in this function)

return ((status & NIOS2_STATUS_IL_MASK) >> NIOS2_STATUS_IL_OFFSET) == 0;

~

../../../../../../../../rtems/c/src/../../cpukit/score/cpu/nios2/nios2-isr-get-level.c:26:16: note: each undeclared identifier is reported only once for each function it appears in ../../../../../../../../rtems/c/src/../../cpukit/score/cpu/nios2/nios2-isr-get-level.c:32:1: warning: control reaches end of non-void function [-Wreturn-type]

}

#2819 23 months ago fixed arch/powerpc Joel Sherrill Sebastian Huber 11 months ago
Summary

powerpc-ss555 does not compile on master

Description

Recent changes broke this configuration:

gmake[6]: Entering directory `/data/home/joel/rtems-4.11-work/rtems-testing/rtems/build-powerpc-ss555-rtems/powerpc-rtems4.12/c/ss555/testsuites/samples/hello' powerpc-rtems4.12-gcc -B../../../../../ss555/lib/ -specs bsp_specs -qrtems -DHAVE_CONFIG_H -I. -I../../../../../../../rtems/c/src/../../testsuites/samples/hello -I.. -mcpu=505 -Dmpc555 -O2 -g -fno-keep-inline-functions -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -MT init.o -MD -MP -MF .deps/init.Tpo -c -o init.o ../../../../../../../rtems/c/src/../../testsuites/samples/hello/init.c In file included from ../../../../../ss555/lib/include/rtems/score/percpu.h:22:0,

from ../../../../../ss555/lib/include/rtems/confdefs.h:32, from ../../../../../../../rtems/c/src/../../testsuites/samples/hello/init.c:51:

../../../../../ss555/lib/include/rtems/score/cpuimpl.h:196:3: error: conflicting types for 'CPU_Interrupt_frame'

} CPU_Interrupt_frame;

In file included from ../../../../../ss555/lib/include/bsp/irq.h:28:0,

from ../../../../../ss555/lib/include/bsp.h:31, from ../../../../../../../rtems/c/src/../../testsuites/samples/hello/init.c:17:

../../../../../ss555/lib/include/libcpu/irq.h:193:3: note: previous declaration of 'CPU_Interrupt_frame' was here

} CPU_Interrupt_frame;

gmake[6]: * [init.o] Error 1 gmake[6]: Target `all' not remade because of errors.

#2820 23 months ago fixed arch/sparc Joel Sherrill Sebastian Huber 11 months ago
Summary

All SPARC64 BSPs do not Build on master

Description

Recent changes broke all builds:

sparc64-rtems4.12-gcc --pipe -DHAVE_CONFIG_H -I../../.. -I../../../../cpukit/../../../usiii/lib/include -mcpu=ultrasparc3 -DUS3 -DSUN4U -g -O2 -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -MT libscorecpu_a-sparc64-exception-frame-print.o -MD -MP -MF .deps/libscorecpu_a-sparc64-exception-frame-print.Tpo -c -o libscorecpu_a-sparc64-exception-frame-print.o test -f 'sparc64-exception-frame-print.c' || echo '../../../../../../../../rtems/c/src/../../cpukit/score/cpu/sparc64/'sparc64-exception-frame-print.c sparc64-rtems4.12-gcc --pipe -DHAVE_CONFIG_H -I../../.. -I../../../../cpukit/../../../usiii/lib/include -mcpu=ultrasparc3 -DUS3 -DSUN4U -g -O2 -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -MT ../no_cpu/libscorecpu_a-cpucounterread.o -MD -MP -MF ../no_cpu/.deps/libscorecpu_a-cpucounterread.Tpo -c -o ../no_cpu/libscorecpu_a-cpucounterread.o test -f '../no_cpu/cpucounterread.c' || echo '../../../../../../../../rtems/c/src/../../cpukit/score/cpu/sparc64/'../no_cpu/cpucounterread.c In file included from ../../../../../../../../rtems/c/src/../../cpukit/score/cpu/sparc64/../no_cpu/cpucounterread.c:15:0: ../../../../cpukit/../../../usiii/lib/include/rtems/score/cpu.h: In function '_CPU_ISR_Is_enabled': ../../../../cpukit/../../../usiii/lib/include/rtems/score/cpu.h:759:12: error: 'psr' undeclared (first use in this function)

return ( psr & SPARC_PSTATE_IE_MASK ) != 0;

../../../../cpukit/../../../usiii/lib/include/rtems/score/cpu.h:759:12: note: each undeclared identifier is reported only once for each function it appears in gmake[7]: * no_cpu/libscorecpu_a-cpucounterread.o Error 1 mv -f .deps/libscorecpu_a-context.Tpo .deps/libscorecpu_a-context.Po In file included from ../../../../cpukit/../../../usiii/lib/include/rtems/system.h:23:0,

#2821 22 months ago invalid unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

No BSPs Build on Master

Description

I have the latest tools.

All BSPs appear to fail like this:

powerpc-rtems4.11-gcc --pipe -DHAVE_CONFIG_H -I.. -I../../cpukit/../../../psim/lib/include -meabi -mcpu=603e -msdata=sysv -fno-common -Dppc603e -O2 -g -fno-keep-inline-functions -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -MT src/libscore_a-smpbarrierwait.o -MD -MP -MF src/.deps/libscore_a-smpbarrierwait.Tpo -c -o src/libscore_a-smpbarrierwait.o test -f 'src/smpbarrierwait.c' || echo '../../../../../../rtems/c/src/../../cpukit/score/'src/smpbarrierwait.c powerpc-rtems4.11-gcc --pipe -DHAVE_CONFIG_H -I.. -I../../cpukit/../../../psim/lib/include -meabi -mcpu=603e -msdata=sysv -fno-common -Dppc603e -O2 -g -fno-keep-inline-functions -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -MT src/libscore_a-kern_tc.o -MD -MP -MF src/.deps/libscore_a-kern_tc.Tpo -c -o src/libscore_a-kern_tc.o test -f 'src/kern_tc.c' || echo '../../../../../../rtems/c/src/../../cpukit/score/'src/kern_tc.c powerpc-rtems4.11-gcc --pipe -DHAVE_CONFIG_H -I.. -I../../cpukit/../../../psim/lib/include -meabi -mcpu=603e -msdata=sysv -fno-common -Dppc603e -O2 -g -fno-keep-inline-functions -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -MT src/libscore_a-libatomic.o -MD -MP -MF src/.deps/libscore_a-libatomic.Tpo -c -o src/libscore_a-libatomic.o test -f 'src/libatomic.c' || echo '../../../../../../rtems/c/src/../../cpukit/score/'src/libatomic.c mv -f src/.deps/libscore_a-semaphore.Tpo src/.deps/libscore_a-semaphore.Po mv -f src/.deps/libscore_a-once.Tpo src/.deps/libscore_a-once.Po ../../../../../../rtems/c/src/../../cpukit/score/src/libatomic.c:19:32: fatal error: machine/_libatomic.h: No such file or directory

#include <machine/_libatomic.h>

compilation terminated. gmake[6]: * [src/libscore_a-libatomic.o] Error 1 In file included from /data/home/joel/rtems-4.11-work/tools/4.11/powerpc-rtems4.11/include/sys/param.h:89:0,

from ../../../../../../rtems/c/src/../../cpukit/score/src/kern_tc.c:48:

../../cpukit/../../../psim/lib/include/sys/uio.h:41:9: error: unknown type name 'ssize_t'

typedef ssize_t ssize_t;

../../cpukit/../../../psim/lib/include/sys/uio.h:46:9: error: unknown type name 'off_t'

typedef off_t off_t;

../../cpukit/../../../psim/lib/include/sys/uio.h:46:17: error: conflicting types for 'off_t'

typedef off_t off_t;

#2822 22 months ago fixed unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

m32csim does not build on master

Description

In file included from ../../cpukit/../../../m32csim/lib/include/rtems/score/types.h:22:0,

from ../../cpukit/../../../m32csim/lib/include/rtems/score/cpu.h:40, from ../../../../../../rtems/c/src/../../cpukit/score/src/percpuasm.c:19:

../../cpukit/../../../m32csim/lib/include/rtems/score/basedefs.h:244:17: error: size of array 'rtems_static_assert_PER_CPU_OFFSET_EXECUTING' is negative

typedef int rtems_static_assert_ ## msg [(cond) ? 1 : -1]

../../../../../../rtems/c/src/../../cpukit/score/src/percpuasm.c:98:1: note: in expansion of macro 'RTEMS_STATIC_ASSERT'

RTEMS_STATIC_ASSERT(

../../cpukit/../../../m32csim/lib/include/rtems/score/basedefs.h:244:17: error: size of array 'rtems_static_assert_PER_CPU_OFFSET_HEIR' is negative

typedef int rtems_static_assert_ ## msg [(cond) ? 1 : -1]

../../../../../../rtems/c/src/../../cpukit/score/src/percpuasm.c:103:1: note: in expansion of macro 'RTEMS_STATIC_ASSERT'

RTEMS_STATIC_ASSERT(

#2823 22 months ago fixed unspecified Joel Sherrill Sebastian Huber 11 months ago
Summary

Nearly all m68k BSPs do not Build on Master

Description

av5282 is the first

In file included from ../../cpukit/../../../av5282/lib/include/rtems/score/types.h:22:0,

from ../../cpukit/../../../av5282/lib/include/rtems/score/cpu.h:26, from ../../../../../../rtems/c/src/../../cpukit/score/src/percpuasm.c:19:

../../cpukit/../../../av5282/lib/include/rtems/score/basedefs.h:241:5: error: static assertion failed: "PER_CPU_OFFSET_EXECUTING"

_Static_assert(cond, # msg)

../../../../../../rtems/c/src/../../cpukit/score/src/percpuasm.c:98:1: note: in expansion of macro 'RTEMS_STATIC_ASSERT'

RTEMS_STATIC_ASSERT(

../../cpukit/../../../av5282/lib/include/rtems/score/basedefs.h:241:5: error: static assertion failed: "PER_CPU_OFFSET_HEIR"

_Static_assert(cond, # msg)

../../../../../../rtems/c/src/../../cpukit/score/src/percpuasm.c:103:1: note: in expansion of macro 'RTEMS_STATIC_ASSERT'

RTEMS_STATIC_ASSERT(

#2824 22 months ago fixed arch/arm Joel Sherrill Sebastian Huber 11 months ago
Summary

arm/lpc23xx_tli800 no longer links tar01

Description

Normally I would add the test to those skipped but I thought this deserved a second look. Should this BSP be able to run this test? I thought it was a fairly beefy board.

arm-rtems4.12-gcc -B../../../../../lpc23xx_tli800/lib/ -specs bsp_specs -qrtems -mcpu=arm7tdmi-s -mthumb -Os -g -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs -Wl,--gc-sections -mcpu=arm7tdmi-s -mthumb -DHAVE_XZ=1 -o tar01.exe init.o test_cat.o initial_filesystem_tar.o initial_filesystem_tar_gz.o initial_filesystem_tar_xz.o -lrtemscpu -lz /data/home/joel/rtems-4.11-work/tools/4.12/bin/../lib/gcc/arm-rtems4.12/6.2.1/../../../../arm-rtems4.12/bin/ld: tar01.exe section .data' will not fit in region ROM_INT' /data/home/joel/rtems-4.11-work/tools/4.12/bin/../lib/gcc/arm-rtems4.12/6.2.1/../../../../arm-rtems4.12/bin/ld: region `ROM_INT' overflowed by 36 bytes collect2: error: ld returned 1 exit status gmake[7]: * [tar01.exe] Error 1

#2825 22 months ago fixed doc Sebastian Huber 11 months ago
Summary

Improve the fatal error handling chapter of the user manual

Description

At least replace the "Document me" markers with something useful.

#2826 22 months ago fixed arch/arm Chris Johns 11 months ago
Summary

arm_cp15_get_translation_table_base_control_register warning.

Description

arm_cp15_get_translation_table_base_control_register in c/src/lib/libcpu/arm/shared/include/arm-cp15.h returns a pointer however ttb_cr is not a pointer"

../../cpukit/../../../xilinx_zynq_zedboard/lib/include/libcpu/arm-cp15.h: In function 'arm_cp15_get_translation_table_base_control_register':
../../cpukit/../../../xilinx_zynq_zedboard/lib/include/libcpu/arm-cp15.h:401:10: warning: return makes pointer from integer without a cast [-Wint-conversion]
   return ttb_cr;
          ^~~~~~
#2829 22 months ago fixed unspecified Joel Sherrill Chris Johns 11 months ago
Summary

xz git URL in README is broken

Description

Use http://git.tukaani.org/?

#2835 22 months ago duplicate tool/gcc Sebastian Huber Needs Funding 11 months ago
Summary

Ada support is broken on SMP configurations

Description

The Ada support is the last user of a task variable: rtems_ada_self. This doesn't work on SMP configurations. The Ada support in GCC should be changed to use a function call or C11 thread-local storage.

#2836 22 months ago fixed score Joel Sherrill Joel Sherrill 11 months ago
Summary

Add posix_devctl()

Description

The posix_devctl() method is defined in POSIX 1003.26 and required by the FACE POSIX profiles. The only use case that needs to be supported is FIONBIO on sockets per the FACE Technical Standard.

ioctl() is not a standardized method per POSIX and is not included in the FACE Profiles.

Making operations non-blocking can also be done with fcntl() but due to RTOS qualification concerns, fcntl() is not included in the more stringent FACE profiles. Specifically, it is not in the Safety Base profile which matches the RTEMS POSIX capabilities.

This requires adding the <devctl.h> file to newlib. That has been done. I am testing my implementation but a tool update will be needed before this can be pushed to the community. This is OK because we have other reasons to move to a new gcc and newlib version soon.

#2838 22 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Termios task driven mode should use mutex for device operations

Description

Termios has a task driven mode (TERMIOS_TASK_DRIVEN). This mode aims to avoid long sections with disabled interrupts. This is only partly implemented since the device level state is still protected by disabled interrupts. Use a mutex to protect the device level state in task driven mode to fix this issue.

#2839 22 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Add new interrupt server driven Termios mode

Description

Add a new new interrupt server driven Termios mode (TERMIOS_IRQ_DRIVEN). This mode is identical to the interrupt driven mode except that a mutex is used for device level locking. The intended use case for this mode are device drivers that use the interrupt server, e.g. SPI or I2C connected devices.

#2840 22 months ago fixed dev/serial Sebastian Huber Sebastian Huber 7 months ago
Summary

Use self-contained mutexes for Termios framework

Description

Use C11 mutexes instead of Classic semaphores as a performance optimization and to simplify the application configuration.

A performance of Classic semaphores vs. C11 mutexes was measured on the arm/atsam BSP. A NXP SC16IS752 was connected via SPI. The RTEMS application used one task to read from the device and write it immediately back (look back via task). A development system constantly transmitted data at 115200 bits per second.

CPU usage by function with Classic semaphores:

name______________________________________|ratio___|1%_____2%________5%_____10%_____20%_______50%___100|
CPU_Thread_Idle_body                      | 22.454%|=================================                  |
atsam_spi_setup_transfer                  |  6.767%|====================                               |
Objects_Get                               |  5.859%|===================                                |
atsam_spi_interrupt                       |  4.483%|================                                   |
Event_Seize                               |  3.867%|==============                                     |
rtems_termios_enqueue_raw_characters      |  3.804%|==============                                     |
Timecounter_Binuptime                     |  3.715%|==============                                     |
Scheduler_priority_Block                  |  3.104%|============                                       |
rtems_semaphore_release                   |  3.018%|============                                       |
Scheduler_priority_Unblock                |  2.901%|===========                                        |
rtems_termios_read_tty                    |  2.777%|===========                                        |
ARMV7M_NVIC_Interrupt_dispatch            |  2.750%|===========                                        |
rtems_semaphore_obtain                    |  2.627%|==========                                         |
Thread_Do_dispatch                        |  2.351%|=========                                          |
ARMV7M_Interrupt_service_leave            |  2.086%|========                                           |
iproc                                     |  1.919%|=======                                            |
CPU_Context_switch                        |  

CPU usage by function with C11 mutexes:

name______________________________________|ratio___|1%_____2%________5%_____10%_____20%_______50%___100|
CPU_Thread_Idle_body                      | 33.395%|======================================             |
atsam_spi_setup_transfer                  |  6.061%|===================                                |
atsam_spi_interrupt                       |  4.690%|================                                   |
Mutex_recursive_Release                   |  3.011%|============                                       |
Event_Seize                               |  2.955%|===========                                        |
ARMV7M_NVIC_Interrupt_dispatch            |  2.885%|===========                                        |
rtems_termios_enqueue_raw_characters      |  2.771%|===========                                        |
rtems_termios_read_tty                    |  2.722%|===========                                        |
Timecounter_Binuptime                     |  2.653%|==========                                         |
Thread_Do_dispatch                        |  2.240%|========                                           |
Scheduler_priority_Block                  |  2.112%|========                                           |
ARMV7M_Interrupt_service_leave            |  2.100%|========                                           |
Scheduler_priority_Unblock                |  1.919%|=======                                            |
Mutex_recursive_Acquire                   |  1.876%|======                                             |
iproc                                     |  1.773%|======                                             |
CPU_Context_switch                        |  

The change resulted in 10% more total idle time on the system.

#2841 22 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Add NXP SC16IS752 serial device driver

Description

Add Termios device driver for NXP SC16IS752 (RS232/RS485 over SPI or I2C).

#2843 22 months ago fixed unspecified Sebastian Huber Sebastian Huber 8 months ago
Summary

Use self-contained objects instead of Classic API for drivers and support libraries

Description

The Classic API has some weaknesses:

  • Dynamic memory (the workspace) is used to allocate object pools. This requires a complex configuration with heavy use of the C pre-processor.
  • Objects are created via function calls which return an object identifier. The object operations use this identifier and map it internally to an object representation.
  • The objects reside in a table, e.g. they are suspect to false sharing of cache lines.
  • The object operations use a rich set of options and attributes. For each object operation these parameters must be evaluated and validated at run-time to figure out what to do exactly for this operation.

The overhead for Classic API mutexes used for example in Termios and the SPI framework is significant, see discussion:

https://lists.rtems.org/pipermail/devel/2016-December/016543.html

There are some API options available:

  1. Use C11 mutexes and condition variables.
  2. Turn the POSIX synchronization objects into self-contained objects and use them.
  3. Use FreeBSD synchronization objects like MUTEX(9) or CONDVAR(9).
  4. Add RTEMS-specific self-contained synchronization objects and use them.

Option 1. and 2. lack support for binary semaphores which are used for task/interrupt synchronization, e.g. Termios.

Option 2. needs run-time evaluation to figure out the actual object variant, e.g. non-recursive, recursive, ceiling, error-checking, robust POSIX mutex.

Option 3. uses hash tables, thus it is not suitable for real-time systems.

Option 1. and 2. lack support for user-defined object names that may help for system diagnostic, tracing and debugging.

Option 4. could be used to avoid all shortcomings of options 1-3. It would be trivial to implement, test and document.

In order to enable user-defined object names one option is to add a const char *name member to Thread_queue_Queue.

#2844 22 months ago fixed fs Sebastian Huber Sebastian Huber 11 months ago
Summary

JFFS2: Add IO controls to get filesystem instance information and force a garbage collection

Description

Some applications need to control the garbage collection of the JFFS2 filesystem. For example during bootloader to application transitions with execute in place flashes (XIP).

#2845 21 months ago fixed doc Sebastian Huber 11 months ago
Summary

Add I2C framework documentation

Description

The new I2C framework lacks documentation.

#2849 21 months ago fixed doc Sebastian Huber 11 months ago
Summary

ATA/IDE support in RTEMS is out-dated

Description

The ATA/IDE support in RTEMS is out-dated. New platforms should consider to use the SATA support provided by FreeBSD via libbsd.

Update the documentation accordingly.

#2850 21 months ago fixed doc Sebastian Huber 11 months ago
Summary

Driver manual covers non-existent Analog Driver

Description

Remove this chapter from the documentation.

#2851 21 months ago fixed doc Sebastian Huber 11 months ago
Summary

Driver manual covers non-existent Discrete Driver

Description

Remove this chapter from the documentation.

#2853 21 months ago fixed doc Sebastian Huber 11 months ago
Summary

Driver manual covers non-existent Non-Volatile Memory Driver

Description

Remove this chapter from the documentation.

#2858 21 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Add user defined thread names

Description

Add user defined thread names to ease debugging, enhance the system diagnostics and improve compatibility to other systems, e.g. Linux and FreeBSD.

Implement pthread_setname_np() and pthread_getname_np(). Add CONFIGURE_MAXIMUM_THREAD_NAME_SIZE to the application configuration options. Add a application configuration dependent storage area for thread names to the thread control block.

#2859 21 months ago fixed posix Gedare Gedare 11 months ago
Summary

Implement POSIX Shared Memory Objects

Description

POSIX Shared Memory is a widely used API for inter-process communication. The functions in the API include:

#2862 21 months ago fixed doc Chris Johns Chris Johns 11 months ago
Summary

docs.rtems.org Add support to ReST format releases.

Description

Add support to the releases section of the web site to handle ReST packages. The catalogues have a legacy field for texinfo docs.

The 4.11.0 and 4.11.1 releases need to have a catalogue added because this did not exist when those releases were created.

#2863 21 months ago duplicate doc Joel Sherrill Joel Sherrill 11 months ago
Summary

Update POSIX 1003.1 Compliance Guide for ReST

Description

The POSIX 1003.1 Compliance Guide should be auto-generated from a spreadsheet into the ReST format. My vague recollection is that we used shell scripts to do this for texinfo output.

I will have to decipher what we used to do and define a new procedure.

This impacts 4.11 and newer. One issue is having correct information for what methods are present on a branch. The FACE Conformance Test Suite can be used for ~800 of the methods.

#2864 21 months ago fixed doc Chris Johns 11 months ago
Summary

docs.rtems.org Automatic update of branches content when a rtems-doc.git change is made.

Description

Add support to automatically update the branches when a git commit happens.

#2865 21 months ago fixed doc Chris Johns Chris Johns 11 months ago
Summary

Coverpage installed when building the docs repeats catalogue.xml entries

Description

The catalogue repeats entries.

#2867 21 months ago fixed tool Stavros Passas Chris Johns 11 months ago
Summary

Fix exclude rule in rtems-test-check

Description

rtems-test-check is responsible of checking the testsuite configuration of a given BSP and adapt it based on a given "command". Currently for the "exclude" command, we never exclude anything, the output of the script is always the whole list of the input tests.

This happens because the script always starts with output = $tests and appends on the list the tests that are not excluded, so the output is always all the tests.

#2868 21 months ago fixed arch/arm David Binderman Gedare Bloom <gedare@…> 11 months ago
Summary

src/c/src/lib/libbsp/arm/smdk2410/smc/smc.c: 3 * pointless local variables ?

Description

[src/c/src/lib/libbsp/arm/smdk2410/smc/smc.c:235]: (style) Variable 'cnt1' is modified but its new value is never used. [src/c/src/lib/libbsp/arm/smdk2410/smc/smc.c:243]: (style) Variable 'cnt2' is modified but its new value is never used. [src/c/src/lib/libbsp/arm/smdk2410/smc/smc.c:246]: (style) Variable 'cnt3' is modified but its new value is never used.

$ egrep "cnt1|cnt2|cnt3" src/c/src/lib/libbsp/arm/smdk2410/smc/smc.c

uint32_t pblock, i, j, lblock, zone, count, cnt1, cnt2, cnt3; cnt1 = 0; cnt2 = 0; cnt3 = 0;

cnt1++;

cnt2++; cnt3++;

$

Maybe someone left some debug code in ?

#2873 20 months ago fixed arch/arm David Binderman Gedare Bloom <gedare@…> 11 months ago
Summary

src/c/src/lib/libbsp/arm/raspberrypi/i2c/i2c.c:320: defective error checking ?

Description

src/c/src/lib/libbsp/arm/raspberrypi/i2c/i2c.c:320]: (style) Checking if unsigned variable 'rv' is less than zero.

Source code is

rv = rpi_i2c_setup_transfer(bus);

if ( rv < 0 ) {

but

uint32_t rv = 0;

and

static int rpi_i2c_setup_transfer(rpi_i2c_bus *bus)

Suggest put return value into an int local variable, then sanity check it, then assign it to rv.

#2874 20 months ago fixed arch/powerpc David Binderman Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

src/c/src/lib/libbsp/powerpc/beatnik/marvell/gt_timer.c: 4 * pointless check ?

Description

[src/c/src/lib/libbsp/powerpc/beatnik/marvell/gt_timer.c:102]: (style) Checking if unsigned variable 'timer' is less than zero. [src/c/src/lib/libbsp/powerpc/beatnik/marvell/gt_timer.c:109]: (style) Checking if unsigned variable 'timer' is less than zero. [src/c/src/lib/libbsp/powerpc/beatnik/marvell/gt_timer.c:117]: (style) Checking if unsigned variable 'timer' is less than zero. [src/c/src/lib/libbsp/powerpc/beatnik/marvell/gt_timer.c:128]: (style) Checking if unsigned variable 'timer' is less than zero.

Parameter "timer" is only ever type uint32_t, so any check < 0 seem pointless.

#2877 20 months ago fixed score Stavros Passas joel.sherrill@… 11 months ago
Summary

DHCP client fails on complex networks

Description

What happens is that on networks with more than one DHCP servers, or on networks that use multiple vlans it can happen that After a DHCP discover our client broadcasts, it receives multiple offers, which is perfectly fine based on the DHCP RFC.

However our implementation of a DHCP client, expects a linear execution flow:

  1. Broadcast a DHCP discover;
  2. Wait for a DHCP offer;
  3. Transmit a DHCP request;
  4. Wait for a DHCP ack;

However the network stack is not cleaned between the reception of a DHCP offer and a DHCP ack, so if multiple offers are received, just the first one will be processed during the "Receive DHCP offer" phase, and the next one will be received when we expect a "DHCP ack", which makes our implementation assume the DHCP handshake is invalid and fail. Thus we restart the network and retry the whole process from the beginning which will cause the same issue again.

This issue that is present from when I remember in RTEMS, definitely from 4.10 up to now.

#2878 20 months ago fixed arch/sparc David Binderman Daniel Hellstrom 11 months ago
Summary

src/c/src/lib/libbsp/sparc/shared/can/occan.c:1573: broken error checking ?

Description

src/c/src/lib/libbsp/sparc/shared/can/occan.c:1573]: (style) Checking if unsigned variable 'speed=pelican_speed_auto(can)' is less than zero.

Source code is

if ( (speed=pelican_speed_auto(can)) < 0 ){

/* failed */ return RTEMS_IO_ERROR;

}

but

unsigned int speed;

and

static int pelican_speed_auto(occan_priv *priv);

I am not sure which C compiler gets using in rtems, but I do know that gcc compiler flag -Wtype-limits will flag this kind of problem.

#2879 20 months ago fixed score David Binderman Chris Johns 11 months ago
Summary

src/cpukit/libdebugger/rtems-debugger-server.c: four problems

Description

1.

src/cpukit/libdebugger/rtems-debugger-server.c:1306]: (style) Redundant condition: extended. '!extended || (extended && check_pid(pid))' is equivalent to '!extended || check_pid(pid)'

Suggest simplify.

2.

src/cpukit/libdebugger/rtems-debugger-server.c:1858]: (warning) Possible null pointer dereference: rtems_debugger

Source code is

  if (r < 0) {
    rtems_printf(printer, "error: rtems-db: remote begin: %s: %s\n",
                 rtems_debugger->remote->name, strerror(errno));
    free(rtems_debugger);
    rtems_debugger = NULL;
  }

  /*
   * Reset at the end of the session.
   */
  rtems_debugger->flags = 0;

Suggest adding return -1 inside the if.

3.

src/cpukit/libdebugger/rtems-debugger-server.c:906]: (style) Redundant condition: extended. '!extended || (extended && check_pid(pid))' is equivalent to '!extended || check_pid(pid)'

Duplicate.

4.

src/cpukit/libdebugger/rtems-debugger-server.c:956]: (warning) Char literal compared with pointer 'p'. Did you intend to dereference it?

Source code is

  while (p != NULL && p != '\0') {

Maybe better code

  while (p != NULL && *p != '\0') {
#2880 20 months ago wontfix unspecified David Binderman 11 months ago
Summary

src/cpukit/libfs/src/jffs2/src/readinode.c:189: faulty logic

Description

src/cpukit/libfs/src/jffs2/src/readinode.c:189]: (style) Condition 'tn.fn.ofs>=offset' is always true

Source code is

if (tn->fn->ofs < offset)

next = tn->rb.rb_right;

else if (tn->fn->ofs >= offset)

next = tn->rb.rb_left;

else

break;

Maybe better code

if (tn->fn->ofs < offset)

next = tn->rb.rb_right;

else if (tn->fn->ofs > offset)

next = tn->rb.rb_left;

else

break;

#2883 20 months ago fixed arch/arm David Binderman Pavel Pisa 11 months ago
Summary

src/c/src/lib/libbsp/arm/tms570/console/tms570-sci.c:248: strange expression ?

Description

src/c/src/lib/libbsp/arm/tms570/console/tms570-sci.c:248]: (style) Same expression on both sides of '|'.

Source code is

uint32_t flr_tx_ready = TMS570_SCI_FLR_TX_EMPTY | TMS570_SCI_FLR_TX_EMPTY;

#2885 20 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

Fix rtems_rate_monotonic_postponed_job_count() prototype

Description

rtems_rate_monotonic_postponed_job_count() should return an RTEMS status code. It should be renamed to rtems_rate_monotonic_get_postponed_job_count() or rtems_rate_monotonic_get_postponed_jobs() (similar to rtems_rate_monotonic_get_statistics()).

#2889 20 months ago fixed score Stavros Passas Stavros Passas <stavros.passas@…> 11 months ago
Summary

RTEMS_STACK_CHECKER_EXTENSION has incomplete definition

Description

The extension for the stack checker defines 8 entries, while the structure for RTEMS extensions gets 9 arguments. This causes warnings to appear on applications compiled with -Werror, or similar flags.

The handler that is missing is for the terminate callback, so a 0 entry would be enough to fix this error.

#2890 20 months ago fixed score Stavros Passas Sebastian Huber <sebastian.huber@…> 11 months ago
Summary

_RBTree_Initialize_node generates warnings

Description

Currently, when _RBTree_Initialize_node is used, it generates warnings of unused variables. I traced the issue down to the variable being used only if RTEMS_DEBUG is set.

Thus, the argument should be marked as RTEMS_UNUSED, if RTENS_DEBUG is not set.

#2893 20 months ago fixed config Sebastian Huber Sebastian Huber 11 months ago
Summary

Remove CONFIGURE_SMP_APPLICATION

Description

SMP support must be enabled with the CONFIGURE_SMP_APPLICATION configuration option. Remove this option and enable the SMP support if CONFIGURE_SMP_MAXIMUM_PROCESSORS > 1.

#2894 20 months ago fixed config Sebastian Huber Sebastian Huber 11 months ago
Summary

Rename CONFIGURE_SMP_MAXIMUM_PROCESSORS to CONFIGURE_MAXIMUM_PROCESSORS

Description

Rename CONFIGURE_SMP_MAXIMUM_PROCESSORS to CONFIGURE_MAXIMUM_PROCESSORS since the SMP part is superfluous.

#2895 20 months ago fixed config Sebastian Huber Sebastian Huber 11 months ago
Summary

Prefix the confdefs.h internal defines with an underscore

Description

Prefix the confdefs.h internal defines with an underscore to simplify the review of this extremely complex header file.

#2896 20 months ago wontfix tool/rsb Joel Sherrill Chris Johns 11 months ago
Summary

RSB requirements are missing pax

Description

Loading a new VM, I noticed that pax is needed. It isn't mentioned in the RSB manual at all.

I can only accurately fix this for Centos 7 but we can safely assume that advice applies to Centos 6, Fedora, and RHEL.

Can users of other distributions check about pax. Please

#2897 20 months ago fixed score Kevin Kirspel Needs Funding 11 months ago
Summary

Update termios.h to match the latest FREEBSD definitions

Description

The FREEBSD struct termios separates out the input and output baud rates into individual speed_t variables. It also supports more flag options. The big benefit is that the rtems-libbsd tty code can be ported cleanly without the need to fixup the input and output baud rates. This should be a transparent change unless someone was manipulating the baud rates directly through the c_cflags (not using the cfgetispeed, cfgetospeed, cfsetispeed, cfsetospeed functions).

#2905 20 months ago fixed arch/sparc Tanu Hari Dixit Daniel Hellstrom 11 months ago
Summary

Merge LEON

Description

Merge LEON

Students: Past, Present, and Potential Students

Status: Some work may be done.

Introduction: Merge Leon RTEMS and mainstream RTEMS merge the Leon DriverManager, samples, and LEON-RTEMS into mainstream RTEMS.

Goal: Concise statement of the overall goal of the project. Refine this initial statement to include: project deliverables (code, docs, testing), required/suggested methodology, standards of quality, possible goal extensions beyond the main objective.

Requirements: List the requirements and level of expertise you estimate are required by the developer tackling this project will have to have: Required level of programming language(s), specific areas of RTEMS or tools, level of familiarity with RTEMS, cross-development, GNU/Linux, etx., development/documentation/testing tools, mathematical/algorithmic background, other desirable skills.

Resources: Current RTEMS developers, papers, etc that may help you in this project.

Acknowledgements

  • who helped and did work

Miscellaneous Sections

As the project progresses, you will need to add build instructions, etc and this page will evolve from a project description into a HOWTO.

References

  • TBD

Other sections: If you have more to say about the project that doesn't fit in the proposed sections of this template, feel free to add other sections at will.

#2906 20 months ago fixed doc Chris Johns 11 months ago
Summary

rtems-doc waf configure does not detect sphinxcontrib.bibtex status

Description

The rtems-docs requires the Sphinx contribution extension for bibtex to build.

A configure check should be added to see if the extension is installed and an error raised or the documentation conditionally built.

It is not clear to me if bibtex needs Tex Alive. Requiring Tex on all hosts to build the documentation is a regression so the extension will need to be removed or a fall back position taken where degraded quality documentation in HTML is created.

#2909 20 months ago fixed score Sebastian Huber Chris Johns 11 months ago
Summary

xz: Support for 64-bit CRC is build although XZ_USE_CRC64 is not defined

Description

This leads to:

../../../../../../rtems/c/src/../../cpukit/libmisc/xz/xz_crc64.c:21:16: warning: no previous prototype for 'xz_crc64_init' [-Wmissing-prototypes] ../../../../../../rtems/c/src/../../cpukit/libmisc/xz/xz_crc64.c:40:20: warning: no previous prototype for 'xz_crc64' [-Wmissing-prototypes]

We should enable the 64-bit CRC or remove this file from the build.

#2912 20 months ago fixed score Sebastian Huber Chris Johns 11 months ago
Summary

libdebugger: control reaches end of non-void function

Description

../../../../../../rtems/c/src/../../cpukit/libdebugger/rtems-debugger-server.c:393:1: warning: control reaches end of non-void function [-Wreturn-type] ../../../../../../rtems/c/src/../../cpukit/libdebugger/rtems-debugger-server.c:405:1: warning: control reaches end of non-void function [-Wreturn-type]

#2916 19 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

termios: Change receive callback invocation to enable select() and poll() support

Description

Call the receive callback in case a read will succeed without to block. This enables the use of the receive callback for a poll() and select() support. Increase raw input buffer size to allow buffering of one line.

#2917 19 months ago fixed score Sebastian Huber Sebastian Huber 11 months ago
Summary

termios: Make write POSIX compatible

Description

Currently only blocking read/write operations are implemented. A blocking write must transfer at least one character. It should not wait for the device for the second character and so on.

#2923 19 months ago wontfix score Joel Sherrill Sebastian Huber 11 months ago
Summary

Questionable Code in resource_snapshot.c

Description

Coverity URL:

https://scan5.coverity.com/reports.htm#v29808/p10069/fileInstanceId=108958257&defectInstanceId=30877219&mergedDefectId=1399703

Coverity Scan doesn't like taking the address of a single uint32_t and then treating it as an array pointer. I think the code is likely doing what is intended but there is an implicit linkable between the order of the fields in the structure here and the class numbers used in the object IDs. Is there a way to improve this code and reduce the linkage?

141

  1. address_of: Taking address with &snapshot->active_posix_keys yields a singleton pointer.
  2. assign: Assigning: active = &snapshot->active_posix_keys.

142 active = &snapshot->active_posix_keys; 143

  1. Condition i < 19U /* sizeof (objects_info_table) / sizeof (objects_info_table[0]) */, taking true branch.

144 for (i = 0; i < RTEMS_ARRAY_SIZE(objects_info_table); ++i) { 145 const Objects_Information *information; 146 147 information = _Objects_Get_information( 148 objects_info_table[i].api, 149 objects_info_table[i].cls 150 ); 151

  1. Condition information != NULL, taking true branch.

152 if (information != NULL) { CID 1399703 (#1 of 1): Out-of-bounds access (ARRAY_VS_SINGLETON)

  1. ptr_arith: Using active as an array. This might corrupt or misinterpret adjacent memory locations.

153 active[i] = _Objects_Active_count(information);

#2924 19 months ago fixed arch/sparc Joel Sherrill Daniel Hellstrom 11 months ago
Summary

Warnings in SPARC BSPs

Description

As of today, the following warnings exist for SPARC BSPs.

log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/console/debugputs.c:43:5: warning: this 'while' clause does not guard... [-Wmisleading-indentation] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/amba/ahbstat.c:156:3: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/amba/ahbstat.c:156:3: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/drvmgr/ambapp_bus.c:647:4: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/drvmgr/ambapp_bus.c:647:4: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/drvmgr/leon2_amba_bus.c:168:3: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/drvmgr/leon2_amba_bus.c:168:3: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/irq/genirq.c:244:3: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/irq/genirq.c:244:3: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/spw/grspw_router.c:213:4: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/spw/grspw_router.c:213:4: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-leon2.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon2/../../sparc/shared/uart/apbuart.c:574:21: warning: format '%x' expects argument of type 'unsigned int', but argument 2 has type 'apbuart_priv * {aka struct <anonymous> *}' [-Wformat=] log/sparc-leon3.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/amba/ahbstat.c:156:3: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-leon3.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/amba/ahbstat.c:156:3: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-ngmp.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/amba/ahbstat.c:156:3: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-ngmp.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/amba/ahbstat.c:156:3: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-leon3.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/drvmgr/ambapp_bus.c:647:4: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-leon3.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/drvmgr/ambapp_bus.c:647:4: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-ngmp.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/drvmgr/ambapp_bus.c:647:4: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-ngmp.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/drvmgr/ambapp_bus.c:647:4: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-leon3.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/irq/genirq.c:244:3: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-leon3.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/irq/genirq.c:244:3: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-ngmp.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/irq/genirq.c:244:3: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-ngmp.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/irq/genirq.c:244:3: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-leon3.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/spw/grspw_router.c:213:4: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-leon3.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/spw/grspw_router.c:213:4: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-ngmp.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/spw/grspw_router.c:213:4: warning: implicit declaration of function 'printk' [-Wimplicit-function-declaration] log/sparc-ngmp.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/spw/grspw_router.c:213:4: warning: nested extern declaration of 'printk' [-Wnested-externs] log/sparc-leon3.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/uart/apbuart.c:574:21: warning: format '%x' expects argument of type 'unsigned int', but argument 2 has type 'apbuart_priv * {aka struct <anonymous> *}' [-Wformat=] log/sparc-ngmp.log:../../../../../../../../rtems/c/src/lib/libbsp/sparc/leon3/../../sparc/shared/uart/apbuart.c:574:21: warning: format '%x' expects argument of type 'unsigned int', but argument 2 has type 'apbuart_priv * {aka struct <anonymous> *}' [-Wformat=]

#2930 19 months ago fixed score Joel Sherrill Daniel Hellstrom 11 months ago
Summary

Coverity Reports Out of Bounds Read in drvmgr_print.c

Description

https://scan5.coverity.com/reports.htm#v29808/p10069/fileInstanceId=109359850&defectInstanceId=30967449&mergedDefectId=1399730

354 printf(" DRIVER ID: 0x%llx\n", drv->drv_id);

  1. Condition drv->name, taking true branch.

355 printf(" NAME: %s\n", drv->name ? drv->name : "NO_NAME"); 356 printf(" BUS TYPE: %d\n", drv->bus_type); 357 printf(" OPERATIONS:\n");

  1. alias: Assigning: ppfunc = &drv->ops->init[0]. ppfunc now points to element 0 of drv->ops->init (which consists of 4 4-byte elements).
  2. Condition i < 6U /* sizeof (struct drvmgr_drv_ops) / sizeof (void (*)(void)) */, taking true branch.
  3. Condition i < 6U /* sizeof (struct drvmgr_drv_ops) / sizeof (void (*)(void)) */, taking true branch.
  4. cond_at_most: Checking i < 6U implies that i may be up to 5 on the true branch.

358 for (i = 0, ppfunc = (fun_ptr *)&drv->ops->init[0]; 359 i < DRVMGR_OPS_NUM(struct drvmgr_drv_ops); i++)

  1. Jumping back to the beginning of the loop.

CID 1399730 (#1 of 1): Out-of-bounds read (OVERRUN)

  1. overrun-local: Overrunning array of 4 4-byte elements at element index 5 (byte offset 20) by dereferencing pointer ppfunc + i.

360 printf(" %s %p\n", drv_ops_names[i], ppfunc[i]); 361 printf(" NO. DEVICES: %d\n", drv->dev_cnt); 362

#2935 19 months ago wontfix score Martin Aberg joel.sherrill@… 11 months ago
Summary

Termios task driven mode not compatible with SMP

Description

When the Termios task driven functioning mode is used, rtems_termios_open_tty() calls rtems_task_create() with RTEMS_NO_PREEMPT in the initial task mode parameter. RTEMS_NO_PREEMPT is not supported on SMP.

rtems_task_create() returns RTEMS_UNSATISFIED in this SMP scenario and Termios ends up in rtems_fatal_error_occurred().

Termios starts the RX and TX tasks successfully on SMP if RTEMS_NO_PREEMPT is removed from the initial task modes of these tasks. However, I suspect there may be assumptions on the NO_PREEMPT mode for the RX and TX tasks in other parts of Termios.

#2941 19 months ago invalid tool/rsb DHANPAL SINGH 11 months ago
Summary

building rsb freezes

Description

dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~$ cd dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~$ mkdir -p development/rtems/rsb dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~$ cd development/rtems/rsb dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems/rsb$ git clone git://git.rtems.org/rtems-source-builder.git fatal: destination path 'rtems-source-builder' already exists and is not an empty directory. dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems/rsb$ cd rtems-source-builder dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems/rsb/rtems-source-builder$ cd rtems dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems/rsb/rtems-source-builder/rtems$ ../source-builder/sb-set-builder --prefix=$HOME/development/rtems/4.12 4.12/rtems-sparc RTEMS Source Builder - Set Builder, 4.12 (10d9e2dfacf7) Build Set: 4.12/rtems-sparc Build Set: 4.12/rtems-autotools.bset Build Set: 4.12/rtems-autotools-internal.bset config: tools/rtems-autoconf-2.69-1.cfg package: autoconf-2.69-x86_64-linux-gnu-1 Creating source directory: sources download: ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.gz -> sources/autoconf-2.69.tar.gz downloading: sources/autoconf-2.69.tar.gz - 1.8MB of 1.8MB (100%) building: autoconf-2.69-x86_64-linux-gnu-1 config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-linux-gnu-1 download: ftp://ftp.gnu.org/gnu/automake/automake-1.12.6.tar.gz -> sources/automake-1.12.6.tar.gz downloading: sources/automake-1.12.6.tar.gz - 2.0MB of 2.0MB (100%) Creating source directory: patches download: https://git.rtems.org/rtems-tools/plain/tools/4.12/automake/automake-1.12.6-bugzilla.redhat.com-1239379.diff -> patches/automake-1.12.6-bugzilla.redhat.com-1239379.diff downloading: patches/automake-1.12.6-bugzilla.redhat.com-1239379.diff - 0.0 bytedownloading: patches/automake-1.12.6-bugzilla.redhat.com-1239379.diff - 408.0 bytes of 408.0 bytes (100%) building: automake-1.12.6-x86_64-linux-gnu-1 cleaning: autoconf-2.69-x86_64-linux-gnu-1 cleaning: automake-1.12.6-x86_64-linux-gnu-1 Build Set: Time 0:00:44.961728 Build Set: 4.12/rtems-autotools-base.bset config: tools/rtems-autoconf-2.69-1.cfg package: autoconf-2.69-x86_64-linux-gnu-1 building: autoconf-2.69-x86_64-linux-gnu-1 reporting: tools/rtems-autoconf-2.69-1.cfg -> autoconf-2.69-x86_64-linux-gnu-1.txt reporting: tools/rtems-autoconf-2.69-1.cfg -> autoconf-2.69-x86_64-linux-gnu-1.xml config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-linux-gnu-1 building: automake-1.12.6-x86_64-linux-gnu-1 reporting: tools/rtems-automake-1.12.6-1.cfg -> automake-1.12.6-x86_64-linux-gnu-1.txt reporting: tools/rtems-automake-1.12.6-1.cfg -> automake-1.12.6-x86_64-linux-gnu-1.xml installing: autoconf-2.69-x86_64-linux-gnu-1 -> /home/dhanpal/development/rtems/4.12 installing: automake-1.12.6-x86_64-linux-gnu-1 -> /home/dhanpal/development/rtems/4.12 cleaning: autoconf-2.69-x86_64-linux-gnu-1 cleaning: automake-1.12.6-x86_64-linux-gnu-1 Build Set: Time 0:00:15.092702 Build Set: Time 0:01:00.058748 config: devel/expat-2.1.0-1.cfg package: expat-2.1.0-x86_64-linux-gnu-1 download: http://downloads.sourceforge.net/project/expat/expat/2.1.0/expat-2.1.0.tar.gz -> sources/expat-2.1.0.tar.gz

redirect: https://nchc.dl.sourceforge.net/project/expat/expat/2.1.0/expat-2.1.0.tar.gz

downloading: sources/expat-2.1.0.tar.gz - 549.4kB of 549.4kB (100%) building: expat-2.1.0-x86_64-linux-gnu-1 reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.txt reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.xml config: tools/rtems-binutils-2.27-1.cfg package: sparc-rtems4.12-binutils-2.27-x86_64-linux-gnu-1 download: ftp://ftp.gnu.org/gnu/binutils/binutils-2.27.tar.bz2 -> sources/binutils-2.27.tar.bz2 downloading: sources/binutils-2.27.tar.bz2 - 24.9MB of 24.9MB (100%) download: https://git.rtems.org/rtems-tools/plain/tools/4.12/binutils/binutils-2.26-gas-reloc.patch -> patches/binutils-2.26-gas-reloc.patch downloading: patches/binutils-2.26-gas-reloc.patch - 0.0 bytes of 510.0 bytes (0downloading: patches/binutils-2.26-gas-reloc.patch - 510.0 bytes of 510.0 bytes (100%) building: sparc-rtems4.12-binutils-2.27-x86_64-linux-gnu-1 reporting: tools/rtems-binutils-2.27-1.cfg -> sparc-rtems4.12-binutils-2.27-x86_64-linux-gnu-1.txt reporting: tools/rtems-binutils-2.27-1.cfg -> sparc-rtems4.12-binutils-2.27-x86_64-linux-gnu-1.xml config: tools/rtems-gcc-6.3.0-newlib-2.5.0.20170228-1.cfg package: sparc-rtems4.12-gcc-6.3.0-newlib-2.5.0.20170228-x86_64-linux-gnu-1 download: ftp://ftp.gnu.org/gnu/gcc/gcc-6.3.0/gcc-6.3.0.tar.bz2 -> sources/gcc-6.3.0.tar.bz2 downloading: sources/gcc-6.3.0.tar.bz2 - 95.3MB of 95.3MB (100%) download: ftp://sourceware.org/pub/newlib/newlib-2.5.0.20170228.tar.gz -> sources/newlib-2.5.0.20170228.tar.gz downloading: sources/newlib-2.5.0.20170228.tar.gz - 17.1MB of 17.1MB (100%) download: http://www.mpfr.org/mpfr-2.4.2/mpfr-2.4.2.tar.bz2 -> sources/mpfr-2.4.2.tar.bz2 downloading: sources/mpfr-2.4.2.tar.bz2 - 1.0MB of 1.0MB (100%) download: http://www.multiprecision.org/mpc/download/mpc-0.8.1.tar.gz -> sources/mpc-0.8.1.tar.gz downloading: sources/mpc-0.8.1.tar.gz - 532.2kB of 532.2kB (100%) download: ftp://ftp.gnu.org/gnu/gmp/gmp-4.3.2.tar.bz2 -> sources/gmp-4.3.2.tar.bz2 downloading: sources/gmp-4.3.2.tar.bz2 - 1.8MB of 1.8MB (100%) building: sparc-rtems4.12-gcc-6.3.0-newlib-2.5.0.20170228-x86_64-linux-gnu-1

#2942 19 months ago invalid unspecified DHANPAL SINGH 11 months ago
Summary

rtems building error

Description

dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~$ export PATH=$HOME/development/rtems/4.12/bin:$PATH dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~$ cd dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~$ cd development/rtems dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems$ mkdir kernel dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems$ cd kernel dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems/kernel$ git clone git://git.rtems.org/rtems.git rtems Cloning into 'rtems'... remote: Counting objects: 504955, done. remote: Compressing objects: 100% (90780/90780), done. remote: Total 504955 (delta 407126), reused 499936 (delta 403143) Receiving objects: 100% (504955/504955), 73.12 MiB | 113 KiB/s, done. Resolving deltas: 100% (407126/407126), done. dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems/kernel$ cd rtems dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems/kernel/rtems$ ./bootstrap -c && ./bootstrap -p && \

$HOME/development/rtems/rsb/source-builder/sb-bootstrap

removing automake generated Makefile.in files removing configure files removing aclocal.m4 files Generating ./cpukit/libmisc/preinstall.am Generating ./cpukit/preinstall.am Generating ./cpukit/ftpd/preinstall.am Generating ./cpukit/mghttpd/preinstall.am Generating ./cpukit/score/preinstall.am Generating ./cpukit/score/cpu/no_cpu/preinstall.am Generating ./cpukit/score/cpu/arm/preinstall.am Generating ./cpukit/score/cpu/lm32/preinstall.am Generating ./cpukit/score/cpu/nios2/preinstall.am Generating ./cpukit/score/cpu/epiphany/preinstall.am Generating ./cpukit/score/cpu/sparc64/preinstall.am Generating ./cpukit/score/cpu/m32c/preinstall.am Generating ./cpukit/score/cpu/i386/preinstall.am Generating ./cpukit/score/cpu/mips/preinstall.am Generating ./cpukit/score/cpu/v850/preinstall.am Generating ./cpukit/score/cpu/or1k/preinstall.am Generating ./cpukit/score/cpu/bfin/preinstall.am Generating ./cpukit/score/cpu/sh/preinstall.am Generating ./cpukit/score/cpu/m68k/preinstall.am Generating ./cpukit/score/cpu/powerpc/preinstall.am Generating ./cpukit/score/cpu/moxie/preinstall.am Generating ./cpukit/score/cpu/sparc/preinstall.am Generating ./cpukit/libcrypt/preinstall.am Generating ./cpukit/dev/preinstall.am Generating ./cpukit/libpci/preinstall.am Generating ./cpukit/wrapup/preinstall.am Generating ./cpukit/sapi/preinstall.am Generating ./cpukit/libdl/preinstall.am Generating ./cpukit/libcsupport/preinstall.am Generating ./cpukit/pppd/preinstall.am Generating ./cpukit/dtc/libfdt/preinstall.am Generating ./cpukit/libnetworking/preinstall.am Generating ./cpukit/libfs/preinstall.am Generating ./cpukit/libfs/src/nfsclient/preinstall.am Generating ./cpukit/zlib/preinstall.am Generating ./cpukit/posix/preinstall.am Generating ./cpukit/librpc/preinstall.am Generating ./cpukit/telnetd/preinstall.am Generating ./cpukit/libdebugger/preinstall.am Generating ./cpukit/rtems/preinstall.am Generating ./cpukit/libmd/preinstall.am Generating ./c/src/wrapup/preinstall.am Generating ./c/src/libchip/preinstall.am Generating ./c/src/lib/libbsp/no_cpu/no_bsp/preinstall.am Generating ./c/src/lib/libbsp/preinstall.am Generating ./c/src/lib/libbsp/arm/csb336/preinstall.am Generating ./c/src/lib/libbsp/arm/smdk2410/preinstall.am Generating ./c/src/lib/libbsp/arm/realview-pbx-a9/preinstall.am Generating ./c/src/lib/libbsp/arm/preinstall.am Generating ./c/src/lib/libbsp/arm/stm32f4/preinstall.am Generating ./c/src/lib/libbsp/arm/atsam/preinstall.am Generating ./c/src/lib/libbsp/arm/rtl22xx/preinstall.am Generating ./c/src/lib/libbsp/arm/csb337/preinstall.am Generating ./c/src/lib/libbsp/arm/beagle/preinstall.am Generating ./c/src/lib/libbsp/arm/edb7312/preinstall.am Generating ./c/src/lib/libbsp/arm/lm3s69xx/preinstall.am Generating ./c/src/lib/libbsp/arm/lpc176x/preinstall.am Generating ./c/src/lib/libbsp/arm/lpc24xx/preinstall.am Generating ./c/src/lib/libbsp/arm/gumstix/preinstall.am Generating ./c/src/lib/libbsp/arm/xilinx-zynq/preinstall.am Generating ./c/src/lib/libbsp/arm/gdbarmsim/preinstall.am Generating ./c/src/lib/libbsp/arm/lpc32xx/preinstall.am Generating ./c/src/lib/libbsp/arm/tms570/preinstall.am Generating ./c/src/lib/libbsp/arm/raspberrypi/preinstall.am Generating ./c/src/lib/libbsp/arm/altera-cyclone-v/preinstall.am Generating ./c/src/lib/libbsp/lm32/milkymist/preinstall.am Generating ./c/src/lib/libbsp/lm32/lm32_evr/preinstall.am Generating ./c/src/lib/libbsp/nios2/nios2_iss/preinstall.am Generating ./c/src/lib/libbsp/epiphany/preinstall.am Generating ./c/src/lib/libbsp/epiphany/epiphany_sim/preinstall.am Generating ./c/src/lib/libbsp/sparc64/niagara/preinstall.am Generating ./c/src/lib/libbsp/sparc64/usiii/preinstall.am Generating ./c/src/lib/libbsp/m32c/m32cbsp/preinstall.am Generating ./c/src/lib/libbsp/i386/pc386/preinstall.am Generating ./c/src/lib/libbsp/mips/rbtx4938/preinstall.am Generating ./c/src/lib/libbsp/mips/rbtx4925/preinstall.am Generating ./c/src/lib/libbsp/mips/hurricane/preinstall.am Generating ./c/src/lib/libbsp/mips/jmr3904/preinstall.am Generating ./c/src/lib/libbsp/mips/malta/preinstall.am Generating ./c/src/lib/libbsp/mips/csb350/preinstall.am Generating ./c/src/lib/libbsp/v850/preinstall.am Generating ./c/src/lib/libbsp/v850/gdbv850sim/preinstall.am Generating ./c/src/lib/libbsp/or1k/preinstall.am Generating ./c/src/lib/libbsp/or1k/generic_or1k/preinstall.am Generating ./c/src/lib/libbsp/bfin/TLL6527M/preinstall.am Generating ./c/src/lib/libbsp/bfin/bf537Stamp/preinstall.am Generating ./c/src/lib/libbsp/bfin/eZKit533/preinstall.am Generating ./c/src/lib/libbsp/sh/gensh2/preinstall.am Generating ./c/src/lib/libbsp/sh/gensh1/preinstall.am Generating ./c/src/lib/libbsp/sh/gensh4/preinstall.am Generating ./c/src/lib/libbsp/sh/shsim/preinstall.am Generating ./c/src/lib/libbsp/m68k/mcf5235/preinstall.am Generating ./c/src/lib/libbsp/m68k/genmcf548x/preinstall.am Generating ./c/src/lib/libbsp/m68k/preinstall.am Generating ./c/src/lib/libbsp/m68k/mcf5329/preinstall.am Generating ./c/src/lib/libbsp/m68k/csb360/preinstall.am Generating ./c/src/lib/libbsp/m68k/av5282/preinstall.am Generating ./c/src/lib/libbsp/m68k/mcf5225x/preinstall.am Generating ./c/src/lib/libbsp/m68k/mvme147s/preinstall.am Generating ./c/src/lib/libbsp/m68k/mvme162/preinstall.am Generating ./c/src/lib/libbsp/m68k/gen68360/preinstall.am Generating ./c/src/lib/libbsp/m68k/mrm332/preinstall.am Generating ./c/src/lib/libbsp/m68k/gen68340/preinstall.am Generating ./c/src/lib/libbsp/m68k/mcf52235/preinstall.am Generating ./c/src/lib/libbsp/m68k/mvme167/preinstall.am Generating ./c/src/lib/libbsp/m68k/uC5282/preinstall.am Generating ./c/src/lib/libbsp/m68k/mvme147/preinstall.am Generating ./c/src/lib/libbsp/m68k/mcf5206elite/preinstall.am Generating ./c/src/lib/libbsp/powerpc/motorola_powerpc/preinstall.am Generating ./c/src/lib/libbsp/powerpc/virtex5/preinstall.am Generating ./c/src/lib/libbsp/powerpc/haleakala/preinstall.am Generating ./c/src/lib/libbsp/powerpc/ss555/preinstall.am Generating ./c/src/lib/libbsp/powerpc/qemuppc/preinstall.am Generating ./c/src/lib/libbsp/powerpc/gen83xx/preinstall.am Generating ./c/src/lib/libbsp/powerpc/gen5200/preinstall.am Generating ./c/src/lib/libbsp/powerpc/virtex/preinstall.am Generating ./c/src/lib/libbsp/powerpc/mpc55xxevb/preinstall.am Generating ./c/src/lib/libbsp/powerpc/t32mppc/preinstall.am Generating ./c/src/lib/libbsp/powerpc/virtex4/preinstall.am Generating ./c/src/lib/libbsp/powerpc/mvme3100/preinstall.am Generating ./c/src/lib/libbsp/powerpc/beatnik/preinstall.am Generating ./c/src/lib/libbsp/powerpc/qoriq/preinstall.am Generating ./c/src/lib/libbsp/powerpc/tqm8xx/preinstall.am Generating ./c/src/lib/libbsp/powerpc/mvme5500/preinstall.am Generating ./c/src/lib/libbsp/powerpc/mpc8260ads/preinstall.am Generating ./c/src/lib/libbsp/powerpc/psim/preinstall.am Generating ./c/src/lib/libbsp/moxie/moxiesim/preinstall.am Generating ./c/src/lib/libbsp/sparc/erc32/preinstall.am Generating ./c/src/lib/libbsp/sparc/leon3/preinstall.am Generating ./c/src/lib/libbsp/sparc/leon2/preinstall.am Generating ./c/src/lib/libcpu/arm/preinstall.am Generating ./c/src/lib/libcpu/lm32/preinstall.am Generating ./c/src/lib/libcpu/nios2/preinstall.am Generating ./c/src/lib/libcpu/sparc64/preinstall.am Generating ./c/src/lib/libcpu/i386/preinstall.am Generating ./c/src/lib/libcpu/mips/preinstall.am Generating ./c/src/lib/libcpu/or1k/preinstall.am Generating ./c/src/lib/libcpu/bfin/preinstall.am Generating ./c/src/lib/libcpu/sh/preinstall.am Generating ./c/src/lib/libcpu/m68k/preinstall.am Generating ./c/src/lib/libcpu/powerpc/preinstall.am Generating ./c/src/lib/libcpu/sparc/preinstall.am Generating ./c/src/ada/preinstall.am bash: /home/dhanpal/development/rtems/rsb/source-builder/sb-bootstrap: No such file or directory dhanpal@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems/kernel/rtems$ sudo -s [sudo] password for dhanpal: root@dhanpal-HP-Pavilion-15-Notebook-PC:~/development/rtems/kernel/rtems# ./bootstrap -c && ./bootstrap -p && \

$HOME/development/rtems/rsb/source-builder/sb-bootstrap

removing automake generated Makefile.in files removing configure files removing aclocal.m4 files Generating ./cpukit/libmisc/preinstall.am Generating ./cpukit/preinstall.am Generating ./cpukit/ftpd/preinstall.am Generating ./cpukit/mghttpd/preinstall.am Generating ./cpukit/score/preinstall.am Generating ./cpukit/score/cpu/no_cpu/preinstall.am Generating ./cpukit/score/cpu/arm/preinstall.am Generating ./cpukit/score/cpu/lm32/preinstall.am Generating ./cpukit/score/cpu/nios2/preinstall.am Generating ./cpukit/score/cpu/epiphany/preinstall.am Generating ./cpukit/score/cpu/sparc64/preinstall.am Generating ./cpukit/score/cpu/m32c/preinstall.am Generating ./cpukit/score/cpu/i386/preinstall.am Generating ./cpukit/score/cpu/mips/preinstall.am Generating ./cpukit/score/cpu/v850/preinstall.am Generating ./cpukit/score/cpu/or1k/preinstall.am Generating ./cpukit/score/cpu/bfin/preinstall.am Generating ./cpukit/score/cpu/sh/preinstall.am Generating ./cpukit/score/cpu/m68k/preinstall.am Generating ./cpukit/score/cpu/powerpc/preinstall.am Generating ./cpukit/score/cpu/moxie/preinstall.am Generating ./cpukit/score/cpu/sparc/preinstall.am Generating ./cpukit/libcrypt/preinstall.am Generating ./cpukit/dev/preinstall.am Generating ./cpukit/libpci/preinstall.am Generating ./cpukit/wrapup/preinstall.am Generating ./cpukit/sapi/preinstall.am Generating ./cpukit/libdl/preinstall.am Generating ./cpukit/libcsupport/preinstall.am Generating ./cpukit/pppd/preinstall.am Generating ./cpukit/dtc/libfdt/preinstall.am Generating ./cpukit/libnetworking/preinstall.am Generating ./cpukit/libfs/preinstall.am Generating ./cpukit/libfs/src/nfsclient/preinstall.am Generating ./cpukit/zlib/preinstall.am Generating ./cpukit/posix/preinstall.am Generating ./cpukit/librpc/preinstall.am Generating ./cpukit/telnetd/preinstall.am Generating ./cpukit/libdebugger/preinstall.am Generating ./cpukit/rtems/preinstall.am Generating ./cpukit/libmd/preinstall.am Generating ./c/src/wrapup/preinstall.am Generating ./c/src/libchip/preinstall.am Generating ./c/src/lib/libbsp/no_c