On 5/6/18 9:03 pm, LINDOW, Phil wrote:
>> Why do you want to use a FAT file system on a flash instead of JFFS2?
>> With the functions you have, you have all what you need to use JFFS2.
>
> Because the file system should be compatible with RTEMS, VxWorks and in the
> best case PikeOS.
> I know th
On 2/6/18 5:29 am, Slide wrote:
>
> Is there any additional information in the logs for the git command failure?
>
> Build: error: git command failed (/usr/bin/git): 1
>
Please raise a ticket to see if more detail can be provided on error.
I think the --trace option has the ability to provide m
On 31/5/18 7:32 am, Slide wrote:
>
> That's something I would like to know as well. When something fails after
> building GCC, it would be nice to not have to rebuild GCC the next time. I
> don't
> know enough about the RTEMS build process at this point to be able to help you
> on that part.
>
On 05/06/18 13:03, LINDOW, Phil wrote:
Why do you want to use a FAT file system on a flash instead of JFFS2?
With the functions you have, you have all what you need to use JFFS2.
Because the file system should be compatible with RTEMS, VxWorks and in the
best case PikeOS.
I know that FAT is not
> Why do you want to use a FAT file system on a flash instead of JFFS2?
> With the functions you have, you have all what you need to use JFFS2.
Because the file system should be compatible with RTEMS, VxWorks and in the
best case PikeOS.
I know that FAT is not the best choice for flash but I am
