We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hello,
I've problems with the printf() routine. I receive frames over the ethernet in a very short intervall. If I received a frame I set a flag in the ISR.
void ethernet_interrupt(void) __irq { unsigned int status; AT91PS_EMAC pEmac = AT91C_BASE_EMAC; status = pEmac->EMAC_ISR; if (status & AT91C_EMAC_RCOM) /* Receive complete */ Emac_Receive++; // clear receive status register pEmac->EMAC_RSR &= ~(AT91C_EMAC_OVR | AT91C_EMAC_REC | AT91C_EMAC_BNA); AT91C_BASE_AIC->AIC_EOICR = 0; /* End of ISR */ }
In the main routine I ask if the flag is set -> if it is set, I use printf() to see via the usart that I get a new frame...
printf("h");
The problem is that I always get a data abort within the printf() routine..
Could it be that the ethernet frames came to close together (in a short time) so that the printf() routine has not finish to transmit the last character?
And after the ISR the printf() routine don't know what to do / what to send -> data abort??
If the printf-argument is much bigger - it is often so that I only can transmit one or two letter - but not the whole word...
e.g.
printf("hello world\n");
I only transmit "hel" - that's all...
best regards Johannes
You often post code that doesn't match your descriptive text - or text that doesn't match your code.
Can we be sure that you really check if the UART is ready before you insert the character? The '\n' part is special, since you make two inserts in your function.
If the first insert (the '\r') is done before the UART is ready, it may/will kill the character directly before the '\n' in the input string.
is the usart init not ready, when I am able to run the first printf("usart_init\n")? Or how can I make sure, that the usart is really able to transmit all characters?
initialize_usart1(); printf("usart_init\n");
Read my text again. I'm not talking about if the USART is ready after the initialize_usart1() call. I'm talking about if the USART is ready for the '\r' character that you insert before every '\n' character.
ok I figured out, that everything works fine, when I only init usart and ethernet - but when a interrupt from the ethernet occured - COM1_1 don't work...
while(1) { if(Emac_Receive >= 1) printf("%x\n", COM1_1); }
Emac_Receive is higher than 1 when a interrupt occured...
then I only get "fff" or "fffc4" - always the beginning of the right address but not the whole address which is 0xFFFC4000
Johannes
no the '\r' is not the problem
while (!(COM1_1->US_CSR & AT91C_US_TXRDY)) { if(COM1_1 != AT91C_BASE_US1) i++; <- data abort } return (COM1_1->US_THR = ch);
there must be something wrong with the interrupt and the prinft together...
Are you not talking about two separate problems?
One problem is that you loose the last character before '\n'.
One problem is that when you build with Ethernet, your comport pointer gets corrupted and you get a data abort.
right - but the first problem should be solved... that I lost the last character bevor \n -> maybe, the problem was a false heather which was included...
right - the problem happens only when I use the MAC interrupts... I don't know what's the reason for - I have no arrays (the buffer for the ethernet packets are safed in the external sdram..
Increase stack
I try to increase the stack size - and there's one point where I'm not able to get any character by usart() using printf function. Could there be the point that the heap-size is too small for the use of printf?
Moreover does a stack overflow occured always on the same position in my code (if I don't change anything?)?
printf() doesn't need a heap.
Do you know a possibility to see how much stack a programm used?