Hello!
>1. In the normal (non-debugging) case, the linker script still places
>the
>
> .text section near zero, but places the start of the .data and .bss
> sections at the start location of the MPC555's internal RAM. The system
> startup code then configures the external RAM just after t
On 04/06/2019 12:34, JunBeom Kim wrote:
Dear Sir,
I am using RTEMS FAT32 File System for both SD-Card and eMMC until now.
Because FAT32 file system doesn’t have Journaling feature, FAT32 is
not Power-Safe file system.
If there is any Power-Safe File system S/W solution(Commercial or
Open-s
On 04/06/2019 12:18, JunBeom Kim wrote:
Dear Sir,
I need O_DIRECT option for calling open() function for handling file I/O.
As I check from posix-users.pdf document, there is not O_DIRECT option
for calling open() function.
There is supporting options from RTEMS POSIX document in below;
-O
Dear Sir,
I am using RTEMS FAT32 File System for both SD-Card and eMMC until now.
Because FAT32 file system doesn't have Journaling feature, FAT32 is not
Power-Safe file system.
If there is any Power-Safe File system S/W solution(Commercial or
Open-source) for RTEMS, please let me know tha
Dear Sir,
I need O_DIRECT option for calling open() function for handling file I/O.
As I check from posix-users.pdf document, there is not O_DIRECT option for
calling open() function.
There is supporting options from RTEMS POSIX document in below;
- O_RDONLY, O_WRONLY, O_RDWR
-
