This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems using two programs

I have created two separate programs for my AT89C51ED2: bootloader (0x0000) and normal program (0x2000). I use an absolute memory addressed variable to distinguish between the two modes of operation so that interrupts either execute code in the bootloader or call the appropriate ISRs in the program code (above 0x2000). The following is an example of the code used for interrupts in program code, in order to eliminate the usual pushes, pops and reti done by the bootloader ISR.

/** Timer 1 ISR.
	*/
void interruptTimer1(void) interrupt 3
{
	#pragma asm
	lcall interruptTimer1Mirror
	ret
	#pragma endasm
}


/** Timer 1 interrupt working function. This routine is used for delays.
	*/
void interruptTimer1Mirror()
{
	timer1Interrupted = TRUE;
}

This seems to work fine most of the time, but it seems that some of the program variables are being corrupted (idata and xdata). Is this a problem with the linker/locater not knowing about the separate bootloader program/project? Is there a better way to handle the fact that the interrupts always result in a jump to the table at 0x0000(ie. in the bootloader)?

Parents Reply Children
  • Many thanks for your reply. My intention is to make the device upgradable in the field via an external UART chip (not the built-in serial port). In the stand-alone bootloader (0x0000-0x2000) I call the API routines which reprogram the device program code (0x2000-0xFFFF). I am not using a PC to download new firmware. My problem seems to be getting the two programs to work independantly (specifically the interrupt side of things) without corrupting data in the main program. Is there no way to get the interrupts to jump ONLY to my new vector table at 0x2000? What other ways are there to make the device network field-programmable ie. without going to each and every device and plugging in a serial cable?

  • I wish to do the same thing. Is there a Flip for Cygnal C8051F021 ?

    Thanks.

  • I wish to do the same thing. Is there a Flip for Cygnal C8051F021 ?
    The downloading software for the SILabs (nee Cygnal) chips is JTAG based. The software is free and you need a 10 pin JTAG connector on your board and an EC2 (serial) or EC3 (USB) adapter.

    Erik

    PS: you can get a complete devkit including the EC adapter for about $10 more than just the EC. I have a lot of SILabs devboards because I needed 8 EC2s for my field guys and took the chance to but devkits.