While i personnaly don't see any advantages, the question is... WHY?
While i personnaly don't see any advantages, the question is... WHY?
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
As you're probably aware from other recent threads, I'm working on a bootloader. For this, it's helpful to have control over what's going where. With the compiler throwing in code wherever, it's sorta messed with that control. I'm certainly able to cope with it in other ways, it was just an unexpected surprise when I got error messages about conflicts with code locations I had @ ORG'd.
If you use DEFINE LOADER_USED 1, it will force PBP to start dropping code
at 0x04h, but it will always insert a GOTO INIT at 0x00h. The boot-loader
software normally just re maps this GOTO to a location after its own jump
vector.
If you're using LCDOUT or I2C, PBP will also insert CLRF FLAGS just before the
GOTO INIT, so that's something else to watch out for.
Bookmarks