Hi all, I have a multicore SoC, and I use "target create" command to create several targets, one for each CPU.
Main CPU is mentioned first. When I want to load and execute Linux kernel on secondary CPU, I use "mon targets second" to switch to the second target from within GDB, and then I do "load" to load kernel to SDRAM of my remote target. At this moment I have OpenOCD complaining about work area, although I had defined working area for the secondary (but not primary) CPU. That means that code load is executed by the primary CPU, and not secondary as I thought, because I can see tha OpenOCD keeps star on second target, marking this one as active. Also, once the code is loaded it is executed on the primary CPU. How come ? And why the OpenOCD is marking that second CPU is the active target ? How to force GDB to use second target in a multi-target configuration, and not always the first declared by the "target create" command ? Best regards, Drasko _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
