Wednesday, September 26, 2012

Nexus JTAG Access - Business - Small Business

Nexus gives a consistent interface for on-silicon instrumentation along with debug tools providing various expanded capabilities forsystem debug. Most well known are generally higher-performance auxiliary interfaces to compliment real-time and data-transferintensiveNexus messages may perhaps be examine from as well as written through this IEEE 1149.1 JTAG port. Message is currently writing tend to be earned by a good outer IEEE 1149.1controller and are also input towards an source arrest concept sign up (IPMR). The IPMR receives their TCODEs and packets by way of multiplepasses over the SELECT-DR_SCAN.The IEEE 1149.1 protocol does not enable court emails for being caused from an onhip interface. Therefore, a great expenditure court principles enroll (OPMR) can be available.

The JTAG interface must be used with Nexus-specific methods of put into action different instructional classes regarding expertise this kind of seeing that studying in addition to writing Nexus subscribess andmessages, as well as letting Nexus trace output being embedded into JTAG messages. Output court message flows are messages thatare produced because of the target processor and so are read from your OPMR. These unsolicited mail messages may comprise variable-lengthpackets of data. Two solutions may be used intended for deciding when an result arrest message.

At their quickest level, Nexus works iwth with JTAG although recognizes that this restriction within JTAG bandwidth are not genuine to the debug conditions for complex or multicore environments, and provides methods of both equally input as well as productivity auxiliary parallel interfaces to get high-speed files transfers. The Nexus specification defines a vendor-neutral IO indicate interface and connection standard protocol this supportsparallel debug along with instrumentation support. The Nexus interface defines a compact pair of command signs as well as AUX records ports(shown throughout Table 11.5) which are implemented jointly with JTAG or maybe as a new self-contained port. The further info pins providedby the particular AUX interfaces are generally scalable intended for corresponding the actual debug necessity and make it possible for higher read/write throughput betweenthe target plus debug and analysis gear in comparison to JTAG Figs. 11.1 and 11.2.

The width on the productivity information register is going to be vendor-defined, where the particular vendor may boost the particular sign up width according to the sizeof the particular packets transmitted.The AUX interfaces are generally unidirectional (either data within or maybe files out), using each AUX port obtaining some clock. The data out pins of the AUX interface can be used intended for trace, as well as information within style is normally employed regarding configuration or even calibrationof an IC. AUX records around as well as out and about plug-ins might become operated concurrently. Nexus in addition specifiesinterface procedures in Nexus may beused pertaining to equally configuration and also handle in the on-silicon instrumentation and for embedding Nexus protocol along with data straight into aJTAGmessage. Both AUX and JTAG interfaces will be restricted by FSM-based controllers, making it possible for a number of exchange operations.There will be a pa ir of FSMs intended for receiving and also transmitting emails via the auxiliary pins when using the MSEI and also MSEO pin functions. A the least a single plus a highest possible with a pair of MSEI pins shall produce the actual standard protocol to the embedded processor acquiring messages, plus a minimum of one particular plus a highest possible regarding a pair of MSEO pins would produce your protocol for any embedded model transmitting messages.The Nexus regular defines a strong extensible auxiliary convey which will both possibly be used with the IEEE 1149.1(JTAG) opening or like a stand-alonedevelopment port. The Nexus common defines this auxiliary pin functions, exchange protocols, plus standard developmentfeaturesto assist both 1149.1 and AUX usage.

The auxiliary interface providesa wider, higher-bandwidth information airport transfer gateway that will state both AUX enter plus result ports. Auxiliary outports are utilized primarily to make additional pins inside convey regarding greater throughput regarding know output.For a full-duplex AUX by using IEEE 1149.1 pins, at least a pair of auxiliary pins are essential intended for compliance [message records out there along with concept start/end out], assumingNexus implementations may have 1 or 2 messaging start/end out there pins, based on complexness belonging to the insight as well as outputstate machines.

A two-bit messagingpin will allow back-to-back records transfers, speeding distribution regarding memory space information as well as trace information.The similar series can be taken taking a couple MSEI/MSEO pins, but when browsing with a pair of MSEI/MSEO pins, it is doable for just two sequences to be able to happen onthe identical clock. MSEI/MSEO can be employed to sign the finale associated with variable-length packets instead of device-specific or even fixed-length packets.MSEI/MSEO tend to be tried around the climbing borders involving MCKI/MCKO.Figure 11.4 demonstrates the particular finite-state machines diagram for one-pin MSEI/MSEO transfers.

When implementing only 1 MSEI/MSEO pin, this end-message state does possibly not contain good data within the MDI/MDO pins.Also, it's not necessarily possibleto have two consecutivend-packet messages. This means that your minimal small fortune sizing for a variable-length small fortune is usually not one but two moments thenumber involving MDI/MDO pins. This means that a wrong end-of-message state is not entered through sending a couple consecutive 1s on theMSEI/MSEO pin before the exact conclusion of the message.Systems using course 2, 3, in addition to 4 functions primarily utilize AUX interfaces, Rulesof sneaking in a new Nexus supply inside a good AUX opening tend to be consistent by using many other parallel.

Nexus provides some sort of standardised program with regard to on-silicon instrumentation and also debug gear delivering a variety of extended characteristics forsystem debug. Most famous will be higher-performance auxiliary interfaces with supporting real-time plus data-transferintensiveNexus messages may be understand through and also authored by using the IEEE 1149.1 JTAG port. Message is currently writing will be earned by an external IEEE 1149.1controller and are feedback in to a strong input arrest communication register (IPMR). The IPMR makes it has the TCODEs and packets via multiplepasses through the SELECT-DR_SCAN.The IEEE 1149.1 method will not enable arrest communications to be initiated from an onhip interface. Therefore, an end product criminal court communication register (OPMR) will be available.

The JTAG dock is used in Nexus-specific methods to put into practice numerous lessons involving services like reading in addition to writing Nexus registers andmessages, in addition to allowing for Nexus trace end result for being embedded into JTAG messages. Output public message reads tend to be mail messages thatare made because of the targeted processor chip and so are study from the OPMR. These unsolicited messages might comprise variable-lengthpackets of data. Two solutions can be utilized for identifying whenever a strong output criminal court message.

At its quickest level, Nexus works with using JTAG nevertheless recognizes the fact that constraints within JTAG bandwidth may not be realistic to get the particular debug requirements for difficult or even multicore environments, and also supplies ways for both insight in addition to output auxiliary parallel interfaces regarding high-speed data transfers. The Nexus specification defines a vendor-neutral IO transmission software in addition to connection method that supportsparallel debug in addition to instrumentation support. The Nexus interface defines a smaller list of manipulate signals in addition to AUX files ports(shown around Table 11.5) which can be integrated together with JTAG or as being a self-contained port. The extra data pins providedby your AUX interfaces are usually scalable with regard to matching the debug prerequisite and also allow for more achieable read/write throughput betweenthe target as well as debug and also research tools when compared with JTAG Figs. 11.1 as well as 11.2.

The thickness with the output meaning register will probably be vendor-defined, where the merchant may possibly optimise your register width according to the actual sizeof the particular packets transmitted.The AUX interfaces will be unidirectional (either data in or data out), along with each one AUX vent acquiring its private clock. The info out and about pins of the AUX software can be made use of to get trace, plus the records around manner is normally made use of for configuration or maybe calibrationof an IC. AUX information with in addition to out jacks could be managed concurrently. Nexus furthermore specifiesinterface experditions throughout Nexus may possibly beused for each configuration in addition to manipulate on the on-silicon instrumentation and also to get embedding Nexus process and data directly into aJTAGmessage. Both AUX and JTAG interfaces tend to be manipulated by simply FSM-based controllers, permitting a number of transfer operations.There are gene rally two FSMs for getting as well as sending messages via the auxiliary pins with the MSEI plus MSEO pin number functions. A minimum of one along with a utmost regarding not one but two MSEI pins should certainly produce the process with the embedded processor getting messages, and also a new the least one and also a utmost with a couple of MSEO pins would supply the actual process with regard to the actual embedded model transmitting messages.The Nexus ordinary defines a strong extensible auxiliary interface that could sometimes often be combined with the particular IEEE 1149.1(JTAG) interface or perhaps for a stand-alonedevelopment port. The Nexus standard defines your auxiliary pin functions, shift protocols, as well as ordinary developmentfeaturesto assist together 1149.1 as well as AUX usage.

The auxiliary port providesa wider, higher-bandwidth data channel which enable it to determine both AUX enter in addition to output ports. Auxiliary outports are employed primarily to supply more pins while in the opening intended for greater throughput to get find output.For a full-duplex AUX along with IEEE 1149.1 pins, at the very least two auxiliary pins usually are required with regard to compliance [message data out there plus message start/end out], assumingNexus implementations often have several messaging start/end out pins, according to difficulty in the insight plus outputstate machines.

A two-bit messagingpin permits back-to-back data transfers, boosting shipping associated with memory records or even know information.The exact collection is followed when using one or maybe a pair of MSEI/MSEO pins, but taking two MSEI/MSEO pins, it really is feasible for two sequences for you to occur onthe exact clock. MSEI/MSEO must be used that will mark the final involving variable-length packets rather than device-specific or even fixed-length packets.MSEI/MSEO will be sampled to the increasing border associated with MCKI/MCKO.Figure 11.4 shows the finite-state appliance diagram regarding one-pin MSEI/MSEO transfers.

When using merely a single MSEI/MSEO pin, the particular end-message condition will not consist of valid files within the MDI/MDO pins.Also, it's not at all possibleto have a couple consecutivend-packet messages. This implies that will the lowest packet dimension for the variable-length packet is twofold thenumber regarding MDI/MDO pins. This helps to ensure that a new false end-of-message condition isn't entered by transmitting two consecutive 1s on theMSEI/MSEO pin number prior to the actual end from the message.Systems with category 2, 3, in addition to some capabilities chiefly make use of the AUX interfaces, Rulesof embedding a Nexus supply within a strong AUX convey are constant together with a number of other parallel.





No comments:

Post a Comment