View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005117 | fsvybrid_Linux | Ethernet | public | 2021-11-04 15:22 | 2021-11-08 14:02 |
| Reporter | Keller | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | fsvybrid-V2.2.1 | ||||
| Target Version | fsvybrid-next | Fixed in Version | fsvybrid-V2.2.1 | ||
| Summary | 0005117: eth1 does not work on armStoneA5.2 | ||||
| Description | When doing peripheral tests for fsvybrid-V2.1.1 release, eth1 was not working. In U-Boot, the link on the cable is detected (i.e. PHY is running) but transmission fails. In Linux, there is the following message when starting eth1 with ifconfig: eth1: no PHY, assuming direct connection to switch PHY 0:00 not found eth1: could not attach to PHY | ||||
| Steps To Reproduce | With only the LAN cable connected to port eth1 (the one next to the power connector), try a tftp in U-Boot. In Linux, try ifconfig eth1 10.0.0.252 up | ||||
| Additional Information | On PicoCOMA5 and NetDCUA5, eth1 actually does work, so it seems to be a problem that is only related to armStoneA5. On an armStoneA5 with board rev 1.10 and KSZ8081 PHYs, eth1 also works. But this board revision does not yet have the CKO1 to RGMII_CLK connection that was introduced in board rev. 1.11. Unfortunately there was no board rev 1.11 available right now to test the eth1 behavior. | ||||
| Forum Link | |||||
