template: riscv/qemu-sifive-u qemu: 4.1.0 gcc:

$ riscv64-unknown-elf-gcc --version
riscv64-unknown-elf-gcc (SiFive GCC 8.2.0-2019.05.3) 8.2.0

$qemu-system-riscv32 -nographic -machine sifive_u -kernel embox
***
[email protected]:/#version                                                            

.------.          _
|  ____|         | | 
| |____ _ __ ___ | |_    _____  __
|  ____| '_ ` _ \|  _ \ / _ \ \/ /
| |____| | | | | | |_) | (_) >  <  
|______|_| |_| |_|____/ \___/_/\_\

Tue Jan 28 18:30:00 MSK 2020

Compiler: 8.2.0

On host:

$ date
Tue Jan 28 19:24:41 MSK 2020

But version works fine on x86 and arm.

Closes #1791 The recommended frequency of sifive coreclk is 1.0 GHz. include embox.arch.system(core_freq=1000000000) #define HZ 100000 then the clock works correctly

closes #997: Implementing ferror and friends and closes #1746 I have added functionality for detection of EOF and any ERR in the files->flags by creating macros IO_EOF_ (0x0010) and IO_ERR_ (0x0020) and updating files->flags, whenever any file IO function encounters EOF or any kind of error occurs, which is detected by functions feof() and ferror() and cleared by clearerr(). file IO functions where EOF may occur -> fread() file IO functions where ERR is set -> fflush(), fread(), fseek() and fwrite().

Using arm/stm32f4-discovery default configuration, immediately after exec'ing tish and showing the prompt, it show the following error and restarts.

Started shell [tish] on device [diag]
loading start script:
(...)
> ifconfig lo 127.0.0.1 netmask 255.0.0.0 up
> route add 127.0.0.0 netmask 255.0.0.0 lo
> ifconfig eth0 192.168.1.128 netmask 255.255.255.0 hw ether AA:BB:CC:DD:EE:02 up
> route add 192.168.1.0 netmask 255.255.255.0 eth0
embox>

  ______
 |  ____|                                            __          __
 | |___  _ __ ___            ____  ____  ____  _____/ /   _____ / /
 |  ___|| '_ ` _ \          / __ \/ __ \/ __ \/ ___/ /   |_____| |
 | |____| | | | | |_ _ _   / /_/ / /_/ / /_/ (__  )_/    |_____| |
 |______|_| |_| |_(_|_|_)  \____/\____/ .___/____(_)           | |
                                     /_/                        \_\
 ASSERTION FAILED on CPU 0
        at src/kernel/irq.c:163
        in function irq_dispatch

irq_stack_protection() == 0

        (Stack overflow detected on irq dispatch)
Embox kernel start
        unit: initializing embox.arch.arm.fpu.fpv5:
(...)

After bisecting the tree, the bug started at: 84747575fc6d87bbca4e1a1d713a4ca6265c4794 : third-party: Porting new version of linenoise

Obs: There are two different observable behaviors: The one explained previously happens after 84747575fc6d87bbca4e1a1d713a4ca6265c4794, and before 4d092c573d10883c0cef3f8bad7b68d6d3f42414: drivers: Refactor cortexm systick. It changes after 4d092c573d10883c0cef3f8bad7b68d6d3f42414, showing the following instead:

> ifconfig lo 127.0.0.1 netmask 255.0.0.0 up
> route add 127.0.0.0 netmask 255.0.0.0 lo
> ifconfig eth0 192.168.1.128 netmask 255.255.255.0 hw ether AA:BB:CC:DD:EE:02 up
> route add 192.168.1.0 netmask 255.255.255.0 eth0

done
runlevel: init level is 3

apparently, leaving 'gracefully' the shell, however leaving the system without ways of interacting with it anymore.

Just reverting 84747575fc6d serves as a workaround, however 4d092c573d10 probably implies a different bug is occurring.

This adds driver support for ARM Dual-Timer Module (SP804) which is emulated in qemu-vexpress-a9.

This closes #1769.

Signed-off-by: Nishant Malpani [email protected]

• static implementation of atexit() with ATEXIT_MAX=32 registered functions.

I wrote this yesterday so I thought it could be useful after seeing that an issue was opened for it. It's a simple static solution. Expanding it to one that allocates memory would be relatively simple, although I don't know if it would be actually needed. It might solve #1816 .

Add the BSP and template for the ST's Nucleo-l476rg Board. This closes #2034 It builds correctly but I have to test it on the board.

Signed-off-by: Puranjay Mohan [email protected]

Close #1716 Done with several problems.

• Send signal 0 with pthread_kill will return -1
• Send signal to terminated threads behave wierd (Even crashed when the signal is SIGALRM)

Fixes #1699

• This PR improves the available lsblk command in Embox. It mirrors the linux lsblk command adding the -b, --bytes flags to choose the unit of displaying size.

  

I tried multiple ways to round the value of size to the nearest integer but they all failed resulting in the error message posted on the issue page. The current behavior is typecasting the float to uint64_t (flooring).

man du

Implement only for regular files and it's enough to follow flags:

      -B, --block-size=SIZE
              scale  sizes  by  SIZE  before printing them; e.g., '-BM' prints
              sizes in units of 1,048,576 bytes; see SIZE format below

       -b, --bytes
              equivalent to '--apparent-size --block-size=1'

block_dev_test command is a simple testing tool for block devices like hdd, usb, flash, etc. It checks that read/write routines work correct.

We suggest extending the existing functionality with the following options:

• Add parameter which specifies the block number at which the command should start at.
• Add parameter which specifies blocks count to be tested.
• Add option to read/write multiple blocks in a single iteration (currenly, we read/write only single block in one iteration)

Hi, I tried to build the opencv with stm32f746g-discovery template in Ubuntu 20.04 I am using the release version of embox-0.5.6

Its downloading gcc version 6.3 and fails to compile it make confload-project/opencv/stm32f746g-discovery Config complete make -j4

Failed as below checking for the correct version of gmp.h... no configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC 0.8.0+. Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify

then I ran this command to download those sources

embox-0.5.6/build/extbld/third_party/gcc/gcc_build/gcc-6.3.0$ ./contrib/download_prerequisites

and tried to compile gcc manually it fails at

0.5.6/build/extbld/third_party/gcc/gcc_build/gcc-6.3.0/isl/include -o ubsan.o -MT ubsan.o -MMD -MP -MF ./.deps/ubsan.TPo ../.././gcc/ubsan.c ../.././gcc/ubsan.c: In function ‘bool ubsan_use_new_style_p(location_t)’: ../.././gcc/ubsan.c:1474:23: error: ISO C++ forbids comparison between pointer and integer [-fpermissive]

then after correcting this It got failed again at

g++ -fno-PIE -c -DIN_GCC_FRONTEND -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I../.././gcc -I../.././gcc/. -I../.././gcc/../include -I../.././gcc/../libcpp/include -I/home/prabhumk/Downloads/embox-0.5.6/build/extbld/third_party/gcc/gcc_build/gcc-6.3.0/host-x86_64-pc-linux-gnu/gmp -I/home/prabhumk/Downloads/embox-0.5.6/build/extbld/third_party/gcc/gcc_build/gcc-6.3.0/gmp -I/home/prabhumk/Downloads/embox-0.5.6/build/extbld/third_party/gcc/gcc_build/gcc-6.3.0/host-x86_64-pc-linux-gnu/mpfr -I/home/prabhumk/Downloads/embox-0.5.6/build/extbld/third_party/gcc/gcc_build/gcc-6.3.0/mpfr -I/home/prabhumk/Downloads/embox-0.5.6/build/extbld/third_party/gcc/gcc_build/gcc-6.3.0/mpc/src -I../.././gcc/../libdecnumber -I../.././gcc/../libdecnumber/dpd -I../libdecnumber -I../.././gcc/../libbacktrace -I/home/prabhumk/Downloads/embox-0.5.6/build/extbld/third_party/gcc/gcc_build/gcc-6.3.0/host-x86_64-pc-linux-gnu/isl/include -I/home/prabhumk/Downloads/embox-0.5.6/build/extbld/third_party/gcc/gcc_build/gcc-6.3.0/isl/include -o cc1-checksum.o -MT cc1-checksum.o -MMD -MP -MF ./.deps/cc1-checksum.TPo cc1-checksum.c g++: error: cc1-checksum.c: No such file or directory g++: fatal error: no input files compilation terminated.

Is there anyway to skip the gcc compilation and use the inbuilt gcc compiler.

Below the version of gcc and arm-gcc compilers in the system gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.4.0-1ubuntu1~20.04.1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-9-Av3uEd/gcc-9-9.4.0/debian/tmp-nvptx/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)

arm-none-eabi-gcc -v Using built-in specs. COLLECT_GCC=arm-none-eabi-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-none-eabi/9.2.1/lto-wrapper Target: arm-none-eabi Configured with: ../configure --build=x86_64-linux-gnu --prefix=/usr --includedir='/usr/lib/include' --mandir='/usr/lib/share/man' --infodir='/usr/lib/share/info' --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir='/usr/lib/lib/x86_64-linux-gnu' --libexecdir='/usr/lib/lib/x86_64-linux-gnu' --disable-maintainer-mode --disable-dependency-tracking --mandir=/usr/share/man --enable-languages=c,c++,lto --enable-multilib --disable-decimal-float --disable-libffi --disable-libgomp --disable-libmudflap --disable-libquadmath --disable-libssp --disable-libstdcxx-pch --disable-nls --disable-shared --disable-threads --enable-tls --build=x86_64-linux-gnu --target=arm-none-eabi --with-system-zlib --with-gnu-as --with-gnu-ld --with-pkgversion=15:9-2019-q4-0ubuntu1 --without-included-gettext --prefix=/usr/lib --infodir=/usr/share/doc/gcc-arm-none-eabi/info --htmldir=/usr/share/doc/gcc-arm-none-eabi/html --pdfdir=/usr/share/doc/gcc-arm-none-eabi/pdf --bindir=/usr/bin --libexecdir=/usr/lib --libdir=/usr/lib --disable-libstdc++-v3 --host=x86_64-linux-gnu --with-headers=no --without-newlib --with-multilib-list=rmprofile CFLAGS='-g -O2 -fdebug-prefix-map=/build/gcc-arm-none-eabi-Gl9kT9/gcc-arm-none-eabi-9-2019-q4=. -fstack-protector-strong' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' CXXFLAGS='-g -O2 -fdebug-prefix-map=/build/gcc-arm-none-eabi-Gl9kT9/gcc-arm-none-eabi-9-2019-q4=. -fstack-protector-strong' FCFLAGS='-g -O2 -fdebug-prefix-map=/build/gcc-arm-none-eabi-Gl9kT9/gcc-arm-none-eabi-9-2019-q4=. -fstack-protector-strong' FFLAGS='-g -O2 -fdebug-prefix-map=/build/gcc-arm-none-eabi-Gl9kT9/gcc-arm-none-eabi-9-2019-q4=. -fstack-protector-strong' GCJFLAGS='-g -O2 -fdebug-prefix-map=/build/gcc-arm-none-eabi-Gl9kT9/gcc-arm-none-eabi-9-2019-q4=. -fstack-protector-strong' LDFLAGS='-Wl,-Bsymbolic-functions -Wl,-z,relro' OBJCFLAGS='-g -O2 -fdebug-prefix-map=/build/gcc-arm-none-eabi-Gl9kT9/gcc-arm-none-eabi-9-2019-q4=. -fstack-protector-strong' OBJCXXFLAGS='-g -O2 -fdebug-prefix-map=/build/gcc-arm-none-eabi-Gl9kT9/gcc-arm-none-eabi-9-2019-q4=. -fstack-protector-strong' INHIBIT_LIBC_CFLAGS=-DUSE_TM_CLONE_REGISTRY=0 AR_FOR_TARGET=arm-none-eabi-ar AS_FOR_TARGET=arm-none-eabi-as LD_FOR_TARGET=arm-none-eabi-ld NM_FOR_TARGET=arm-none-eabi-nm OBJDUMP_FOR_TARGET=arm-none-eabi-objdump RANLIB_FOR_TARGET=arm-none-eabi-ranlib READELF_FOR_TARGET=arm-none-eabi-readelf STRIP_FOR_TARGET=arm-none-eabi-strip Thread model: single gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599] (15:9-2019-q4-0ubuntu1)

@anton-bondarev

Embox is mentioned in https://en.wikipedia.org/wiki/Comparison_of_real-time_operating_systems but I can't find the Embox article in the English Wikipedia. There is https://ru.wikipedia.org/wiki/Embox but there is no https://en.wikipedia.org/wiki/Embox .