> Yes, thank you. I have corrected for that. Now I'm wondering why the
> scan seems to be dying before the end of the ROM table. Why would that
> happen?
>
Could be many different reasons - these will never be fixed.
1) Because the ROM table is full of bugs.
2) There are “hidden features” that are not present but not documented for you.
3) The ROM table points to a ROM extension that has the power or clock to that
section turned off.
It is very hard to get these tables correct in complex chips.
===================
Why won’t this be fixed in silicon?
===================
There is a very important phrase to understand: “mission mode” vrs “debug mode"
Mission mode is the primary reason or use of the chip, it is why they make the
chip at a rate of 1 million chips per week, or month. Think about millions of
chips being made with a mission mode bug - it will effect the millions of
products - Odds are this bug will be fixed.
Think about a cellphone chip - or in this case a “router chip”
Grandmother cannot call you on the phone if there is a bug in her cellphone
chip.
Or grandmother cannot look at goofy cat pictures
Or - grandfather cannot forward you another weird email he thinks is funny.
That bug will be fixed - it effects millions of people
===================
Debug Mode
===================
is not mission mode, not many grandmothers need this feature.
Ok - there are grandmothers (and fathers) who debug software and need
this
The vast majority of customers do not need debug mode it only needs to work
“good enough"
Bottom line - TL;DR version is this:
ROM TABLE USAGE: If it works - use it - if not - Hard code and move on.
It’s useful one time to see if the interface is working - it is never useful
the second time.
-Duane.
------------------------------------------------------------------------------
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
