ARMmbed / mbed-os-example-filesystem

The Mbed OS file system example
https://mbed.com
Apache License 2.0
16 stars 33 forks source link

Readme needs update #81

Closed jafermarq closed 3 years ago

jafermarq commented 5 years ago

I believe the Readme, in particular, the changing-the-block-device section, needs to be updated after the latest change to main.cpp. Also, shouldn't the SPI numbering be specified in the mbed_app.json. Although I'm able to compile this project, executing the generated binary will result in a hard fault.

dannybenor commented 5 years ago

@jafermarq can you provide more specific info? What target are you using? Did you change anything?

jafermarq commented 5 years ago

I'm using a Nucleo-F767ZI and mbed-cli 1.8.3. I can compile the example in master but when flashing it, it will result in a HardFault when attempting to mount the filesystem. This error seems to trigger a reset so this is happening in a loop over and over. The error code is 0x800259E By switching to override-storage-components branch I can make it work. I'm mostly interested in using a SD card, so I haven't tested other types of BlockDevice interfaces.

dannybenor commented 5 years ago

@jafermarq Did you add support for Nucleo-F767ZI in targets.json? Can you paste here your compilation command?

dannybenor commented 5 years ago

@0xc0170 I did not mean to close this issue.

jafermarq commented 5 years ago

@dannybenor, I haven't edited targets.json. I run the following command: mbed compile -m auto -t GCC_ARM. The compilation is successful but after flashing it, I get the hard fault. My guess is that the problem is in line BlockDevice *bd = BlockDevice::get_default_instance(); in the main.cpp.

RonEld commented 5 years ago

Hi @jafermarq What is set as you component in your target? Did you add

"target_overrides": {
         ...
         "NUCLEO_F767ZI": {
             "target.components_add": ["SD"],
             ...
         },
         ...
  }

to your mbed_app.json ?

linlingao commented 5 years ago

@jafermarq Can you respond to @RonEld? If you've solved your issue, please close.

adbridge commented 5 years ago

Apologies, this was closed in error by the automated bot - re-opening.

ciarmcom commented 4 years ago

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2068

evedon commented 3 years ago

Fixed by #133