Using CCS to verify TAP connection on LS1046ARD

Daves_Garage — Tue, 14 Jun 2022 21:03:56 GMT

Setting up TAP device through telnet or TeraTerm via serial, get the following

####
##########
########## .... Freescale Semiconductor Inc.
#### .......... Copyright (c) 2015
.......... #### All Rights Reserved
.... ##########
########## Codewarrior TAP Firmware
.... #### Boot Loader Version 1.0.1
.......... built Mon Aug 26 18:55:20 UTC 2013
.......... #### OS Version 1.0.4
#### .... ########## built Thu Apr 23 22:28:59 UTC 2015
########## ##########
########## .... #### Main Board: CodeWarrior TAP (3.3V)
#### .......... Probe Tip: Cortex-10
..........
#### ....
########## Note: This product uses open-source
########## components. See "help license"
#### for details.

Network configuration is static:FSL0724BF
Using static IP address 192.168.0.15

But using CCS to verify connection, I get this:

0: CC not present
There are no command converters configured
Clients allowed from all hosts
No clients denied
(bin) 10 % findcc cwtaps -verbose
no devices found
{amphisbaena} FSL0724BF (169.254.57.3:1087):
Main Board = CodeWarrior TAP (3.3V) {8,8}
Probe Tip = Cortex-10 {2}
Firmware = Boot Loader {1.0.1}
Firmware = Operating System {1.0.4}
{amphisbaena} FSL0724BF (169.254.57.3:1087):
Main Board = CodeWarrior TAP (3.3V) {8,8}
Probe Tip = Cortex-10 {2}
Firmware = Boot Loader {1.0.1}
Firmware = Operating System {1.0.4}
1

Trying a second time, I get this:

(bin) 11 % findcc cwtaps -verbose
no devices found
0
(bin) 11 %

Can somebody tell me what's going on, and why this happens? I believe it is affecting functionality within my CodeWarrior installation.

By the way, I can ping the TAP device from a command line as well as from within CCS:

(bin) 11 % ping 192.168.0.15

Pinging 192.168.0.15 with 32 bytes of data:
Reply from 192.168.0.15: bytes=32 time=1ms TTL=64
Reply from 192.168.0.15: bytes=32 time<1ms TTL=64
Reply from 192.168.0.15: bytes=32 time<1ms TTL=64
Reply from 192.168.0.15: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
(bin) 12 %

Re: Using CCS to verify TAP connection on LS1046ARD

Daves_Garage — Tue, 14 Jun 2022 22:00:03 GMT

By the way, from the interface to TAP, I have this:

core> netparam
ethernet_address = 00:04:9F:07:24:BF
bootconfig = static:FSL0724BF
static_ip_address = 192.168.0.15
static_dns_server = <none>
static_hosts = hostname ip address
--------------- ---------------
buntu
buntu
static_routes = <none>
core>

I'd also be interested in knowing how to remove the unwanted hostnames that show up here. They still remain after reloading firmware.

Re: Using CCS to verify TAP connection on LS1046ARD

Daves_Garage — Wed, 06 Jul 2022 15:56:03 GMT

This issue turned out to be a faulty TAP device. Replacing the module eliminated the issue.

Other NXP ProductsのトピックRe: Using CCS to verify TAP connection on LS1046ARD

Using CCS to verify TAP connection on LS1046ARD

Re: Using CCS to verify TAP connection on LS1046ARD

Re: Using CCS to verify TAP connection on LS1046ARD