CodeWarrior TAP combined with a host debugger provide control and visibility into your target embedded system through a debugging process.
Main tasks to test a Reference Design Board with are:
For all of them and every activity involving real hardware, a link is needed nevertheless is a very straightforward process that is going to be crawled in this document.
Windows® OS: Intel® Pentium® 4 processor, 2 GHz or faster, Intel® Xeon™, Intel® Core™, AMD Athlon™ 64, AMD Opteron™, or later
Linux® OS: 1.8 GHz Intel® Pentium® class processor (or better). 64-bit host OS required.
Microsoft® Windows 7 64-bit
Microsoft® Windows 10 64-bit
RHEL 7.8, 8.2 64-bit
CentOS 7.8, 8.2 64-bit
Ubuntu 16.04 64-bit
Ubuntu 18.04 64-bit
Ubuntu 20.04 64-bit
Fedora 31 64-bit
Mint 19.3 64-bit
At least 2 GB of RAM
At least 3 GB of free disk space
Connect debugger and target's end to each other, while both of them are powered off.
Note that CPU JTAG silkscreen label is in the red box, but also may be visible the 1 label.
If communication is directly to host, considerate that you'll be joined into a private network and you will not have internet access.
Predefined connections are processor oriented and have a default configuration, you cannot and should not override this values, e.g., MAC field for TAP probe, you should duplicate and then customize it.
Click on the reference board that you have, then duplicate, name new target and save.
Settings are initialized based on the duplicated board, it's recommended to just update MAC. Click on look for probes, select the one that matches your MAC and save.
Serial number field is updated and you are notified of unsaved changes, is the asterisk at the left of your duplicate name, save (ctrl + s) and you may close the connection data is done now.
I created a new project to simply read RCW inside NOR Flash Bank 0 of LS1043ARDB following the below process.
Click on recheck connection button (green play button) and connection status should change from no-link (connection button right side) to connection working.
Go to Target Connections view and click diagnose connection, Connection Diagnostics view should be popped up and log different tests to ensure that there is a target connection and SOC modules are accessible.
At this point, the connection is made and is already tested, but in this document, RCW will also be dumped into our project just to work ourselves with the connection already made.
Under Component Inspector view go to Import tab, select Import From Target and click Read from target.
Results are display in text box as:
RCWSR registers were successfully read from the target and imported!
RCWSR1:0x08100010
RCWSR2:0x0A000000
RCWSR3:0x00000000
RCWSR4:0x00000000
RCWSR5:0x14550002
RCWSR6:0x80004012
RCWSR7:0xE0025000
RCWSR8:0xC1002000
RCWSR9:0x00000000
RCWSR10:0x00000000
RCWSR11:0x00000000
RCWSR12:0x00038800
RCWSR13:0x00000000
RCWSR14:0x00001101
RCWSR15:0x00000096
RCWSR16:0x00000001
That should save a connection to a CWTAP to reuse with that same MAC intended to a any RDB that features the selected processor. Later on you can recover LS Series processors, flash, configure or validate a board. Please ask any question you may have.
Best regards, Joseph