2017-03-02 06:02 AM
I do have the same issue
https://community.st.com/0D50X00009XkgMqSAJ
with the code generated for the stm32F2 device.Additionally some values are not correct, below is the value we should have (based on the demo for the nucleo 207 board).
/* Section 4: Extended PHY Registers */
&sharpdefine PHY_SR ((uint16_t)0x1FU) /*!< PHY status register Offset */&sharpdefine PHY_SPEED_STATUS ((uint16_t)0x0004U) /*!< PHY Speed mask */
&sharpdefine PHY_DUPLEX_STATUS ((uint16_t)0x0010U) /*!< PHY Duplex mask */&sharpdefine PHY_ISFR ((uint16_t)0x001DU) /*!< PHY Interrupt Source Flag register Offset */
&sharpdefine PHY_ISFR_INT4 ((uint16_t)0x0010U) /*!< PHY Link down interrupt */null2017-03-06 07:24 AM
Hi
Castrignano.Adalgiso
,Could you please precise in which MX version you have found the issue. So, we can verify it.
-Nesrine-
2017-03-06 07:27 AM
Hi,
In cube 4.19 and library for F2 version 1.4
2017-03-06 08:38 AM
Hi
Castrignano.Adalgiso
,I forward this issue to our MX team for checking.
Sorry for the inconvenience it may bring.
-Nesrine-
2017-03-13 03:41 AM
I've been trying for the last few days to get some STM32F7discovery examples to work.
Looks like this is probably the problem.
Has this problem been rectified? Is there any info on the solution/fix?
i.e. correct register/mask values to substitute into the library?
2017-03-13 05:13 AM
Actually... looking at it now, the addresses appear to be correct. Looks like I had the wrong datasheet for the PHY?! So confusing.