--- Quote Start ---
originally posted by rugbybloke+jun 13 2006, 12:23 pm--><div class='quotetop'>quote (rugbybloke @ jun 13 2006, 12:23 pm)</div>
--- quote start ---
<!--quotebegin-frd66@Jun 13 2006, 02:17 AM
thanks banx,
actually, my system does just nothing for now.
it's why i am quite worried about futur with this os on my system.
i've tried with a slower system tick (100 hz), but it isn't better.
do i have to unmask interrupt or something like that before using this driver ?
-- fred
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=16147)
--- quote end ---
--- Quote End ---
There are two drivers polled and interrupt driven, you should not be manually interfering with interrrupts this should be left to the driver. Without looking at your entire application it's tricky to diagnose the problem, I suggest you follow the instructions to get one of the examples working on a development board, once you have that working then try to build your application on this board, then try your own hardware.
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=16153)</div>
[/b]
--- Quote End ---
That's not so simple !
Of course, I use the interrupt version of driver.
Till now, I have the following results :
- it works on EP2C35 at 85MHz with Altera HAL
- it works on EP2C35 at 85MHz with eCos
- it works on our hardware at 20MHz with Altera HAL
- it
doesn't works on our hardware at 20MHz with eCos
Unfortunatly, I'm not good enought to program the PLL (for the SSRAM) as required to make my EP2C35 running at 20 MHz. It would help me to unvestigate the things...