• Hi, • • We have a need to start Keil UV4 Debugger from Command Line for loading and executing a C166 ModV2 application of XLARGE memory model. We also need o use a .ini file in which we give definition of a function say retrieveData() that will printf a memory containing a char array, after setting LOG><ourfile>. Next we set breakpoints at a function in our app at which we will invoke this function afrom the first time and then proceed. The app will of course cycle back to this break, execute the retrieveData() and again proceed. When we are done, we stop the debugger and quit Keil. • • The .ini file looks like • • load Executable • func void retrieveData(void) { • int i; • i = 0; • while (chararray[i]) printf("%c",chararray[i++]); • } • bs myfunction,1,"retrieveData()" • log > mydataout.dat • G • EXIT • • and at another place we invoke uv4 as • • start /WAIT uv4 -d $pwd/myproj.uvproj • • The above works well in uv4 for C166 Mod167 even in Simulator, but there seems some trouble in uv4 C166 ModV2. • • Has anyone any material about this behaviour and solution plese. • • Thank you. • • Krishnan