Search Results

Well - I fixed it, but not with an interrupt, but rather by polling the CSR in the idle loop. void OS_Idle(void) { // Idle loop: No task is ready to exec char c; while (1) { if ((_USART1_CSR & 0x00000001) != 0) { c = _USART1_RHR; On485Rx(c); } } } So, my code is working, I'm just lacking the proper bit to have the hardware generate the interrupt. Help please.

Well, I got the transmit interrupt to work now, but not the receive interrupt. Apparently I'm not setting up the receive interrupt properly in the USART.

Maybe this will give you some more info. I compiled the example that comes with the AVR32 drivers and needed to add "exception.s82" in the project. But, when I did that I got the following Error[e24]: Segment EV100 (from module "OS_Switch", address [80004100-800041af]) overlaps segment EVTAB (from module "exception", address [80004000-800041b7]) I needed this for the definition of ipr_val used in init_interrupts and register_interrupt which are in intc.c file. I know this is something simple. I …

I'm not getting any output from my USART ISR. I looked at your example code that uses a mailbox as an output buffer and it calls OS_GetMailCond1(). The manual specifically says OS_GetMailCond1() must NOT be used in ISRs. I'm confused. Also, it seems I have not enabled my interrupts properly, or you can not set a breakpoint in an ISR either. I'm using AVR32 and EWAVR32. Does this explain why I get an error when I call OS_EnterInterrupt()? I copied the code from the OS_COM_Init for COM0 to turn on…

Never mind. I started up embOSView and found out that it is the packet wrapper for embOSView. Nice tool!

I used the following: OS_SendString("Hello World!\r\n"); and got the following on hyperterminal: ŒíCHello World! „ Are the extra characters I'm seeing part of embOSView protocol?

Is there an opposite for OS_Q_Create()? I want to create or terminate a task that uses a queue, but there seems to be no way to terminate or delete a queue. I resorted to suspending and resuming the task and leaving the queue initialized.

I'm not sure if this is a SAM-ICE question or an IAR issue, but When I choose the flash configuration of the sample files, I can not set breakpoints in the debugger window. Breakpoints can be set in the editor window prior to build, but not while debugging code running in flash. Running from SRAM or DRAM, I can set breakpoints as usual, but when running from flash, I get a bing from the computer and no breakpoint set. What is the reason for this? Is this an IAR thing, or an ARM thing, or a J-LIN…

The search function on the forum is too literal. I was looking for some help regarding OS_GetMail so I just typed in getmail. That returned no hits. Typing in OS_GetMail got me a few. I'm now searching for a few more items before I post them, and I get nothing in return, but I might not be literal enough. Thanks, Mike.

Thanks. That makes more sense now. I'll have to watch for that in the future. Mike.

Is it possible to run embOSview connected to the target through ethernet so that I can free up a com port for my project? Do I have to create a serial port bridge to a virtual com port in windows, or can I simply specify an IP address and port for debugging?

I'm using OS_GetMailCond1 as such if (OS_GetMailCond1(&mb,&key)) process(key); But it seems that this is no good since the data is left in the mail box buffer. I experimented by using OS_PutMailCond1(&mb,&c) only once, but the process key would run forever. Does OS_GetMailCond1 not clear the buffer automatically? Am I over simplifying this? I went to if(OS_GetMessageCnt(&mb)) { OS_GetMailCond1(&mb,&key)) process(key); } And that seems to work. But, I don't understand the operation of OS_GetMailC…

I'm using the IAR AVR32 compiler. I created a new workspace for the main.c demo application start2tasks. I added the required embos files - OS_Error.c, RTOS_INIT*, RTOS.h and library file osavr32alladp.r82, I get no errors when I compile. But, when I debug, I get the following message: Thu Jun 05 01:52:29 2008: The stack pointer for stack 'Application' (currently Memory:0x0) is outside the stack range (Memory:0xD000 to Memory:0xF000) What am I missing? I added the other setup files one at a time…