Sir,I want to create api which communicate between NVidia Jetson Nano and ID TECH 3300 OEM for transaction purpose.I want NVidia Jetson Nano take our transaction details and through my api send to ID TECH 3300 OEM terminal.How I will go forward to create a api by using WCF in .Net and which protocol support by NVidia Jetson Nano devoce. How can i download SDK for windows.
Moving to the Jetson Nano topic, from the Nsight Systems topic
I know nothing about the specific device, but see some information here which provides some ideas:
The topic isn’t entirely clear, but I am guessing you want to run this device over USB on a Nano (the device-to-Nano being USB…the Nano-to-Windows is unimportant at this stage). And then some result of this gets communicated to another computer running Windows. You might want to clarify if this is correct or not.
I see in one location this shows Android support, and another a C interface on Linux. This provides a lot of hope, but some questions still must be answered. Some USB devices are a standard class and use more or less generic drivers. A device such as this probably uses custom drivers. Information on the driver is a starting point for any answers. The company producing the product could answer whether this is a custom driver or a simply an API accessing a standard USB class. The former case is the more difficult, the latter case is easy to to work with.
If the device is a generic standard class, then there are lots of examples and not much difficulty. In the case of a custom driver, then the driver must be compiled for this kernel version on 64-bit ARM architecture (arm64/aarch64/ARMv8-a).
Aside from the manufacturer providing information, if you run “dmesg --follow”, and then insert the USB connector, some output will become visible as a result of this. You could post the output here. As the USB hot plug layer detects the device a driver might take ownership if one already exists, and the dmesg would tell you whether or not this is the case.
Another tools is that if you run “lsusb”, then you will see a list of devices. If you can identify the specific device, then you can limit lsusb to provide information about the specific device, and to go into more detail. You will have a different device ID, but as an example an ID will look something like “ID 0955:7020” when you run lsusb. If you were to run this command (edited for your ID), then you could post a log of what shows up:
sudo lsusb -d 0955:7020 -vvv
(note that in the upper right of your forum post there is a “code” icon, “</>”, and if you highlight your log and click on this, then the format of the highlighted content will preserve whitespace and display better)
If it turns out that there is a custom driver (and I suspect this will be the case), then once the driver is in place the API they mention for Linux would work. It is quite possible that the manufacturer will not release the driver in source format, but if they do, then you simply compile this and copy a file to the Nano. If the manufacturer does not provide this in source form, then they must provide a binary driver for the 4.x Linux kernels on the “arm64/aarch64/ARMv8-a” architecture. If this is not possible, then you won’t be able to continue development. If this is possible, then there are a lot of options available for how to integrate with Windows.