AN2295 bootloader and I2C, with S08SG32

[Witya]

hello everyone,

I am using MC9S08SG32 uC, hc08sprg-s08sh.mcp slave bootloader, with "S08SH32 - TB1TB0 (TxD/RxD)" cofig.

bootloader works, loads the app and runs it, as it should (I didn't design the bootloasder, an2295sw.zip had it, and I modified it a bit, for my purpose)

but app uses I2C protocol (to transfer data), that is not going through the TxD/RxD channel. Aparrently it is initialized and then drops.

the app works perfectly if it is flashed to the uC, but with bootloader it does not initialize I2C, or initializes, but then closes, for some reason...

any ideas or questions are welcome

[bigmac]

This is your second attempt to start a new thread for the same problem as your existing thread.  Again, please do not split threads.

Furthermore, I believe the reason for your problem has already been outlined in the earlier thread.  You do not have the appllication's vector table, including the IIC interrupt, at the correct relocated position.

Mac

[Witya]

one more question,

is it possible to turn off protecttion of the bootloader flash? or set it limited like from one address to another, not like it is now from some address till 0xFFFF?

[Witya]

so the application's interrupt vector table is at correct relocated position, because application always restarts... I tried to experiment with it, and app hangs if there is some different address.

since IIC interrupts are in this table, means app cannot use them for some reason... means it is impossible to use IIC with bootloader. weird, but true

[Witya]

hello everyone,

aparently the application does not proceed to the interrupt service routine of I2C... and app restarts...

how can I know where these interrupts are located?

addresses 0xFFB0 - 0xFFFF are relocated and because of that bootloader should be transparent to the app? or not?

if it is transparent, then all interrupts should be found? not?

correct me if I am wrong.

[Witya]

Hey,

well as far as I understood the all vectors are relocated correctly by the bootloader.

there are 2 vectors that are not relocated, but they are created by the app and bootloader at the same address.

maybe the problem with the app...