-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FUTURE_SEQUANA: failing to pass block device tests. #9620
Comments
FYI @lrusinowicz |
Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-838 |
Which one is that?
How does SD component use this signal? Does it try to configure it as hardware-controlled part of SPI object? This won't work at the moment; current HAL implementation supports only a single SS signal per interface and that's P9_3, available only on microBUS connector. |
The SD driver control the CS as a GPIO and do not pass it to the SPI driver. The ci-test-shield is : https://github.com/ARMmbed/mbed-HDK-Eagle-Projects You may have to pay attention to the voltages supported by the host board and the µsd adapter. |
1. Removed random i/o glitches occurring during device reconfiguration 2. Fixed hazardous reads occurring at the end of transfer resulting in incorrect values being received 3. Added spi_free() function 4. Replaced default M0 image with a one ignoring i/o reservation. This is a workaround for missing proper destructors in Mbed drivers and BlockDevice tests failing on repeated initialization Fixes issue ARMmbed#9620.
1. Removed random i/o glitches occurring during device reconfiguration 2. Fixed hazardous reads occurring at the end of transfer resulting in incorrect values being received 3. Added spi_free() function 4. Replaced default M0 image with a one ignoring i/o reservation. This is a workaround for missing proper destructors in Mbed drivers and BlockDevice tests failing on repeated initialization Fixes issue #9620.
1. Removed random i/o glitches occurring during device reconfiguration 2. Fixed hazardous reads occurring at the end of transfer resulting in incorrect values being received 3. Added spi_free() function 4. Replaced default M0 image with a one ignoring i/o reservation. This is a workaround for missing proper destructors in Mbed drivers and BlockDevice tests failing on repeated initialization Fixes issue ARMmbed#9620.
Description
mbed test -t GCC_ARM -m FUTURE_SEQUANA -n mbed-os-features-storage-tests-blockdevice-general_block_device -v
fails withUsing mbed's cishield and this configuration :
Issue request type
The text was updated successfully, but these errors were encountered: