Hi,
in our project i found some small problems with the MMC Driver in our current Version 2.3.4. It was not possible to use multiple Devices on the same SPI with the old driver becase there was a spiAcquireBus missing. I fixed the problem but now i don't know where to update the code in SVN. I could ...
Search found 22 matches
- Mon Oct 06, 2014 3:06 pm
- Forum: AT91SAM7x Support
- Topic: SAM7 in new ChibiOS trunk
- Replies: 1
- Views: 28893
- Tue Dec 17, 2013 4:18 pm
- Forum: AT91SAM7x Support
- Topic: UART and DMA
- Replies: 10
- Views: 69846
Re: UART and DMA
Hi,
actually we don't use the preserved register. I just had a look at the diassembly to find the cause of my error. We still think the problem is that the stacksize of the irq is too small.
After we increased the __irq_stack_size__ in AT91SAM7X256.ld it seems like i solved the problem.
So the ...
actually we don't use the preserved register. I just had a look at the diassembly to find the cause of my error. We still think the problem is that the stacksize of the irq is too small.
After we increased the __irq_stack_size__ in AT91SAM7X256.ld it seems like i solved the problem.
So the ...
- Mon Dec 16, 2013 6:24 pm
- Forum: AT91SAM7x Support
- Topic: UART and DMA
- Replies: 10
- Views: 69846
Re: UART and DMA
Hi,
I got a little bit stuck with my implementation of the "uartAT91StartReadQueuedI".
In the interrupt of the USART0 i call a callbackfunction. This will call the function "uartAT91StartReadQueuedI" be able to receive. But while calling that i will write over the bounds of the stack in ...
I got a little bit stuck with my implementation of the "uartAT91StartReadQueuedI".
In the interrupt of the USART0 i call a callbackfunction. This will call the function "uartAT91StartReadQueuedI" be able to receive. But while calling that i will write over the bounds of the stack in ...
- Wed Oct 16, 2013 1:18 pm
- Forum: AT91SAM7x Support
- Topic: UART and DMA
- Replies: 10
- Views: 69846
Re: UART and DMA
Hi,
while i'm in callback i maybe miss the start of the next frame.
Regards,
Florian
while i'm in callback i maybe miss the start of the next frame.
Regards,
Florian
- Wed Oct 16, 2013 12:36 pm
- Forum: AT91SAM7x Support
- Topic: UART and DMA
- Replies: 10
- Views: 69846
UART and DMA
Hi,
within our project we need a continous receive of data via the UART. For that case the DMA Controller of the AT91SAM7 provides two Receive (and two transmit) Buffer. Even with a lot of thinking we did not find a solution how we implement that in the lowlevel driver with the given highlevel ...
within our project we need a continous receive of data via the UART. For that case the DMA Controller of the AT91SAM7 provides two Receive (and two transmit) Buffer. Even with a lot of thinking we did not find a solution how we implement that in the lowlevel driver with the given highlevel ...
- Fri Oct 11, 2013 2:28 pm
- Forum: AT91SAM7x Support
- Topic: [TODO] AT91SAM7 CAN Driver
- Replies: 10
- Views: 57541
Re: [TODO] AT91SAM7 CAN Driver
Hi,
If you allow I'll integrate the driver my way and I try to help maintainining as much as possible.
I'd need some tutorial for that.
Regards,
Florian
If you allow I'll integrate the driver my way and I try to help maintainining as much as possible.
I'd need some tutorial for that.
Regards,
Florian
- Thu Oct 10, 2013 1:25 pm
- Forum: AT91SAM7x Support
- Topic: [TODO] AT91SAM7 CAN Driver
- Replies: 10
- Views: 57541
Re: [TODO] AT91SAM7 CAN Driver
Hi,
I'm wondering if the (AT91SAM7) CAN Driver will be integrated in the next version of ChibiOS. Can I somehow support that?
Regards,
Florian
I'm wondering if the (AT91SAM7) CAN Driver will be integrated in the next version of ChibiOS. Can I somehow support that?
Regards,
Florian
- Wed Sep 11, 2013 1:04 pm
- Forum: General Support
- Topic: chEvtWaitAny and Syslock
- Replies: 9
- Views: 7912
Re: chEvtWaitAny and Syslock
I have a thread which does some CAN initialisation. This is needed later on in the main thread. So i just wait until the CAN-Thread is ready. To not suck in a while, which does nothing, i want to yield execution to the CAN thread.
I had other situations where I just wanted to ensure that the thread ...
I had other situations where I just wanted to ensure that the thread ...
- Tue Sep 10, 2013 5:44 pm
- Forum: General Support
- Topic: chEvtWaitAny and Syslock
- Replies: 9
- Views: 7912
Re: chEvtWaitAny and Syslock
Hi,
i think i found the cause of the SV#4. After creating a thread we used chSchDoReschedule() instead of chThdYield(). But why doesn't chSchDoReschedule() work?
Regards,
Florian
i think i found the cause of the SV#4. After creating a thread we used chSchDoReschedule() instead of chThdYield(). But why doesn't chSchDoReschedule() work?
Regards,
Florian
- Mon Sep 02, 2013 5:29 pm
- Forum: General Support
- Topic: chEvtWaitAny and Syslock
- Replies: 9
- Views: 7912
Re: chEvtWaitAny and Syslock
Hi,
the prorities are like in board.c defined highest - 1. We are on a AT91SAM7X256 (board by olimex).
from board.c:
/*
* PIT Initialization.
*/
AIC_ConfigureIT(AT91C_ID_SYS,
AT91C_AIC_SRCTYPE_HIGH_LEVEL | (AT91C_AIC_PRIOR_HIGHEST - 1),
SYSIrqHandler);
AIC_EnableIT(AT91C_ID_SYS);
AT91C_BASE ...
the prorities are like in board.c defined highest - 1. We are on a AT91SAM7X256 (board by olimex).
from board.c:
/*
* PIT Initialization.
*/
AIC_ConfigureIT(AT91C_ID_SYS,
AT91C_AIC_SRCTYPE_HIGH_LEVEL | (AT91C_AIC_PRIOR_HIGHEST - 1),
SYSIrqHandler);
AIC_EnableIT(AT91C_ID_SYS);
AT91C_BASE ...