I found out a problem developing a project with VDK and ethernet, but fortunately after an intensive step-by-step debugging I'm able to reproduce and describe it with a simple example.
I have a custom board with BF527, and I use PH15 pin as a General purpose output: I want to toggle it for debug purposes.
I slightly modified the \LAN\INETD VisualDSP++ 5.0 Update 6 supplied example to int the adi_flag service and to toggle PH15.
The pin doesn't toggle if I don't call the instructions
result = adi_dev_Control (
in the system_init( ) function.
For my software init process I follow the guidelines from ADI help
- Interrupt control service
- External bus interface unit
- Power management service
- Port control (if applicable)
- Deferred callback service
- DMA manager service
- Programmable flag service
- Timer service
- Real-time clock service
- Semaphore service
- PWM service (if applicable)
then the supplied example initializes the LAN, but after that the PH15 pin doesn't toggle.
But if I re-open the adi_flag service again (after ADI_ETHER_CMD_START command) everything works fine.
Is this an expected behaviour?