yes and no. There is a lot of setup i haven't been able to figure out in Integrity yet so i initially boot with U-boot. With U-boot i am able to bootm my kernels just fine. The problem that i have is i need a more intelligent boot program that can do more that u-boot so I'm trying to use an Integrity bootloader. I can load and start if from u-boot just fine. Then, using the Integrity bootloader, i want to load and run my application. According to the console output, my application is decompressing correctly and i get a message that the new kernel is booting, but then it hangs. According to Green Hills documentation, i need to disable cache and interrupts before i jump to the new kernel, using a BSP function that i need to write. I have wrote the function and i see that it is called, but i don't know how it is supposed to disable cache and interrupts.
Maybe i need to dive into u-boot code again and see what "dcache off" does. Is there a U-boot command to disable the interrupt handler?
BTW, thanks for your response. Any way you can help would be greatly appreciated, I've been beating my head against this for a couple weeks now.
