The RI Digital TIM can be used as a Boundary Scan tool as long as the digital scan patterns are in Guru after having been translated using the Digital Translator application program.
Loading scan patterns into the digital TIM
From the Configuration Panel for the digital TIM press the Edit Patterns button
The left side shows the current patterns loaded and as each is selected, the right side shows info about the pattern.
Pattern Menu picks
add from guru - Provides selection which can be added
remove - Removes the selected pattern
rename - Rename the selected pattern. This name is what is referenced in the test plans
save - Writes the pattern directory to the TIM.
This is done automatically after each load so it is not necessary
restore - Re read the directory from the TIM. Again this is automatic
test - Computes the checksum of the pattern selected.
Note : The result is written to the message window.
Used to check for possible corruption of the data once transferred to the TIM.
inspectMaps - These are the serial scan maps.
Pattern Menu picks sub menus
Dut/pins/dib Sub menues
dut Selects a device family.
This is optional and if selected limits other selections to only those for this device
pins Device pins objects have information on the device to hardware mapping.
For use see pin mapping below
dib The dib may also have pin mapping so it may need to be selected as well.
Erase Sub menues
memory Executes a full erase of the entire memory. Takes about a minute
All patterns Erases just the used portion.
last pattern Erases just the last pattern written
NOTE : Erased files and pattern storage
The memory in the TIM is flash memory so files when files are added they are not actually
removed but overwritten. During development work, it may beneficial to clean up the memory
occasionally, if it gets filled with obsolete objects.
In order to load the pattern memory we need the pattern file but we also need enough information
to map the logical pins to the hardware pins. There are there way to do this:
Add hardware mapping to the pattern file
This can be done with a text editor as it is not recommended since it hard wires the pattern
file to specific pins. However its quick and simple.
To the signals section of the pattern file add some lines which look like these:
Define a Device Pins object with special pin identifiers.
The identifiers need to have a form like D1-4.
The pin name is not important and the signal needs to match the signal names in the patter file.
N55 is an example RiDevicePins object. Use the device connection editor to create/modify
Define a Dib and a device pins.
In this case the pin identifier can be arbitrary in the device pins object
(perhaps matching the device pin number) with the dib mapping from pin identifier to the TIM pin.
The main purpose of this approach is to support multiple sites where the dib does the actual mapping.
Basic loading instructions
Select add from guru
You will be asked for a dib but this is optional
The pins are selected from the pattern file ( if not there will be a prompt to select them).
You are then asked for a pattern selector. This is the name which will be used in the test plan.
If there are multiple patterns in the file and you wish to accept the pattern names from the file
then typing * will keep you from continuously getting the selector prompt.
If the name matches one already in the TIM then it is replaced
The file then loads and update the TIM directory.
Errors during loading.
The main potential error currently is a warning that the scan map is full.
There are 12 maps available each holding 32 states of 64 possible.
This is enough for most scans. If you get this message one solution is to select another
when translating. If this does not work then less signals need to be mapped
( for instance reset may be constant thoughout the scan and could be removed.)
The final solution is to convert to a wide ( full width pattern ) which uses lots more memory
but should be able to handle any pattern.
Scan maps map the scan vector into a compressed format.
They are created on the fly as vectors are encountered.
They are stored in the TIM along with the pattern information
Standard ( reserved names ) are scan, spi jtag and i2c.
There are 12 maps available for users.
Names are alpha numeric only and must be less than 28 chars.