Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why can I debug the EMAC and PHY device drivers in the NDK example projects?

April 26, 2017debug device Drivers emac ndk phy Projects

0

Posted

Why can I debug the EMAC and PHY device drivers in the NDK example projects?

1 Answer

0

Posted

This is because the hardware initialization routines are inside the HAL libraries. For example, the DM6437 EMAC device driver is the library . Only assembly step-by-step debugging is allowed (more on this below). However, all NDK examples have callback routines from the device driver that help verify if it is working properly. In the case of DM6437, the file contains two callback functions: • DM64LCEMAC_getConfig() reports the MAC address was properly assigned to the EMAC and allows you to configure what interrupt source will be used by the EMAC peripheral: variable *pIntVector; • DM64LCEMAC_linkStatus() is used to report that a valid link was detected and at what speed. If device driver source code debugging is really needed, this is possible by including the HAL and low-level source files into the CCS project (typically installed under %NDK_INSTALL_DIR%/packages/ti/ndk/src/hal/). The build process will overload the device drive