alanmacd opened a new issue #10206:
URL: https://github.com/apache/tvm/issues/10206


   There are two versions of the nRF5340 development kit, 1.0.0 and 2.0.0. The 
1.0.0 DK exposes three COM ports, where COM2 is used to communicate with the 
device while running tests. The 2.0.0 DK only has two COM ports as can be seen 
here:
   ```
   $ nrfjprog --com
   1050063518    /dev/ttyACM0    VCOM0
   1050063518    /dev/ttyACM1    VCOM1
   ```
   [microtvm_api_server.py always uses 
VCOM2](https://github.com/apache/tvm/blob/3b2780a4141b5654439c43dfc7c1409f9cb1858c/apps/microtvm/zephyr/template_project/microtvm_api_server.py#L628)
 which doesn't exist on the 2.0.0 DK.
   
   To accommodate this, the USB product ID (PID) can be used to differentiate 
between the 1.0.0 and 2.0.0 DKs. The PID for 1.0.0 is 1055, while the PID for 
the 2.0.0 DK is reported as 1051 via lsusb:
   ```
   $ lsusb
   Bus 005 Device 006: ID 1366:1051 SEGGER J-Link
   ```
   
   Here are more details from Nordic Semiconductor's site:
   
   [nRF5340 DK v2.0.0 COM 
ports](https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html#nrf5340-dk-v2-0-0-com-ports)
   When connected to a computer, the nRF5340 DK v2.0.0 emulates two virtual COM 
ports. In the default configuration, they are set up as follows:
   - The first COM port outputs the log from the network core (if available).
   - The second COM port outputs the log from the application core.
   
   [nRF5340 DK v1.0.0 COM 
ports](https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html#nrf5340-dk-v1-0-0-com-ports)
   When connected to a computer, the nRF5340 DK v1.0.0 emulates three virtual 
COM ports. In the default configuration, they are set up as follows:
   - The first COM port outputs the log from the network core (if available).
   - The second (middle) COM port is routed to the P24 connector of the nRF5340 
DK.
   - The third (last) COM port outputs the log from the application core.
   
   ### Expected behavior
   Tests pass while successfully connection to device via VCOM2
   
   ### Actual behavior
   Tests fail due to inability to connect to device as VCOM2 does not exits.
   
   ### Environment
   Linux Ubuntu 20.04 with nRF5340 v2.0.0 development kit
   
   ### Steps to reproduce
   `pytest test_zephyr.py --zephyr-board=nrf5340dk_nrf5340_cpuapp`
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to