Why do you think caches have something to do with the problem? Also, how do I config the compilation to disable caches? The only configuration I'm aware about it modifying the header file: $(uboot_folder)/include/configs/davinci_dvevm.h
Thanks On Mar 31, 2015 2:39 AM, "Jeroen Hofstee" <jer...@myspectrum.nl> wrote: > Hello noti1234, > > On 30-03-15 20:44, noti1234 wrote: > >> I'm having problems booting my DaVinci board with Green-Hills' Integrity >> OS. >> My setup is: >> Hardware: TI's DaVinci EVM: >> http://www.spectrumdigital.com/product_info.php?products_id=192 >> u-boot: u-boot-2015.4-rc3. Configured for dvevm with elf support. >> >> * If the board's flash is programmed with u-boot then the Integrity OS >> initialization process gets stuck. >> * If the board's flash is erased (which means I get BOOTME BOOTME >> requests) >> then the Integrity OS initialization process, using Green Hills probe >> (something like JTAG), works fine. >> >> This behavior is strange. It seems that something in the u-boot >> initialization process, messes up something for the Integrity OS to run >> smoothly. >> >> To make things clearer: >> The u-boot works fine before trying to boot the Integrity OS elf. I can >> read >> memory regions, write, tftp, etc. >> The problem is that the init process of the Integrity OS gets stuck. >> So currently I can only boot the board using the Green Hills probe, when >> the >> flash has no boot loader. >> >> Do you have any idea how to approach this problem? Any way to debug it? >> >> > I have no knowledge of your actual setup, but it might be worth > checking if disabling caches at compile time helps (in your boards config > or perhaps menuconfig nowadays). > > Regards, > Jeroen > > > _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
