• Locked Locked
  • Replies 4 replies
  • Subscribers 119 subscribers
  • Views 5973 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

Secondary CPU Boot-Up

Sajid Rabbani Avagundam
Note: This was originally posted on 21st April 2011 at http://forums.arm.com

Environment: ARM-CA9 MultiCore

Pre-condition: Boot monitor starts all the cores together and later continues with primary CPU0, where as the secondary CPU1, CPU2, ... are moved to wait for interrupt condition with WFI instruction.

-------------------- snippet start (secondary CPU wait state)
loop:
wfi
ldr  pc, loop
-------------------- snippet end


Question: For primary CPU, later when boot monitor gives control to u-boot software and finally u-boot gives control to application software. In this application context, if the primary CPU wants to wakeup the secondary CPUs, it basically needs to interrupt them, below observations was done:
  • no interrupt handling was observed by secondary CPUs
  • but when, above shown snippet was modifed to include a 'nop' instruction after WFI instruction, the secondary CPUs started handling interrupts
I assume that this is because of the way the return from interrupt handling is done, something like LR+4, LR, ... so on.

Please clarify/reason-out why it is working in the later modified condition? Or what is the actual procedure to wake up secondary CPUs using interrupts ...
  • Note: This was originally posted on 21st April 2011 at http://forums.arm.com


    Couple of  questions, do you have the CPSR.I bit clear and how do you send the interrupt?


    Boot monitor source code is not-available at present. i have analyzed the assembly source code (disassembly) when we dump the vector area and its vicinity. However, i infer that CPSR.I is definitely cleared, because just by introducing the 'nop' instruction the interrupt is generated and handled.

    Interrupt from primary CPU to secondary CPUs is done using Software Generated Interrupt Register (ICDSGIR).
  • Note: This was originally posted on 28th April 2011 at http://forums.arm.com


    As you're looking at the disassembly, how are you inserting the NOP?

    in application, by overwriting the same source code with additional NOP.



    How  are you checking whether the interrupt is taken?  By breakpointing the  IRQ vector, or just by seeing whether any appears to happen?

    interrupt handler of primary CPU is executed when interrupt handling is required for secondary CPU. I have no HW debugger to make use of breakpoints.



    What  does the IRQ handler do?  Does it return with the standard sequence  (SUBS pc, lr, #4 or equivalent), or to some other address?

    it is a general handler with register dumps. Yes, it does return with "SUBS pc, lr, #4".
  • Arm Employee Badge
    Note: This was originally posted on 21st April 2011 at http://forums.arm.com

    The idea of putting the secondary CPUs into a holding pen, then waking them with an interrupt, is quite common.  Its how Linux boots on most of the A9 boards I've seen, and several of ARM's examples use it as well.

    Adding the NOP should not make any difference.

    Couple of  questions, do you have the CPSR.I bit clear and how do you send the interrupt?
  • Arm Employee Badge
    Note: This was originally posted on 21st April 2011 at http://forums.arm.com

    As you're looking at the disassembly, how are you inserting the NOP?

    How are you checking whether the interrupt is taken?  By breakpointing the IRQ vector, or just by seeing whether any appears to happen?

    What does the IRQ handler do?  Does it return with the standard sequence (SUBS pc, lr, #4 or equivalent), or to some other address?