- Thu Jan 14, 2010 8:15 am
#90578
Is there a bugtrack system for OpenOCD??? I can't fine one so I am reporting this here.....
Looking at svf.c, the code wrongly assumes that there is always a space delimiter e.g. TDI<space>(123) when it can be TDI(123).
This is a fundamental mistake. See the spec for SVF, here http://www.asset-intertech.com/support/svf.pdf this makes no such assumption about the use of spaces and does not use them in it's examples.
The code is written such that every keyword is paired with a value with a space delimiter in between but this is not always the case. I was going to fix it, but so far as I can see the parser needs a complete rewrite to remove this fixed pairing and I have not got time to do that right now.
BTW: I noticed this as Actel's SVF output does not have spaces.
For now I will write a post processor that will convert non-space delimited to space delimited.
Looking at svf.c, the code wrongly assumes that there is always a space delimiter e.g. TDI<space>(123) when it can be TDI(123).
This is a fundamental mistake. See the spec for SVF, here http://www.asset-intertech.com/support/svf.pdf this makes no such assumption about the use of spaces and does not use them in it's examples.
The code is written such that every keyword is paired with a value with a space delimiter in between but this is not always the case. I was going to fix it, but so far as I can see the parser needs a complete rewrite to remove this fixed pairing and I have not got time to do that right now.
BTW: I noticed this as Actel's SVF output does not have spaces.
For now I will write a post processor that will convert non-space delimited to space delimited.