Re: Marking files as "Hidden / Inaccessible" on filesystem

On 30/3/19 2:22 am, Matthew J Fletcher wrote: > Is there a method of hiding (does not appear in a 'ls -l' directory listing, > or > FTP listing) a file ?,. in addition is there a way of making a file > inaccessible > (cannot cat to screen from console, or ftp by guessing the name) ? > > The appl

[driver] non-volatile flash

Hi, I'm starting development for a non-volatile flash driver (norflash) and would like to know where I should start. I understand I should respect the IO Manager interface (with the driver table: read, open, init, write, etc). I do not understand if there is a standard way to manage block devices.

Re: Trouble building RTEMS LibBSD

- Ursprüngliche Mail - > Von: "Brendan McNally" > An: "RTEMS Users" > Gesendet: Freitag, 29. März 2019 19:40:52 > Betreff: Trouble building RTEMS LibBSD > Hello all - > > I have been following along with the RTEMS LibBSD readme > , and

Re: Sqlite building failure using rtems-source-builder

On Fri, Mar 29, 2019 at 12:57 AM JunBeom Kim wrote: > Because there is file locking problem due to fcntl(F_SETLK) unsupported > feature, DB file access is error. SQLite3 ships with a set of VFS methods that avoid file locking entirely, named "unix-none". There are several methods available to

Trouble building RTEMS LibBSD

Hello all - I have been following along with the RTEMS LibBSD readme , and I have encountered an issue building the rtems-libbsd module with waf. Note: I'm building on a FreeBSD-11.2 dev machine. I have successfully built and installed the tools

Marking files as "Hidden / Inaccessible" on filesystem

Hi, Is there a method of hiding (does not appear in a 'ls -l' directory listing, or FTP listing) a file ?,. in addition is there a way of making a file inaccessible (cannot cat to screen from console, or ftp by guessing the name) ? The application of course would still need access via the C api.

fcntl(.., F_SETLK, ..) replacement possible ?

Dear Sir, As I know from fcntl.c of cpukit part, fcntl() did not support F_GETLK, F_SETLK, F_SETLKW, F_SETOWN, F_GETOWN. When I test sqlite3 code on RTEMS, there is file locking problem due to non-implementation of F_SETLK option. I guess that because RTEMS is not process OS model with

Re: RTEMS scheduler bug ?

On 29/03/2019 14:31, Catalin Demergian wrote: Sure, I will build and try. Is _ISR_Get_level() something CPU-specific ? I mean we use it to figure out if interrupts are enabled or not, right ? forgot to say, I use a STM32H7. Does _ISR_Get_level work on it ? I would run test testsuites/sptests

Re: RTEMS scheduler bug ?

Sure, I will build and try. Is _ISR_Get_level() something CPU-specific ? I mean we use it to figure out if interrupts are enabled or not, right ? forgot to say, I use a STM32H7. Does _ISR_Get_level work on it ? Also, I thought the scheduler code runs with interrupts enabled, I mean doesn't it use

Re: [altcycv_devkit] Access to FPGA Fabric via HPS2FPGA Bridge

Hello, On 29/03/2019 12:57, Christian Spindeldreier wrote: Hi, currently we experimenting with the RTEMS-5 on a Cylcone V SoC-FPGA using the altcycv_devkit BSP. Now we are trying to access a simple hardware module connected to the HPS2FPGA Bridge via an AXI interconnect. Our approach of simp

[altcycv_devkit] Access to FPGA Fabric via HPS2FPGA Bridge

Hi, currently we experimenting with the RTEMS-5 on a Cylcone V SoC-FPGA using the altcycv_devkit BSP. Now we are trying to access a simple hardware module connected to the HPS2FPGA Bridge via an AXI interconnect. Our approach of simply write data to the corresponding address or using the 'alt

Re: Complete stall: root causes and diagnosis

On 27/03/2019 03:02, Tim Gaggstatter wrote: B) Is there a way we can somehow get out of this situation to diagnose it, ideally getting the stacktrace of the halted threads? Is there some kind of non-maskable interrupt I can send  to make a postmortem diagnosis w/o needing to reboot? I would f

Re: RTEMS scheduler bug ?

Hello Catalin, On 29/03/2019 10:56, Catalin Demergian wrote: Hi, We had some time ago (sept/oct 2018) a long discussion where I was suspecting a scheduler issue (subject "rtems_message_queue_receive/rtems_event_receive issues") We got to the point where I realized that _Chain_Append_unprotec

RTEMS scheduler bug ?

Hi, We had some time ago (sept/oct 2018) a long discussion where I was suspecting a scheduler issue (subject "rtems_message_queue_receive/rtems_event_receive issues") We got to the point where I realized that _Chain_Append_unprotected might fail to add an element in the queue, with the effect of h

stm32 uart read

here is my code: #define CONFIGURE_INIT #include #include #include /* String function definitions */ #include /* UNIX standard function definitions */ #include/* File control definitions */ #include/* Error number definitions */ #include /* POSIX terminal control definitions */

RE: Memory allocation speed is slow by memory fragmentation on long-run test.

Dear Sebastian, There is not any problem using my patch code in my customer side until now. I will consider TLSF. Thank you very much for TLSF information. On referencing, I will investigate libbsd's SD-Card speed improvement for IMX target(your side: i.MX7D, my side: i.MX6Q) soon. If there is

Re: Memory allocation speed is slow by memory fragmentation on long-run test.

On 29/03/2019 08:19, JunBeom Kim wrote: Dear Sir, I am still working with my customer using RTEMS based Qt Framework in long time. My customer are using memory allocation(malloc, realloc, free) with frequency about small size(64, 128, 256, 512, 1024 byte, etc). When RTEMS application i

Memory allocation speed is slow by memory fragmentation on long-run test.

Dear Sir, I am still working with my customer using RTEMS based Qt Framework in long time. My customer are using memory allocation(malloc, realloc, free) with frequency about small size(64, 128, 256, 512, 1024 byte, etc). When RTEMS application is run in long time(for example: 6 hours), ma