This is the mail archive of the ecos-bugs@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1000910] New port: Ethernet over SPI driver for ENC424J600


Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000910

Ilija Stanislevik <ilijas@siva.com.mk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #1033|0                           |1
        is obsolete|                            |

--- Comment #11 from Ilija Stanislevik <ilijas@siva.com.mk> 2011-02-17 10:43:46 GMT ---
Created an attachment (id=1132)
 --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1132)
Patch to ecos.db, ChangeLog and STM3210eval HAL

STM3210e_eval HAL:

STM3210e_eval HAL defined resources used for SPI Ethernet driver are now
parented in SPI Ethernet driver.

User enters port and pin to which interrupt from SPI Ethernet controller is
connected. Default values are intentionally made unacceptable, so the user is
given a chance to think and enter data which match his hardware situation.

Interrupt vector is automatically calculated based on pin entered.

User can select to which of the STM32's SPI buses is connected the Ethernet
chip. Only the buses which are enabled in SPI driver are available for
selection. This option requires at least one SPI bus to be enabled. If none is
enabled, the "requires" mechanism automatically enables bus 1. I find this safe
enough because if there is only this SPI device in the system, it is highly
likely that it is connected to bus 1. If someone adds more SPI devices, or a
device to another SPI bus, he/she will be aware of the possibilities and will
enable and select correct buses. Using the same logic, the chip select number
defaults to 0 (indicating the first cs from the list defined in SPI driver),
which I made the lowest legal_value. I wasn't able to establish a hard upper
limit, so I put one which I deem fair enough.

SPI bus pin toggle rate is required to be 50MHz, which accommodates for
enc424j600's SPI 14MHZ rate.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]