Virtual Interrupt Vector for bootloader project in IAR

Question

Hi everyone, 
 
 I'm struggling to end a bootloader project. Specificaly, I struggle to perform a clean jump to application after flashing it. 
 
 Bootloader Project 
 In the bootloader project, I'm flashing the application based on a .s19 file generated by IAR in the Application Project. I want the bootloader to jump to a specific address (0x6000 in my case) to run the application. The flashing is OK, I read data from 0x6000 until the end and I am able to flash it. So I don't think the issue is coming from the bootloader project. 
 
 Application Project 
 By itself, the application project is working. Then I convert it to a .s19 file that I use to send data to the bootloader. I modified the linker file to make sure everything is above address 0x6000. But when I'm look at the .s19 file, there is still data remaining below this address. 
 I was advised to check my Interrupt Vector table and to create a Virtual Interrupt Vector Table referring to the real one. The thing is, I really don't know how to do this in IAR (Version 7). I have seen other project using an irq_table.s87 file but I haven't this in my project, only a .xcl file for the linker. 
 
 Thanks in advance for your help, I hope I gave you enough information 
 
 Have a good day !

Lazy Dridri · Accepted Answer

Ok I may have undestand why the boot swap is useful in my case thanks to this post : https://community.renesas.com/mcu-mpu/rl78/f/rl78-forum/29913/rl78-l13-bootloader-jump-to-app-problem/110915#110915 
 So, I'll try this : 
 
 Update flash linker to make sure bootloader is contained in 0x0000-0x3FFF area 
 Flash the bootloader using classic E1 tool 
 Send data to bootloader and make sure that the Start Program of the application is contained in 0x4000-0x7FFF 
 Jump to application from bootloader AND perform boot swap (so Start Program of the application will be connected to the ISR) 
 
 This way, when I want to update application, I can swap again both boot to use the one of the bootloader. 
 Might not be that clear but I'll try this and keep you update. Do you think this process can make the job?

Lazy Dridri · Answer

Hi all, 
 
 Sorry for late answer. So the solution was indeed to use boot cluster swapping as explained in this post : https://community.renesas.com/mcu-mpu/rl78/f/rl78-forum/29913/rl78-l13-bootloader-jump-to-app-problem/110915#110915 
 The Start program of the bootloader goes in Boot Cluster 0 
 The Start program of the application goes in Boot Cluster 1 
 The Bootloader program goes above the Boot Cluster 1 
 The Application program goes above the Bootloader program 
 Thanks for your answer, I know have another issue but I'll create new ticket

JimB · Answer

The RL78 does not support relocating the interrupt vectors, any interrupt will vector to the lower 64KB of the code-flash (due to only 16-bit intr vectors). As such, where the interrupt processing needs to go has to be handled in software by some method. 
 If your boot-loader doesn't use any interrupts, the solution is pretty easy - vector to a long-jump that resides somewhere in the application. 
 If the boot-loader uses an interrupt, the ISR will need to check something to decide whether to handle the ISR in the boot-loader's code or the application's code.

Hossein · Answer

Hi, dear Lazy Dridri. 
 Please check the post blow, it might clarify the topic. 
 https://community.renesas.com/mcu-mpu/rl78/f/rl78-forum/31553/2-project-codes-to-be-placed-in-the-same-rl78g23/112182#112182 If you needed further assistant let us know. and about the linker, please clarify the compiler that you are using in IAR. I hope you find that useful. 
 Best regards. 
 If this response or any other user's response answers your concern, kindly verify the answer. Thank you! 
 Renesas Engineering Community Moderator https://community.renesas.com/ https://academy.renesas.com/ https://en-support.renesas.com/knowledgeBase/

Virtual Interrupt Vector for bootloader project in IAR

Top Replies