> On Fri, Aug 02, 2019 at 10:14:28AM +0200, [email protected] wrote:
...
> > Ok, how do you want to handle this then ?
> With  data/0/PARTS as intermediate step.

That seems to be a good idea.

> > To manually update the directory column is a pain that I want to avoid.
> 
> Pain is a human thing.

Got me there.

> Yes, updating the directory column will require human attention.
> Luckly there is no need for a bulk update that might wear down humans.
...

///

Regarding the mapping idcode -> manufacturer

JEP106AZ lists 75 comany name changes, e.g.
 Siemens -> Infineon
 Motorola -> Freescale
 Philips Semi (Signetics) -> NXP
 Toshiba -> Toshiba Memory Corporation

and we have already seen that urjtag disagrees with jep106az in
my mail from aug 1 (the first one in [1]).

[1] 
https://sourceforge.net/p/urjtag/mailman/urjtag-development/?viewmonth=201908&viewday=1

Then manufaturer (the full name) is only used in presentation, like 
in print chain.

There is no way that we can know that this chip is from that year when 
that company owned the idcode.

Why not just take current owner of the id as shown in (latest) jep106
and be done with it ?

///

And regarding idcode -> part
If we are lucky, there is just one uniqe chip part (as in register 
setup, set of instructions, signal names, bsr use) that matches
bits 27-12 of the idcode.

Currently I have four devices matching the same idcode:
$ grep -l 0110010000100000 *
STM32F1_Low_Med_density_value_LQFP100.bsd
STM32F1_Low_Med_density_value_LQFP48.bsd
STM32F1_Low_Med_density_value_LQFP64.bsd
STM32F1_Low_Med_density_value_TFBGA64.bsd

that has different pin map and boundary register setup.

This cannot be expressed in the current
data/<manf. nick name>/<part name>/<stepping name>
setup. So why bother ?

///

It would be more efficient to have something like
data/<manuf. id>/<part id>/<bsdl files>
and then the user has to tell the program which of theese <n> files 
matches your chip (in this position of the jtag chain).

Why bsdl files:
. always use data from as close to the source as possiblea
. they are what the manufacturer publishes
. current data/<mfg>/<part>/<stp>/file setup is just a cache of the 
  above
. if you miss a file, you can get it from mfg. or from e.g.
  http://www.bsdl.info/index.htm

Regards,
/Karl Hammar



_______________________________________________
UrJTAG-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/urjtag-development

Reply via email to