Priyadrasta-2111CS10 opened a new issue, #13237:
URL: https://github.com/apache/tvm/issues/13237

   
   ### Expected behavior
   The output should be something like this.The picture shown below is showing 
the result while the RPC tracker is set on Raspberry PI and the RPC server is 
set on local host which in fact should be opposite.
   
   
![image](https://user-images.githubusercontent.com/92008353/199019051-7cbd64c2-6d5f-4ff4-94a8-e192b5bdca2a.png)
   
   ### Actual behavior
   The RPC tracker couldn't track down the connected Raspberry PI as shown 
below.
   
   
![image](https://user-images.githubusercontent.com/92008353/199018414-c27ac580-2213-4794-ae29-9df0c3135c84.png)
   
   
   ### Environment
   
   **Operating System for host :** Linux 22.04 LTS
   **Operating System for target :** Raspbian 64 bit OS
   
   
   ### Steps to reproduce
   
   1. Start the RPC tracker on the host system by the command `python -m 
tvm.exec.rpc_tracker --host=0.0.0.0 --port=9190`
   
   2. Start the RPC server in the target devices  by the command : `python -m 
tvm.exec.rpc_server --tracker=[HOST_IP]:9190 --key=[KEY] `.In the case of 
HOST_IP and KEY use your host system IP address and key for target device.
   
   3.Track the connected devices to the current RPC tracker on your host device 
: `python -m tvm.exec.query_rpc_tracker --host=0.0.0.0 --port=9190`
   
   
   
   ### Triage
   
   Please refer to the list of label tags 
[here](https://github.com/apache/tvm/wiki/Issue-Triage-Labels) to find the 
relevant tags and add them below in a bullet format (example below).
   
   * core:rpc
   


-- 
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