how to remap interrupt vector - pic18f4550

[amgen]

Along the same lines of recieving data,
I frame the data with a start(to take) and end(to trigger) char, fast enough to be handled in the interrupt routine, then flag basic looping at 10X/sec.

IE......... [ abcdxyz...COMMAND.....1234]

"[" to start taking chars to array,
"]" to stop taking and flag to basic to parse for command ete etc.

the "[" always sets the array back to start.

Don
Amgen

[Charles Linquis]

But I don't have that luxury. I'm getting SNMP packets (80-230 bytes). The host sends me a request, and has about a 20mSec timeout. I have to do an enormous amount of processing to decode the packets, grab the appropriate data, rebuild the response packet, and send. I previously did everything (receive, process, send) in one long ISR. That worked great. I was getting queries every 410mSec. The problem is - the customer added a second host that was sending me queries every 1 second. Most of the time, all was OK. But of course, there were times when the two requests hit me at virtually the same time. Since I was processing and sending in the 'receive' ISR, I missed the second request. I should mention that I don't have any flow control out of my network port. The hardware is already in the field and the handshake lines are not connected.
So I made the ISR a 'receive only' segment and made my buffer twice as long (so it could handle two incoming packets), and modified my routines so that they worked with an offset. Offset '0' is the first byte of the first packet and offset $100 is the first byte of the second packet.
When a packet came in, I set flags (packet offset 0 recieved and packet offset $100 received) and tested those flags in my main loop. Unfortunately, my main loop takes up to .5 second to execute. The host would time out before I sent my response.
So I set up Timer3 Int as a low-priority int, but didn't turn on the timer. I set PIR2.1 just before I exit the (high priority) receive ISR. As soon as it exits, it goes into my 'fake' TMR3 int and processes and sends the packet. If another packet comes in right after the first, the high priority receive interrupt stops the 'process and send' routine and grabs the packet. It then goes right back to processing and sending - both packets if it needs to. I'm running the net-port to PIC interface at 230K baud.
It all works!

[amgen]

OK, I think I follow your sequence. Sounds like your using Basic serout or HWserout ??
I use TXint to send from either ram(array) or flash(1 of several tables at the end of flash mem).
I will put together the easy change to PB18....lib for arrayread and send you. You (and me too) can be confident since Darrel checked it out.
Don

[Charles Linquis]

I'm using HWserout, but I don't think I could do much better using TXint. It isn't the sending time that is the problem, it is the large amount of processing I have to do with the packets.
SNMP requires that I do lexicographical sorts (1.2.1.3.1.1.1.4.2.1 is before 1.2.1.3.1.1.1.4.2.1.1 and 1.2.1.3.1.1.1.4.2.1 is after 1.2.1.3.1.1.1.3.9.9.9.9.9.9.9)
Even if you get sent a string that does not match one that you have (internally) in your list, you have to pick the first item in your list that (lexicographically) comes after the received string,
then grab the appropriate data, perform encryption on certain bytes (3 different types, depending on the data), re-assemble the variable-length packets, calculate the LRCs, and send.
And some of the data is a (calculated) number 40 bits long.

[amgen]

alot to ask of a PIC !

[Charles Linquis]

It is doing a lot of data collection at the same time. That is why I'm running my '8723 at 40MHz and it is full of code.