Skip to content
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

NUCLEO_F746ZG Issues #2960

Closed
screamerbg opened this issue Oct 6, 2016 · 7 comments
Closed

NUCLEO_F746ZG Issues #2960

screamerbg opened this issue Oct 6, 2016 · 7 comments

Comments

@screamerbg
Copy link
Contributor

screamerbg commented Oct 6, 2016

Description

  • Type: Bug
  • Priority: Major

Interrupt failures (InterruptIn)

InterruptIn on D2 actually works
InterruptIn on D3 throws greentea error, I suspect that the test crashes
InterruptIn on D4-9 are skipped due to the error with InterruptIn on D3

Analog In failures (AnalogIn)

Analog Input on A0 (fails with ARMCC, works with GCC)
Analog Input on A5 (fails with GCC, works with ARMCC)

I2C failures with EEPROM (I2C)

I2C - EEProm Write - 2bytes (but 1 byte words)
I2C - EEProm Write - 10bytes
I2C - EEProm Write - 100bytes

Target
NUCLEO_F746ZG

Toolchain:
GCC_ARM+ARM

meed-os sha:
22ec73b Merge pull request #2948 from jamike/Fixed_iarm_debug_built_failed

Steps to reproduce
Tests available here https://github.com/armmbed/ci-test-shield
Hardware components here https://github.com/ARMmbed/mbed-HDK/tree/master/Production%20Design%20Projects/CITestShield

CC @adustm @bcostm

@BlackstoneEngineering
Copy link
Contributor

#ci-test-shieldfor the win!

@screamerbg screamerbg changed the title NUCLEO_L746ZG Issues NUCLEO_F746ZG Issues Oct 14, 2016
@screamerbg
Copy link
Contributor Author

Added I2C issues @bcostm @adustm

@screamerbg
Copy link
Contributor Author

Note that ST Discovery F746NG based on the same silicon has issues with AnalogIn A0 only, not A5. A clue that this might be peripheral configuration issue

@adustm
Copy link
Member

adustm commented Nov 21, 2016

Hi,
I just pushed a fix for InterruptIn test.
SYSCFG_EXTICR4, EXTI_IMR, EXTI_RTSR, EXTI_FTSR registers were not in a correct state after the sw destruction of the InterruptIn object.
The next time those HW registers were activated by a new InterruptIn object, the interrupt management was all messed up.

0xc0170 added a commit that referenced this issue Dec 2, 2016
Fix #2956 #2939 #2957 #2959 #2960: Add HAL_DeInit function in gpio_irq destructor
@jeromecoutant
Copy link
Collaborator

Hi @screamerbg

All tests with ci-shield are OK with NUCLEO_746ZG

    "NUCLEO_F746ZG": {
         "AOUT": "D13"
    },

Can you close the issue ?

@bcostm
Copy link
Contributor

bcostm commented May 18, 2017

ST_TO_BE_CLOSED

@LMESTM
Copy link
Contributor

LMESTM commented Jun 30, 2017

@sg- @screamerbg @0xc0170 please close as all the CI tests are now passed on this board

@0xc0170 0xc0170 closed this as completed Jun 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants