Re: MIDAS rtems Port

2018-07-24 Thread Lee Pool
Hi, Konstantin, I've noted your request... Should be easy to get going, if I can find little bit of time this week. On 21/07/2018 02:51, Konstantin Olchanski wrote: Hi, there - on my side, I got MIDAS to (partially) run on ucLinux (mmu-less embedded ARM CPU), and I think it would be good to

Changing the default block size of FAT on RAM-disk

2018-07-24 Thread Udit agarwal
Hi all, I need to change the default block size of FAT to, say 1024. By default, the block size of FAT(on a ramdisk) is 512 as stated here: https://devel.rtems.org/wiki/TBR/UserManual/Using_the_RTEMS_DOS_File_System#RAMDisk and that's what 'blkstats /dev/rda' showed. I couldn't find any relevant p

Re: IMFS on ram-disk

2018-07-24 Thread Joel Sherrill
On Tue, Jul 24, 2018 at 11:34 AM, Gedare Bloom wrote: > On Tue, Jul 24, 2018 at 10:46 AM, Joel Sherrill wrote: > > > > > > On Tue, Jul 24, 2018 at 9:24 AM, Udit agarwal > wrote: > >> > >> > >> > >> On Jul 24, 2018 7:45 PM, "Gedare Bloom" wrote: > >> > >> On Tue, Jul 24, 2018 at 10:12 AM, Gedar

Re: IMFS on ram-disk

2018-07-24 Thread Gedare Bloom
On Tue, Jul 24, 2018 at 10:46 AM, Joel Sherrill wrote: > > > On Tue, Jul 24, 2018 at 9:24 AM, Udit agarwal wrote: >> >> >> >> On Jul 24, 2018 7:45 PM, "Gedare Bloom" wrote: >> >> On Tue, Jul 24, 2018 at 10:12 AM, Gedare Bloom wrote: >> > On Tue, Jul 24, 2018 at 4:48 AM, Udit agarwal >> > wrote

Re: IMFS on ram-disk

2018-07-24 Thread Joel Sherrill
On Tue, Jul 24, 2018 at 9:24 AM, Udit agarwal wrote: > > > On Jul 24, 2018 7:45 PM, "Gedare Bloom" wrote: > > On Tue, Jul 24, 2018 at 10:12 AM, Gedare Bloom wrote: > > On Tue, Jul 24, 2018 at 4:48 AM, Udit agarwal > wrote: > >> Hi all, > >> I've been trying to use IMFS with a ramdisk on BBB. H

Re: IMFS on ram-disk

2018-07-24 Thread Udit agarwal
On Jul 24, 2018 7:45 PM, "Gedare Bloom" wrote: On Tue, Jul 24, 2018 at 10:12 AM, Gedare Bloom wrote: > On Tue, Jul 24, 2018 at 4:48 AM, Udit agarwal wrote: >> Hi all, >> I've been trying to use IMFS with a ramdisk on BBB. Here's what i did: >> >> After creating a ram disk (block size:512, block

Re: IMFS on ram-disk

2018-07-24 Thread Gedare Bloom
On Tue, Jul 24, 2018 at 10:12 AM, Gedare Bloom wrote: > On Tue, Jul 24, 2018 at 4:48 AM, Udit agarwal wrote: >> Hi all, >> I've been trying to use IMFS with a ramdisk on BBB. Here's what i did: >> >> After creating a ram disk (block size:512, block count:262144), i used >> mount_and_make_target_p

Re: IMFS on ram-disk

2018-07-24 Thread Gedare Bloom
On Tue, Jul 24, 2018 at 4:48 AM, Udit agarwal wrote: > Hi all, > I've been trying to use IMFS with a ramdisk on BBB. Here's what i did: > > After creating a ram disk (block size:512, block count:262144), i used > mount_and_make_target_path("/dev/rda","/mnt",RTEMS_FILESYSTEM_TYPE_IMFS,RTEMS_FILESYS

Re: IMFS on ram-disk

2018-07-24 Thread Sebastian Huber
You cannot use the IMFS on a RAM disk. The IMFS always allocates its memory via the standard heap allocator. See: https://docs.rtems.org/branches/master/c-user/configuring_a_system.html#configure-imfs-memfile-bytes-per-block -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-

Re: IMFS on ram-disk

2018-07-24 Thread Ian Caddy
Hi Udit, While I am not familiar with your exact setup, we had issues with larger files on the IMFS using RTEMS4.10. We discovered that there is a default max size of an IMFS file which is around 4.3MBytes. It can be changed by changing the bytes per block in the CONFDEFS: /* IMFS file sys

IMFS on ram-disk

2018-07-24 Thread Udit agarwal
Hi all, I've been trying to use IMFS with a ramdisk on BBB. Here's what i did: After creating a ram disk (block size:512, block count:262144), i used mount_and_make_target_path("/dev/rda","/mnt",RTEMS_FILESYSTEM_TYPE_IMFS,RTEMS_FILESYSTEM_READ_WRITE,NULL) There is no error during bootup, but when

RTEMS 5 tool chain update

2018-07-24 Thread Sebastian Huber
Hello, I updated the tool chain (RSB) to use the latest Newlib snapshot (3.0.0.20180720) and Binutils 2.31.1. An immediate update from the previous tools based on Newlib 3.0.0 is not necessary. I merged the RISC-V tool targets riscv32-rtems5 and riscv64-rtems5 into a common riscv-rtems5 targ