This software accompanies the application note primarily introduces how to implement MDIOI slave interface functionality using SmartDMA.
- MCUXpresso IDE V11.10.0 or later.
- SDK_2_16_000_FRDM-MCXN947
- MCUXpresso for Visual Studio Code: This example supports MCUXpresso for Visual Studio Code, for more information about how to use Visual Studio Code please refer here.
- Type-C USB cable
- two sets of FRDM-MCXN947
- Personal Computer
- Logic device: Saleae logic pro16
- Some Dupont wires
This application requires two FRDM-MCXN947 boards to implement MDIO communication, with one acting as the MDIO master and the other as the MDIO slave. The two boards are connected through two pins and ground. The hardware connections are shown in the table below.
Function | MDIO Master FRDM-MCXN947 Board | MDIO Slave FRDM-MCXN947 Board |
---|---|---|
MDIO | J1-7(P1-21) | J1-1(P3_16) |
MDC | Pad 1 of R191(remove R191) (P1_20) | J1-5(P3_20) |
GND | J5-8(GND) | J5-8(GND) |
-
Connect logic device to PC with USB cable, connect the logical device to the MDIO signal.
-
Connect FRDM-MCXN947 boards to PC with USB type-C cable.
-
Connect the signal pins of the two FRDM-MCXN947 boards.
- Prepare the master board firmware
It is worth mentioning that the MCXN947's Ethernet peripheral has MDIO master functionality. Users can demonstrate the MDIO master function through the example named “txrx_rxpoll” in the corresponding SDK. The example path is SDK_2_16_000_FRDM-MCXN947\boards\frdmmcxn947\driver_examples\enet\txrx_rxpoll.
The important code routines are as follows:
```
**static** **void** **MDIO_Init**(**void**)
{
(**void**)CLOCK_EnableClock(s_enetClock[ENET_GetInstance(EXAMPLE_ENET_BASE)]);
EXAMPLE_ENET_BASE->MAC_MDIO_ADDRESS = ENET_MAC_MDIO_ADDRESS_CR(0);
}
**static** status_t **MDIO_Write**(uint8_t phyAddr, uint8_t devAddr,uint16_t regAddra, uint16_t data)
{
uint32_t reg = EXAMPLE_ENET_BASE->MAC_MDIO_ADDRESS & ENET_MAC_MDIO_ADDRESS_CR_MASK;
/* Build MII write command. */
EXAMPLE_ENET_BASE->MAC_MDIO_ADDRESS =
reg | ENET_MAC_MDIO_ADDRESS_GOC_0(1) | ENET_MAC_MDIO_ADDRESS_PA(phyAddr) | ENET_MAC_MDIO_ADDRESS_RDA(devAddr)| ENET_MAC_MDIO_ADDRESS_C45E(1);
EXAMPLE_ENET_BASE->MAC_MDIO_DATA = (regAddra << 16) | data;
EXAMPLE_ENET_BASE->MAC_MDIO_ADDRESS |= ENET_MAC_MDIO_ADDRESS_GB_MASK;
**while** (((EXAMPLE_ENET_BASE->MAC_MDIO_ADDRESS & ENET_MAC_MDIO_ADDRESS_GB_MASK) != 0U))
{
}
}
**static** status_t **MDIO_Read**(uint8_t phyAddr, uint8_t devAddr, uint16_t regAddr, uint16_t *pData)
{
uint32_t reg = EXAMPLE_ENET_BASE->MAC_MDIO_ADDRESS & ENET_MAC_MDIO_ADDRESS_CR_MASK;
/* Build MII read command. */
EXAMPLE_ENET_BASE->MAC_MDIO_ADDRESS = reg | ENET_MAC_MDIO_ADDRESS_GOC_0(1) | ENET_MAC_MDIO_ADDRESS_GOC_1(1) |ENET_MAC_MDIO_ADDRESS_PA(phyAddr) | ENET_MAC_MDIO_ADDRESS_RDA(devAddr)| ENET_MAC_MDIO_ADDRESS_C45E(1);
EXAMPLE_ENET_BASE->MAC_MDIO_DATA = (regAddr << 16);
EXAMPLE_ENET_BASE->MAC_MDIO_ADDRESS |= ENET_MAC_MDIO_ADDRESS_GB_MASK;
**while** (((EXAMPLE_ENET_BASE->MAC_MDIO_ADDRESS & ENET_MAC_MDIO_ADDRESS_GB_MASK) != 0U))
{
}
*pData = (EXAMPLE_ENET_BASE->MAC_MDIO_DATA & ENET_MAC_MDIO_DATA_GD_MASK);
}
The operations code as below:
MDIO_Init();
**for**(uint32_t i = 0; i < 8*4; i = i+4)
{
MDIO_Write(0x10, 0x20, 0x8000+i, i);
SDK_DelayAtLeastUs(10, SystemCoreClock);
}
**for**(uint32_t i = 0; i < 8*4; i = i+4)
{
MDIO_Write(0x10, 0x20, 0x9000+i, i+0x100);
SDK_DelayAtLeastUs(10, SystemCoreClock);
}
**for**(uint32_t i = 0; i < 8*4; i = i+4)
{
MDIO_Write(0x10, 0x20, 0xa000+i, i+0x200);
SDK_DelayAtLeastUs(10, SystemCoreClock);
}
**for**(uint32_t i = 0; i < 8*4; i = i+4)
{
MDIO_Write(0x10, 0x20, 0xb000+i, i+0x300);
SDK_DelayAtLeastUs(10, SystemCoreClock);
}
**for**(uint32_t i = 0; i < 8*4; i = i+4)
{
MDIO_Read(0x10, 0x20, 0x8000+i, &g_rec_data);
PRINTF("addr:0x%4x,RxD:0x%4x.\r\n",0x8000+i,g_rec_data);
}
**for**(uint32_t i = 0; i < 8*4; i = i+4)
{
MDIO_Read(0x10, 0x20, 0x9000+i, &g_rec_data);
PRINTF("addr:0x%4x,RxD:0x%4x.\r\n",0x9000+i,g_rec_data);
}
**for**(uint32_t i = 0; i < 8*4; i = i+4)
{
MDIO_Read(0x10, 0x20, 0xa000+i, &g_rec_data);
PRINTF("addr:0x%4x,RxD:0x%4x.\r\n",0xa000+i,g_rec_data);
}
**for**(uint32_t i = 0; i < 8*4; i = i+4)
{
MDIO_Read(0x10, 0x20, 0xb000+i, &g_rec_data);
PRINTF("addr:0x%4x,RxD:0x%4x.\r\n",0xb000+i,g_rec_data);
}
- Import the slave project to MCUXpresso IDE.
-
Open MCUXpresso IDE, in the Quick Start Panel, choose Import from Application Code Hub.
-
Enter the demo name in the search bar.
-
Click Copy GitHub link, MCUXpresso IDE will automatically retrieve project attributes, then click Next>.
-
Select main branch and then click Next>, Select the MCUXpresso project, click Finish button to complete import.
- Connect the micro USB cable between the PC host and the USB port (J17) on the board.
- Compile and download the master and slave firmware to the master and slave board respectively.
- Reset and run.
- Open the PC host software connected to the MDIO master board's serial port, then reset the boards.
- Reset the demo boards, first resetting the MDIO slave board, then the MDIO master board.
- You can see the serial log printed by the MDIO master board as follows:
addr:0x8000,RxD:0x 0.
addr:0x8004,RxD:0x 4.
addr:0x8008,RxD:0x 8.
addr:0x800c,RxD:0x c.
addr:0x8010,RxD:0x c.
addr:0x8014,RxD:0x c.
addr:0x8018,RxD:0x c.
addr:0x801c,RxD:0x 1c.
addr:0x9000,RxD:0x 1c.
addr:0x9004,RxD:0x 1c.
addr:0x9008,RxD:0x 108.
addr:0x900c,RxD:0x 10c.
addr:0x9010,RxD:0x 110.
addr:0x9014,RxD:0x 114.
addr:0x9018,RxD:0x 118.
addr:0x901c,RxD:0x 11c.
addr:0xa000,RxD:0x 200.
addr:0xa004,RxD:0x 204.
addr:0xa008,RxD:0x 208.
addr:0xa00c,RxD:0x 20c.
addr:0xa010,RxD:0x 210.
addr:0xa014,RxD:0x 214.
addr:0xa018,RxD:0x 218.
addr:0xa01c,RxD:0x 21c.
addr:0xb000,RxD:0x 300.
addr:0xb004,RxD:0x 304.
addr:0xb008,RxD:0x 308.
addr:0xb00c,RxD:0x 30c.
addr:0xb010,RxD:0x 310.
addr:0xb014,RxD:0x 314.
addr:0xb018,RxD:0x 318.
addr:0xb01c,RxD:0x 31c.
Provide URLs for help here.
Questions regarding the content/correctness of this example can be entered as Issues within this GitHub repository.
Warning: For more general technical questions regarding NXP Microcontrollers and the difference in expected functionality, enter your questions on the NXP Community Forum
Version | Description / Update | Date |
---|---|---|
1.0 | Initial release on Application Code Hub | September 10th 2024 |
If applicable - note software licensing here with links to licenses, otherwise remove this section
if applicable - note components your application uses regarding to license terms - with authors / licenses / links to licenses, otherwise remove this section