System debugs multivendor multiprocessor designs

Tasking reckons its new Multicore debug system is the first-ever vendor-independent multicore debugging technology.

Tasking reckons its new Multicore debug system is the first-ever vendor-independent multicore debugging technology.

Through this Multicore debug system (MDS), Tasking claims to have solved the dilemma of developers designing next-generation communications and network technology using multiple processors or integrating multiple IP cores who have been unable to debug or simulate the interactive behaviour of such multiprocessor applications.

Using software logic that mediates between the debuggers for each processor, the MDS synchronises the debuggers' behaviour in order to accurately reflect how the processors interact with each other, while providing a platform that facilitates complete simulation of the multicore behaviour.

This breakthrough technology has only been possible thanks to Tasking's adherence to open-interface standards and its commitment to the vendor-independent support.

"As the first company to provide a heterogeneous debugging solution, Tasking once again confirms its commitment to excellence and its ability to create innovative solutions to complex development problems", attests Scott Taitel, CEO of Protel's Tasking Group.

"Thanks to Tasking's vendor independence and delivery of an open interface, we are able to offer current and new semiconductor partners a multicore solution that can be targeted to any processors that are expected to be used in multicore applications.

With this technology, Tasking will extend its reach in the embedded communications sector where wireless and networking developers are currently struggling to solve complex interactive relationships between multiple processing cores".

To initiate an environment where multiple debugger clients can communicate with multiple targets, Tasking extends the generic interface used by Tasking's CrossView Pro debugger to enable target systems to interact with both proprietary and open-standard platforms.

Within this open framework, the object-oriented nature of Tasking's MDS creates an environment in which discrete microprocessors and processing cores are all treated as "processing units".

The configurable debug topology defines how the processing units interact with each other, orchestrating the relational dynamic of the multicore system that tracks how the messaging and logic is passed between the various cores.

Using run-control logic, Tasking manages the synchronous operation of multiple executing elements in the target environment, enabling the attached debuggers and targets to behave independently or as a unit, as well as paving the way for a simulated environment that mirrors the independent and coordinated behaviour of the processing units.

With this level of sophisticated control, for the first time developers can rigorously test and debug the multiprocessor solutions underlying many of the next-generation communications designs.

Because the MDS brings together mature, single-core debugging solutions, developers can exploit the advanced debugging capabilities of Tasking's CrossView Pro debugger with each processor working independently or in conjunction with the other processors in the core.

To pinpoint specific problem areas, developers can monitor memory use, display register values, and trace program performance of each processor or of the system as a whole.

Breakpoints can be set that allow other processors to continue executing, so that developers can drill down into the complex interactive behavior of an SoC solution.

With these debug capabilities, Tasking rounds out the resources needed to address the complexities of next-generation embedded communications design.

Back to top