Hello
I have notice that my device has had some problems with the Data Abort and
Prefech Data Abort. Then, I found that this abort ocurred because the device
was wrong programmed. Some bytes was diferent from map list.
I have the question if the problem is the lpc or if is possible that the
openoc
On Wed, Feb 25, 2009 at 5:42 PM, Laurent Gauch
wrote:
>>
>> >/ Maybe the check should be put back anyway, even when we know that
>> />/ it takes 7 or less steps in case someone changes the code later.
>> />/
>> />/
>> /No doubt that check is needed, or
>>
>> a function rewrite which changes tms to
> Since I am a dummy, I have experience with "APIs for Dummys".
No problem. If you think it's useful for OpenOCD, feel free to
massage it into the way you want it working. If not, just drop
it :-)
___
Openocd-development mailing list
Openocd-developmen
>
>
> >/ Maybe the check should be put back anyway, even when we know that
> />/ it takes 7 or less steps in case someone changes the code later.
> />/
> />/
> /No doubt that check is needed, or
>
> a function rewrite which changes tms to bit a bit vector, and then
> "bits" (which BTW should be cal
> Maybe the check should be put back anyway, even when we know that
> it takes 7 or less steps in case someone changes the code later.
>
>
No doubt that check is needed, or
a function rewrite which changes tms to bit a bit vector, and then
"bits" (which BTW should be called bitcount to make
> 1) A bad assumption is made in the above code that the number
> of bits is 7 or less. The above code should be changed to
> work with more than 7 bits or at least report the error if
> bits argument is greater than 7.
I had proven that you can reach from every state to every state
in 7 or les
