PicoBlaze

[jeffrey_a_graham]

I have a design with both picoblaze and microblaze.

I am trying to use both a Microblaze with a MDM (C_JTAG_CHAIN = USER2) and a

picoblaze with JTAGLoader(C_JTAG_CHAIN = USER2) in the same design.

The picoblaze JTAGLoader seems to have the C_JTAG_CHAIN hard coded to USER2 ie 2.

If I change the JTAGLoader VHDL code to set the  C_JTAG_CHAIN  to something other then 2

the JTAGloader.exe software does not detect the loader.

If I change the Microblaze MDM C_JTAG_CHAIN to something other than 2 it all works fine

but the microblaze environment is shared between many designs and is problematic to change.

Are there any plans to allow the C_JTAG_CHAIN variable to be set by the command line in the

JTAGLoader.exe software to allow it to function if the C_JTAG_CHAIN  to something other then 2?

[chapman]

There are plans and hopefully there will be a command line switch in the next release to override the ‘USER2’ default currently in the software.  The hardware change would remain a very simple manual edit of the ‘ROM_form’ template but of course that template would then carry that setting through to all assembled files with which it was used.   

[jeffrey_a_graham]

Thanks Ken.

For anyone who is interested here how to change the microblaze mdm module

to use JTAG_CHAIN USER3.

The Microblaze mdm module uses C_JTAG_CHAIN=2 (ie.USER2) by default.

Change this by editing the mdm section of the microblaze.mhs configuration file.

Add the line.

PARAMETER C_JTAG_CHAIN = 3

Jeff.

[chapman]

I am pleased to say that since the update of the KCPSM6 package in September 2012 (‘KCPSM6_Release5_30Sept12.zip’) it has been possible to specify an alternative BSCAN ‘USER’ port. Please see the ‘JTAG Loader and BSCAN Users’ section in the ‘READ_ME_FIRST.txt’ file for details.