The code will not affect those who are not using a supported operating
system. I have used the automatic thread awareness code with no
problems in the following cases:
* No RTOS - STM32
* FreeRTOS - STM32
* ThreadX - STM32
I agree the memory state issue is still a potential problem which
would need resolving....
Evan
Quoting Michel Catudal <[email protected]>:
Le 23/08/2011 03:47, Evan Hunter a écrit :
The way it has been designed means that no memory locations are
touched until symbol locations are provided by GDB. The symbols
names which are available tell the system which RTOS is in use.
On most platforms OpenOCD would have initialised the memory system
by the time GDB attaches. However, you are correct, on some
platforms the memory controller may have to be enabled in the
software. Hence, I would suggest only enabling the feature for
Cortex-M3 devices or just STM32 devices to start with, since it has
only been implemented/tested for these so far...
Evan
It is a mistake. It could be available but disabled by defaults.
There may be many people who use an RTOS but a lot more not using
any and not planning to ever use any except some small version.
Openocd should not make any assumption on how ram is used. To do
that is opening a can of worms that cannot be close.
It OpenOCD would be implemented like that I would have to make a fork of it.
Michel
--
Tired of Microsoft's rebootive multitasking?
then it's time to upgrade to Linux.
http://home.comcast.net/~mcatudal
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
