Zephyr File System Not Working


Yie
 

Thank you so much! I tried building it on qemu_x86 and it works fine.

However, if you don't mind, I have another question regarding the file system.

This is my code: 
Inline images 2

I'm currently trying to open the file to write to it. It seems to be opening fine, but I cannot call the fs_write/fs_seek don't seem to be working for me.. The only output I am getting is "Done opening file". 

Can I get any help on this? Thanks once again.

Cheers.

On 23 September 2017 at 05:38, Nashif, Anas <anas.nashif@...> wrote:

When you enable the filesystem without actually having storage, FAT is enabled with a RAM disk with 96kb storage, this does not fit in Qemu configuration you are using.

If you are looking at emulation, you probably should try qemu_x86 which has more storage configured, this will build just fine.

 

Anas

 

From: Hui Yie Teh [mailto:hteh703@aucklanduni.ac.nz]
Sent: Friday, September 22, 2017 11:59 AM
To: Nashif, Anas <anas.nashif@...>
Cc: zephyr-devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] Zephyr File System Not Working

 

Thanks for your reply. 

 

I am not linking any external code in. I'm building a simple app that prints "hello" to the console.

 

This is what I have in my config file:

 

CONFIG_STDOUT_CONSOLE=y
CONFIG_FILE_SYSTEM=y

 

Cheers.

 

On 23 September 2017 at 03:52, Nashif, Anas <anas.nashif@...> wrote:

Hi,

 

You are running out of memory, this is not related to the file system.

What exactly are you building? Are you linking external code in?

 

Anas

 

 

From: zephyr-devel-bounces@lists.zephyrproject.org [mailto:zephyr-devel-bounces@lists.zephyrproject.org] On Behalf Of Hui Yie Teh
Sent: Friday, September 22, 2017 11:43 AM
To: zephyr-devel@lists.zephyrproject.org
Subject: [Zephyr-devel] Zephyr File System Not Working

 

Hi,

I'm having problems with Zephyr's file system. I am building on the board qemu_cortex_m3 on Linux. I'm getting the following error when I'm building:

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: zephyr_prebuilt.elf section `bss' will not fit in region `SRAM'

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: section .intList VMA [0000000020010000,0000000020010013] overlaps section bss VMA [0000000020000000,0000000020018437]

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: region `SRAM' overflowed by 37308 bytes

 

collect2: error: ld returned 1 exit status

 

 

Any help would be much appreciated. Thank you.

 



Nashif, Anas
 

When you enable the filesystem without actually having storage, FAT is enabled with a RAM disk with 96kb storage, this does not fit in Qemu configuration you are using.

If you are looking at emulation, you probably should try qemu_x86 which has more storage configured, this will build just fine.

 

Anas

 

From: Hui Yie Teh [mailto:hteh703@...]
Sent: Friday, September 22, 2017 11:59 AM
To: Nashif, Anas <anas.nashif@...>
Cc: zephyr-devel@...
Subject: Re: [Zephyr-devel] Zephyr File System Not Working

 

Thanks for your reply. 

 

I am not linking any external code in. I'm building a simple app that prints "hello" to the console.

 

This is what I have in my config file:

 

CONFIG_STDOUT_CONSOLE=y
CONFIG_FILE_SYSTEM=y

 

Cheers.

 

On 23 September 2017 at 03:52, Nashif, Anas <anas.nashif@...> wrote:

Hi,

 

You are running out of memory, this is not related to the file system.

What exactly are you building? Are you linking external code in?

 

Anas

 

 

From: zephyr-devel-bounces@... [mailto:zephyr-devel-bounces@...] On Behalf Of Hui Yie Teh
Sent: Friday, September 22, 2017 11:43 AM
To: zephyr-devel@...
Subject: [Zephyr-devel] Zephyr File System Not Working

 

Hi,

I'm having problems with Zephyr's file system. I am building on the board qemu_cortex_m3 on Linux. I'm getting the following error when I'm building:

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: zephyr_prebuilt.elf section `bss' will not fit in region `SRAM'

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: section .intList VMA [0000000020010000,0000000020010013] overlaps section bss VMA [0000000020000000,0000000020018437]

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: region `SRAM' overflowed by 37308 bytes

 

collect2: error: ld returned 1 exit status

 

 

Any help would be much appreciated. Thank you.

 


Yie
 

Thanks for your reply. 

I am not linking any external code in. I'm building a simple app that prints "hello" to the console.

This is what I have in my config file:

CONFIG_STDOUT_CONSOLE=y
CONFIG_FILE_SYSTEM=y

Cheers.

On 23 September 2017 at 03:52, Nashif, Anas <anas.nashif@...> wrote:

Hi,

 

You are running out of memory, this is not related to the file system.

What exactly are you building? Are you linking external code in?

 

Anas

 

 

From: zephyr-devel-bounces@lists.zephyrproject.org [mailto:zephyr-devel-bounces@lists.zephyrproject.org] On Behalf Of Hui Yie Teh
Sent: Friday, September 22, 2017 11:43 AM
To: zephyr-devel@lists.zephyrproject.org
Subject: [Zephyr-devel] Zephyr File System Not Working

 

Hi,

I'm having problems with Zephyr's file system. I am building on the board qemu_cortex_m3 on Linux. I'm getting the following error when I'm building:

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: zephyr_prebuilt.elf section `bss' will not fit in region `SRAM'

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: section .intList VMA [0000000020010000,0000000020010013] overlaps section bss VMA [0000000020000000,0000000020018437]

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: region `SRAM' overflowed by 37308 bytes

 

collect2: error: ld returned 1 exit status

 

 

Any help would be much appreciated. Thank you.



Nashif, Anas
 

Hi,

 

You are running out of memory, this is not related to the file system.

What exactly are you building? Are you linking external code in?

 

Anas

 

 

From: zephyr-devel-bounces@... [mailto:zephyr-devel-bounces@...] On Behalf Of Hui Yie Teh
Sent: Friday, September 22, 2017 11:43 AM
To: zephyr-devel@...
Subject: [Zephyr-devel] Zephyr File System Not Working

 

Hi,

I'm having problems with Zephyr's file system. I am building on the board qemu_cortex_m3 on Linux. I'm getting the following error when I'm building:

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: zephyr_prebuilt.elf section `bss' will not fit in region `SRAM'

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: section .intList VMA [0000000020010000,0000000020010013] overlaps section bss VMA [0000000020000000,0000000020018437]

 

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: region `SRAM' overflowed by 37308 bytes

 

collect2: error: ld returned 1 exit status

 

 

Any help would be much appreciated. Thank you.


Yie
 

Hi,

I'm having problems with Zephyr's file system. I am building on the board qemu_cortex_m3 on Linux. I'm getting the following error when I'm building:

/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: zephyr_prebuilt.elf section `bss' will not fit in region `SRAM'
 
/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: section .intList VMA [0000000020010000,0000000020010013] overlaps section bss VMA [0000000020000000,0000000020018437]
 
/home/user/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/real-ld: region `SRAM' overflowed by 37308 bytes
 
collect2: error: ld returned 1 exit status


Any help would be much appreciated. Thank you.