Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Calling NetIF_Add() Function

If the function doesn't return:

  1. Verify that your driver Base Address is correct (see section Network Interface Configuration).
  2. Could also be a problem with your BSP Clock or GPIO configuration (see section Network Board Support Package).

If the target crashes before returning:

  1. Verify that your driver Base Address is correct (the target should crash in NetDev_Init()if the Base Address is incorrect).
  2. Could be a problem in your BSP (the target should crash in NetDev_Init() after a BSP call).
  3. Your start task stack size could be insufficient.

If the function returns an error

Memory related error

Queue size related error:

Driver Configuration error:

Driver Initialization error:

PHY Invalid Configuration error:

PHY Initialization error:

  • If the stack is not able to read and write PHY register, the BSP GPIO configuration must be incorrect (see section Network Board Support Package). 
  • Bad PHY driver.

Other error:

  • Refer to net_err.h for the error code details.

Calling NetIF_Start() Function

If the function returns an error

  • Refer to net_err.h for the error code details.

If the target crashes before returning:

  • Is the BSP ISR Handler reached? If the ISR Handler crashes before completed: Y our ISR handler could perform an invalid operation.  You have a CPU, Compiler or Linker configuration issue. Check interrupt vector table location and interrupt configuration.

Is Net_DevRx() reached?

  • If reached : Increase the Rx Task stack size.
  • If not reached : There is an issue with the OS task switch. 

Does it crash when a context switch occurs?

...