Xilinx IP core drivers for RTEMS- Keith Robertson still around?

[Robert S. Grimes]

Hi Ed,

Oh, yeah - you did - works great, too!

-Bob

Ed Sutter wrote:
> Bob,
> I gave you what I have for the ML403/micromonitor stuff right?
> If you need help with that, lemme know.
> Ed Sutter
>
> Robert S. Grimes wrote:
>
>> Hi Greg,
>>
>> Please, less formality - Bob is fine by me!
>>
>> Sounds like I'll be following you, I guess!  I had originally (as in 
>> earlier today) thought I'd finish my MicroMonitor work first, but 
>> perhaps I should move RTEMS up first.  It doesn't really matter too 
>> much for me, and hopefully I'll be able to contribute more - given 
>> your schedule.
>>
>> Do you have the TEMAC working yet?  Or are you using one of the 
>> "soft" IP cores?  What serial port core are you using?
>>
>> Take care,
>>
>> gregory.menke at gsfc.nasa.gov wrote:
>>
>>> Thanks Robert!
>>>
>>> Exactly what I needed.  Over the next few days I will be working the
>>> patches in and comparing to the firmware as its been specified in our
>>> board- its quite similar to an ML403.  We do have flexibility wrt the
>>> Virtex firmware so reconfigs there will not be an issue.  I think the
>>> goal will be to create a proper bsp to support our board.  The initial
>>> tests will be RTEMS running our flight software, taking data in over a
>>> serial port and transmitting out of ethernet.
>>>
>>> I'd be happy to share the RTEMS portions of the work & collaborate
>>> wherever its feasable.  We have to be running & stable by the end of
>>> August so development is going to be brisk over the next couple weeks.
>>>
>>> Regards,
>>>
>>> Greg
>>>
>>>
>>> Robert S. Grimes writes:
>>>  > Hi Greg,
>>>  >  > I'm in the same boat as you.  Keith has sent me his diffs, 
>>> which I  > include here.  Note that they are against a little older 
>>> version  > (V4.6.5) of RTEMS, and should work on a suitably 
>>> configured Xilinx ml403  > board.  You'll have to make sure your V4 
>>> configuration is compatible  > with his stuff, or change one side or 
>>> another...
>>>
>>>
>>>   
>
>