USART中断4字节限制?

这与我在前一个帖子中发布的问题非常相似（显然，我无法链接这个线程而没有论坛软件在权限错误上产生异常），但是由于我对代码进行了一些修改，并且使用了稍微不同的处理数据的方式，所以i我现在应该使用一个单独的线程。对于上下文，我现在使用中断来接收我的数据，以我的芯片设置作为同步接收从，并且反复发送字符串“Word”，后面跟着A。我的发射机时钟在4MHz，KbAd值为9.615（SPBRG B的十进制值）。EN 103）。我使用的是两个PIC16F628 A，一个是发射机，另一个是接收机。这是我的接收代码：由于我收到的一些反馈，我学会了如何实现中断，并把数据的处理/写入到一个单独的函数中，并用一个缓冲器…然而，当我收到数据并阅读EEPROM时，我所得到的只是“Word Word Word Word Word”，而D是从来没有写过的。我已经确认了几次D确实是通过检查它来发送的，所以这不是我的发射机代码的问题。我怎样才能确保D确实被写入和处理正确？我得到的建议是，如果我知道数据的大小，我可以把它存储在一个通用缓冲器中，然后把它一次写入EEPROM，但是为了我项目的这一部分的生产目的，实际上，我收到的一个芯片的数据将是随机的，从8到15字节，没有null终止符，我必须正确处理和存储这个。这种随机的数据流每隔几秒钟就会发给我一次。这就让我回到了一个问题：我如何确保准确地处理数据而不丢失任何东西？



      以下为原文

    So this is extremely similar to the issue I posted about here in my previous thread (and apparently I can't link the thread without the forum software freaking out over permission errors), but since I made some modifications to my code and am using a slightly different way of handling my data, I figured I should make a separate thread.

For context, I am now using interrupts to receive my data with my chip setup as a Synchronous Recieve Slave and am repeatedly sending the string "World" followed by a __ms_delay(2000);. I have the transmitter clocked at 4Mhz with a KBAUD value of 9.615 (decimal value for SPBRG being 103). I am using two PIC16F628A's, one acting as a transmitter and the other a receiver.

Here is my reciever code:

volatile unsigned char addr = 0x00;

void USART_init(void){
    TRISBbits.TRISB1 = 1;
    TRISBbits.TRISB2 = 1;
   
    TXSTAbits.SYNC = 1;
    RCSTAbits.SPEN = 1;
    TXSTAbits.CSRC = 0;

    PIE1bits.RCIE = 1;
    INTCONbits.GIE = 1;
    INTCONbits.PEIE = 1;
   
    RCSTAbits.CREN = 1;
}

void writestuff(unsigned char x){
    EEPROM_WRITE(addr, x);
    addr++;
}

void interrupt message(void){
    if(PIR1bits.RCIF == 1){
        unsigned char d = RCREG;
        writestuff(d);
    }
}

void main(void) {
    USART_init();
    while(1){}
}

Because of some of the feedback I received, I learned how to implement interrupts and put the processing/write of data to the EEPROM in a separate function with a buffer... Yet still, when I receive the data and read the EEPROM, all I get is "WorlWorlWorlWorlWorl", the d is never written. I have confirmed several times that the d is indeed sent by checking for it specifically so it's not an issue with my transmitter code.

How can I make sure the d is indeed written and processed correctly?

I have gotten the recommendation that if I know the size of the data, I can just store it in a universal buffer and then write it all at once to EEPROM, but for production purposes of this section of my project, in reality, the data that I receive by a chip will be random in size, ranging from 8 to 15 bytes with no null terminator and I have to correctly process and store this. This random stream of data will be sent to me every couple of seconds or so. So that leads me back to the question of how I can make sure to accurately process the data without losing anything?