Hi,
This post is the start of the process to formally define the tiers for RTEMS.
The RTEMS Tiers helps the project and you understand the current tested state of
RTEMS in an open and public manner. It is important we do this and we get valid
results.
Up to this starting I have made a bit of gues
On Oct 21, 2017 7:44 AM, "Hui Yie Teh" wrote:
Hi,
I have the following size for my application:
textdata bss dec hex filename
> 775001544 64032 143076 22ee4 o-optimize/test.exe
I believe .bss and part of the .data is allocated in RAM. However, the
LM3S6965 Qemu bo
> There is no general purpose flash framework in RTEMS (like MTD on Linux). The
> JFFS2 uses therefore a framework independent interface. You have to provide
> functions for the basic flash operations read, program and erase > yourself.
> You should test these operations separately.
>
> The fi
Hi,
I have the following size for my application:
textdata bss dec hex filename
> 775001544 64032 143076 22ee4 o-optimize/test.exe
I believe .bss and part of the .data is allocated in RAM. However, the
LM3S6965 Qemu board only has 64kB of RAM. On top of that, I have
- Am 21. Okt 2017 um 2:17 schrieb xuelin tian xuelin.t...@qkmtech.com:
> I followed the example (testsuites/fstests/jffs2_support/fs_support.c), and
> some
> error came up, like
> "undefined reference to rtems_jffs2_initialize",
> "undefined reference to rtems_jffs2_compressor_zlib_compress",
Hi Joel,
I was wondering if the command TARGET-rtems4.xx-size works for QEMU? I am
getting this as the output for my application:
>
>textdata bss dec hex filename
> 77540 1544 64032 143116 22f0c o-optimize/test.exe
However, I am emulating the
