i.mx6ul evk Board ethernet driver

cancel
Showing results for 
Search instead for 
Did you mean: 

i.mx6ul evk Board ethernet driver

Jump to solution
202 Views
zhangzhaoxa
Contributor I

I find some mismatch betweent hardware and the SDK driver.

In the schematics, the ENET1_nINT is connected to SNVS_TAMPER5. In the SDK2.0 the boards\evkmcimx6ul\driver_examples\enet\txrx_transfer\pin_mux.c, there define "{pin_num: K13, peripheral: ENET1, signal: enet_1588_event0_in, pin_signal: GPIO1_IO00}".

In fact the pin SNVS_TAMPER5 that only can be set to GPIO5_IO05 in the IOMUX, can't be set to  enet_1588_event0_in.

I can't understand how this work , Does anybody know?

0 Kudos
1 Solution
189 Views
igorpadykov
NXP TechSupport
NXP TechSupport

ENET1_nINT is interrupt from KSZ8081 (U1501 SPF-28616 i.MX6UL EVK schematic),

it is connected to processor gpio and can notfy processor about KSZ8081 state.

In linux seems such codes are not implemented.

 

Best regards
igor

View solution in original post

0 Kudos
3 Replies
198 Views
igorpadykov
NXP TechSupport
NXP TechSupport

Hi Joey

 

>In fact the pin SNVS_TAMPER5 that only can be set to GPIO5_IO05 in the IOMUX, can't be set to enet_1588_event0_in.

 

seems there is some misunderstanding as define "{pin_num: K13, peripheral: ENET1, signal: enet_1588_event0_in, pin_signal: GPIO1_IO00}" refers to

 

1.jpg

while ENET1_nINT is connected to SNVS_TAMPER5 is used for GPIO5_IO05 interrupt.

 

Best regards
igor

0 Kudos
194 Views
zhangzhaoxa
Contributor I

Thank you for your answer. Then what is the use for ENET1_nINT PIN? I search the pin-defines in u-boot codes and SDK codes, find 'SNVS_TAMPER5  for GPIO5_IO05' not defined in enet module. Is that means this pin is not needed?

0 Kudos
190 Views
igorpadykov
NXP TechSupport
NXP TechSupport

ENET1_nINT is interrupt from KSZ8081 (U1501 SPF-28616 i.MX6UL EVK schematic),

it is connected to processor gpio and can notfy processor about KSZ8081 state.

In linux seems such codes are not implemented.

 

Best regards
igor

0 Kudos