Not applicable
Sep 24, 2014
12:04 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sep 24, 2014
12:04 AM
4 Replies
Not applicable
Sep 24, 2014
04:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sep 24, 2014
04:07 AM
Uhh, I dont think so. You have to use DAvE in order to get an Ethernet driver quickly.
Sep 29, 2014
08:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sep 29, 2014
08:36 PM
Hi,
You can use the follwoing apps from DAVE3.
1. ETH001 >> Driver for ETH MAC
2. ETH002 >> Driver for PHY
Best Regards
Travis
You can use the follwoing apps from DAVE3.
1. ETH001 >> Driver for ETH MAC
2. ETH002 >> Driver for PHY
Best Regards
Travis
Not applicable
Oct 01, 2014
01:09 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 01, 2014
01:09 AM
Hi Travis,
thanks for your response. I know that the ETH1/ETH2 Drivers do have the functionality needed. But still there is a gap in the Interface (CMSIS) between the DAVE Drivers and the KEIL IP Stack which I expected to be closed by the Infineon DFP/BSP for KEIL MDK. Can you suggest an example which can speed up my neccessary work, or is a CMSIS abstraction layer for the DAVE ETH Drivers in place.
Best regards,
Frank
thanks for your response. I know that the ETH1/ETH2 Drivers do have the functionality needed. But still there is a gap in the Interface (CMSIS) between the DAVE Drivers and the KEIL IP Stack which I expected to be closed by the Infineon DFP/BSP for KEIL MDK. Can you suggest an example which can speed up my neccessary work, or is a CMSIS abstraction layer for the DAVE ETH Drivers in place.
Best regards,
Frank
Oct 09, 2014
07:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 09, 2014
07:29 PM
Frank wrote:
Hi Travis,
thanks for your response. I know that the ETH1/ETH2 Drivers do have the functionality needed. But still there is a gap in the Interface (CMSIS) between the DAVE Drivers and the KEIL IP Stack which I expected to be closed by the Infineon DFP/BSP for KEIL MDK. Can you suggest an example which can speed up my neccessary work, or is a CMSIS abstraction layer for the DAVE ETH Drivers in place.
Best regards,
Frank
Hi Frank,
So sorry to say that the CMSIS abstraction layer do not have any relationship with ETH001/002 etc. May I suggest that you port the codes from ETH001/002 into your KEIL platform as they are pretty standard software.
best regards
Travis