CYW43907, filesystem on modustoolbox

[cedric_roomz]

Hi,

I'm trying to add a filesystem using emfile or littlefs on my cyw43907 firmware using mtb.

It seems it's not currently supported. It fails at the first include: for example #include "lfs.h" for littlefs

What's the best way to integrate a filesystem on cyw43907  with modustoolbox?

Thanks,

Cédric

[Qi_Colin]

Hi @cedric_roomz :

You can try to add the "littlefs" component in the library.

Regards 

Colin

[cedric_roomz]

Hi Colin,

Thanks for the pointer, indeed it helped. But it now fails at the inclusion of "cy_smif_memslot.h"

I cannot add "mtb-pdl-cat1" with the library manager. 

How can I add it?

Thanks,

Cédric

[Qi_Colin]

Hi @cedric_roomz :

"mtb-pdl-cat1"  don't support CYW43907(normally it is used for PSoC6 devices), so you can't add it.

May I know about which function call "cy_smif_memslot.h"?

Best Regards 

Colin

[cedric_roomz]

It's included in lfs_spi_flash_bd.h which uses cy_stc_smif_mem_config_t

[Qi_Colin]

Hi @cedric_roomz :

Which project of BSP you're working on? 

I didn't find  "lfs_spi_flash_bd.h" in "littlefs" component...

I need to do some test then give you feedback.

Best Regards 

Colin

[cedric_roomz]

Hi Colin,

lfs_spi_flash_bd.h is in mtb-littlefs\release-v1.0.0\include

It is used in the psoc6 littlefs example 

    /* Get the default configuration for the SPI flash block device. */
    lfs_spi_flash_bd_get_default_config(&spi_flash_bd_cfg);

    /* Initialize the pointers in lfs_cfg to NULL. */
    memset(&lfs_cfg, 0, sizeof(lfs_cfg));

    /* Create the SPI flash block device. */
    result = lfs_spi_flash_bd_create(&lfs_cfg, &spi_flash_bd_cfg);
    check_status("Creating SPI flash block device failed", result);

lfs_spi_flash depends on qspi in mtb-pdl-cat1, which seems complicated to adapt for cyw43907

I searched  for qspi examples for CYW43907 but have not found any.

If you can make a small example project or point me the direction on how to integrate it that would be of much help!

[Qi_Colin]

Hi @cedric_roomz :

mtb-littlefs only supports PSoC 6, not include CYW43907.

Currently I don't find any code example can touch your requirements.

Could you provide the detail requirements of the code example? 

I will try to make a example project to you.

Best Regards 

Colin

[cedric_roomz]

Hi Colin,

The requirements would be:
- Using CYW43907

- using Littlefs (or emfile, I don't have strong preference here)

- Write and read a file on flash

Thanks,

Cédric

[Qi_Colin]

Hi @cedric_roomz ：

I‘ve tried to make a code example to you, but unfortunately failed because the QSPI driver of CYW43907 is still under integration, not supported on ModusToolbox yet.

 If you have any experience of development on WICED, it's better to develop this function on it. If not, maybe we need to wait for the update of HAL in the future.

Best Regards 

Colin

[cedric_roomz]

Hi Colin,

Thanks for trying and for the info.

When shall the QSPI driver be integrated?

You mean develop the filesystem handling in wiced and integrate the built object in ModusToolbox? Is there any example on how to do this?

Thanks,

Cédric

[Qi_Colin]

Hi @cedric_roomz :

I'm not sure the schedule of integration, our AE team are working on it.

If you use WICED to develop,  you should develop whole project in it, not only filesystem function...

Best Regards 

Colin

[cedric_roomz]

Hi Colin,

Thank you for the feedback.

To explain our situation, we have decided to switch our product to the cyw43907 due to chip availability and need to have a working product in the coming months. I have been told on this forum that CYW43907 was supported by modustoolbox and started developing on it. 

Now I'm being told that not all features are actually present. 

There are several options for us:

1: Redevelop everything in wiced

2: Wait for functionnality to be ported on modustoolbox 

Solutions 2 would be my preferred solution as it does not require redeveloping what has been done and we could easily switch to psoc6+cyw43012 in the future. However I need at least a tentative timeline to decide. 

How can we get a rough schedule of integration? Can you put me in touch with the AE team?

[Qi_Colin]

Hi @cedric_roomz :

Thank you for your information, and I will check the integration status then feedback to you ASAP.

Best Regards 

Colin

[cedric_roomz]

Thank you Colin!

[Qi_Colin]

Hi @cedric_roomz :

One more thing check with you.

In your application, you will use the same flash of FW image with the filesystem function, or you will use another flash for the filesystem function.

Best Regards 

Colin

[cedric_roomz]

Hi Colin,

The same flash for everything, we use a 64MBIT MX25L6433. (And we also plan to implement dfu and ota)

Cédric

[Qi_Colin]

Hi @cedric_roomz :

I try to check the schedule of the integration status, but till now no result about this issue.

I suggest you to contact our local sales representative for further support.

No matter you merge the code to WICED or push the integration.

Best Regard,

Colin

[cedric_roomz]

Thanks Colin,

I've been pushing for support with the sales channel as well for some months now.  

Best feedback I received was:

---

"Wiced will not be supported in the future, so updates will not be available.

Every feature will be ported to ModusToolbox but this will take an indefinite amount of time.

Because of this we also do not have the capacity to support you directly for this project."

---

Which makes me start to wonder whether indefinite also means "maybe never"...

Can you direct me in private message to someone who could help me?

Thanks,

Cédric