The JTK1 is quite capable of compiling sofware directly on it, so nothing more than ssh access makes this fairly simple (especially if you install keys for access without passwords). I’m not sure of the state of gdb on Windows, but you can run gdbserver on a JTK1, or run gdb command line directly on a JTK1 via ssh. I don’t know if the nsignt eclipse edition runs directly on Windows or not (I have not looked), but it might (anyone know what platforms nsight runs on?).
You might be able to use Cygwin for cross compiles in combination with the Linaro tool chains…I’d expect it to get very complicated. An actual VM should work if you have enough disk space…your Windows install could host a Linux install. Cross-compiles via Cygwin would probably work with NTFS file system and not have any issues with NTFS.
The rest of this reply is if you are also wanting to flash, and not just cross compile…
The flash executable runs on Linux x86_64 only. During the flash, even if the executable ran on Windows x86_64, creating the image for transfer over to the Jetson itself requires the underlying file system type to be a native Linux type…other file systems do not have any knowledge of Linux permissions (and you’re not just creating files, you’re setting them up with permissions). Assuming Windows could mount and use Linux native file system types, you would also have to add a loopback mount ability (which Windows is not capable of).
So…you could use a VM, which definitely can succeed, and is your best bet for running JetPack, but realize you may have to “tune” the USB behavior (sometimes a VM’s USB causes mysterious failures, but this can be adjusted to work if you know VMs). Additionally expect that you cannot base it off of the NTFS partitions…you’ll have to have a dedicated ext3 or ext4 partition.