Closed Mircerson closed 2 years ago
@Mircerson thank you for raising this issue.Please take a look at the following comments:
What target(s) are you using? What Mbed OS version are you using? It would help if you could also specify the versions of any tools you are using? How can we reproduce your issue?
NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered. Please update the issue header with the missing information.
Target currently used is a Nucleo-L073RZ and a custom board built around the STM32L073. The bug is present on both boards. The mbed version is 6.15.1. Using mbed studio ( latest ) and GCC. See above to reproduce.
cc @ARMmbed/team-st-mcd
Checking i2c_device.c, there is no I2C_2.
Good catch :-( I am correcting it asap.
@Mircerson please check #15268
Cheers, I'll give it a go tonight
@jeromecoutant thanks for the fix, all working as intended now 👍
Description of defect
I2C2 instance not found on the Nucleo-L073RZ and STM32L073RZTx MCUs This is similar to #15257
++ MbedOS Error Info ++ Error Status: 0x80FF0100 Code: 256 Module: 255 Error Message: Fatal Run-time error Location: 0x800752D Error Value: 0x0 Current Thread: main Id: 0x200015A8 Entry: 0x8002311 StackSize: 0x1000 StackMem: 0x20001838 SP: 0x200025E4 For more info, visit: https://mbed.com/s/error?error=0x80FF0100&tgt=NUCLEO_L073RZ -- MbedOS Error Info -- I2C: unknown instance
Target(s) affected by this defect ?
STM32L073RZTx Nucleo-L073Rz
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM
What version of Mbed-os are you using (tag or sha) ?
Mbed os 6.15.1
How is this defect reproduced ?
Using PB_11 - I2C2 SDA and PB_10 - I2C2 SCL in an I2C instance. Checking i2c_device.c, there is no I2C_2.