Hello,
i do not find a requirement that the cache needs to be off in the vxWorks manuals.
The entry point sysInit(int) intended by Windriver to be called from the vxWorks bootrom, a very small vxWorks system. The routine is called by the go() handler in the bootrom, that clears the cache from start of image to end of usable memory.
The POWERPC implementations only invalidates and disable the cache, the ARM implementations also flush it.
U-boot will be on the save side, if it disables the data cache before calling vxWorks sysInit(int).
Reinhard
-----Original-Nachricht----- Subject: Re: [U-Boot] Problems using vxboot Date: Wed, 10 Aug 2011 11:40:43 +0200 From: Detlev Zundel dzu@denx.de To: Reinhard Arlt reinhard.arlt@t-online.de Cc: u-boot@lists.denx.de
Hi Reinhard,
i run into a strange problem booting vxWorks on the cpci750 and vme8349 using u-boot 2011.06.
The decrementer slot contains old code. The problem is starting vxWorks with the data cache enabled.
The code below fix the problem. It disable (and flush) the data cache, and set the start parameter to cold boot for the vxWorks sysInit(int p0) routine.
Is this code acceptable?
If vxworks needs the caches disabled to start, then sure why shouldn't it? Isn't there some vxWorks documentation item for that? It would be good to reference that in a comment.
Cheers Detlev
-- Less talking -- more hacking -- Olin Shivers -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de