Atmega多线程开发：栈指针操控失败致函数跳转异常求助

Hey there! Stack manipulation for AVR multi-threading can be finicky—let's walk through the most likely issues keeping your code from jumping to func after returning from go_to_func.

1. Double-Check Your go_to_func Assembly Logic #

The core issue is almost certainly in how you're modifying the stack to replace the return address. When you call go_to_func, the AVR automatically pushes the return address (the next instruction after your go_to_func call) onto the stack. Your assembly needs to overwrite this address with func's address so the ret instruction jumps there instead.

Here's a correct example of how to do this (assuming func is a known function):

.global go_to_func
.func go_to_func
go_to_func:
    ; Load Stack Pointer into Y register (R29:R28) to access stack contents
    in r28, SPL
    in r29, SPH

    ; Replace the stack's return address with func's address
    ; Stack top holds the low byte of the original return address first
    st Y+, LOW(func)   ; Write func's low byte to stack, increment Y
    st Y, HIGH(func)   ; Write func's high byte to the next stack position

    ret                ; Now ret will pop func's address into PC
.endfunc

Common mistakes here:

• Mixing up the order of low/high bytes (AVR expects the low byte first in the stack for return addresses)
• Failing to correctly access the stack (not loading SP into Y before modifying stack values)
• Forgetting that ret pops two bytes (PCL then PCH) to set the program counter

2. Verify Stack Initialization & Memory #

AVR stacks grow downward from the top of RAM—if your stack pointer isn't initialized correctly, your stack operations will corrupt memory or fail silently. Make sure your main starts with:

#include <avr/io.h>

int main(void) {
    // Initialize stack pointer to the end of RAM
    SP = RAMEND;

    // Rest of your init code...
    DDRD |= (1 << PD3); // Don't forget to set PD3 as output!
    go_to_func();
    // ...
}

Also, check that you have enough free RAM—if your stack is overlapping with other variables, modifying it can cause unexpected behavior.

3. Test func Isolated First #

Before debugging the stack logic, confirm func works on its own. Call func() directly in your code and check if PORTD's 3rd pin is set (use an LED or multimeter). Don't forget to set DDRD for PD3—this is a super common oversight that makes it look like func isn't running when it actually is.

Example func code:

void func(void) {
    PORTD |= (1 << PD3);
    // Add a loop here temporarily to keep the pin high for testing
    while(1);
}

4. Check Compilation & Linking #

• Make sure asm1.s is included in your build process (most AVR toolchains will compile .s files automatically if they're in the project).
• Declare go_to_func correctly in your C code with extern void go_to_func(void); so the linker can find it.
• Check your project's .map file to confirm func's address matches what you're using in the assembly (if you're hardcoding it instead of using LOW(func)/HIGH(func)).

5. Debug with Hardware (If Possible) #

If you have an AVR debugger like Atmel-ICE:

1. Set a breakpoint at the ret instruction in go_to_func.
2. Inspect the stack contents before ret executes—you should see func's low byte at SP and high byte at SP+1.
3. Step through the ret and check the program counter to confirm it jumps to func's address.

Without a debugger, add simple LED blinks before/after go_to_func to confirm it's being executed, then check if func's LED turns on.

内容的提问来源于stack exchange，提问作者Radu