Hi,
the same applies for RMII phy KSZ8031.
STM32_MAC_ETH1_CHANGE_PHY_STATE has to be disabled for this phy.
Bye, RuWe
Search found 104 matches
- Tue Nov 26, 2013 11:54 am
- Forum: STM32 Support
- Topic: Stm32f4discovery and Embest Base Board
- Replies: 3
- Views: 2915
- Sun Nov 24, 2013 4:29 pm
- Forum: STM32 Support
- Topic: Ethernet PHY hardware interrupt
- Replies: 10
- Views: 6994
Re: Ethernet PHY hardware interrupt
The KSZ8031 has a strapping option for enabling auto negotiation. The state of a pin is samples when reset pin is released. According to the data sheet, this pin has an internal pullup, leading to a activation of auto negotiation by default. When I read the control register I can see that in some po...
- Sat Nov 23, 2013 11:17 pm
- Forum: STM32 Support
- Topic: Ethernet PHY hardware interrupt
- Replies: 10
- Views: 6994
Re: Ethernet PHY hardware interrupt
Sorry, wrong trigger setup. The response is always on the MAC TX pins, also in the faulty power-up cycle.
The measurement of the physical packet length on the pins shows me that - in the fault case - the MAC uses 10mbps mode instead of 100mbps.
Have to check PHY registers for configuration.
The measurement of the physical packet length on the pins shows me that - in the fault case - the MAC uses 10mbps mode instead of 100mbps.
Have to check PHY registers for configuration.
- Sat Nov 23, 2013 7:13 pm
- Forum: STM32 Support
- Topic: Ethernet PHY hardware interrupt
- Replies: 10
- Views: 6994
Re: Ethernet PHY hardware interrupt
Yes this is what I already tried: 100mbit switch 1000mbit switch point-to-point crossover cable No impact. Since this is a realtime problem, I added some debugcode in the STM32 firmware. I also changed the Windows test software to send packets using overlapped I/O which is the fastest and most effic...
- Fri Nov 22, 2013 6:04 pm
- Forum: STM32 Support
- Topic: Ethernet PHY hardware interrupt
- Replies: 10
- Views: 6994
Re: Ethernet PHY hardware interrupt
Yes you're right. The KSZ8031 internally doubles the 25MHz clock input in order to operate in RMII mode. The 50MHz clock is provided on an output pin and routed to STM32 MAC input.
- Fri Nov 22, 2013 3:57 pm
- Forum: STM32 Support
- Topic: Ethernet PHY hardware interrupt
- Replies: 10
- Views: 6994
Re: Ethernet PHY hardware interrupt
hmmm..
In some test cycles I never loose pings, no matter how often I try.
After re-powering my board, I permanently loose pings (up to 70%).
So in some power-up cycles, everything works perfectly, in other-up power cycles, the problem is permanently present.
In some test cycles I never loose pings, no matter how often I try.
After re-powering my board, I permanently loose pings (up to 70%).
So in some power-up cycles, everything works perfectly, in other-up power cycles, the problem is permanently present.
- Fri Nov 22, 2013 3:50 pm
- Forum: STM32 Support
- Topic: Ethernet PHY hardware interrupt
- Replies: 10
- Views: 6994
Re: Ethernet PHY hardware interrupt
Is the PHY clock good enough? Not sure. The F407 is clocked with a 25MHz oscillator, which is output at MCO1. This is the clock input for the KSZ8031, which internally doubles the frequency, and this 50Mhz clock is looped back to the STM32 MAC clock input. I heard there're problems when clocking an...
- Fri Nov 22, 2013 3:24 pm
- Forum: STM32 Support
- Topic: Ethernet PHY hardware interrupt
- Replies: 10
- Views: 6994
Ethernet PHY hardware interrupt
Hello, I ported Olimex P407 LWIP demo to my own board which uses a KSZ8031 phy. The problem is, at high ping rates (1ms interval with maximum packet size) I sometimes get dropped packages (in the range 0...70% lost packages). On my board, I did not connect the KSZ8031 interrupt pin to the F407. I co...
- Tue Oct 22, 2013 11:53 pm
- Forum: General Support
- Topic: USB-CDC raw communication
- Replies: 3
- Views: 2660
Re: USB-CDC raw communication
Ok, thanks... The readme.txt of ARMCM4-STM32F407-DISCOVERY-G++ demo says that it provides an USB-CDC, but in fact it doesn't. Maybe this comment should be removed. However, now I'm using the ARMCM4-STM32F407-DISCOVERY-MEMS demo and removed the shell stuff. Inside the main loop, this works fine: chTh...
- Mon Oct 21, 2013 5:23 pm
- Forum: General Support
- Topic: USB-CDC raw communication
- Replies: 3
- Views: 2660
USB-CDC raw communication
Hello, I would like to use the USB-CDC on an STM32F4 to do some data transmission. Most demos use a test suite or shell with chprintf to show if it works. The demonstrator shell works fine. But I'd like to do some raw read/write access, first of all a simple echo application, returning all data whic...