Did you follow the instructions in the efus Startinterface documentation?
Chapter 7 "Programming NBoot" describes the necessary steps.
Is a new HID device shown in the device manager when you connect the USB cable?
nbootimx6_asa9_u1 is a special variant. If in doubt, don't use it. If you use an armStoneA9 board and F&S told you to use it, then you may need it.
Just use nbootimx6 for all other cases.
You can use the SX8674. It is has the same pinout and functionality.
Installing a new nboot should not affect U-Boot and OS.
From the messages I can see that the nboot is around 3 years old.
You have to change the nboot in order to get decent functionality.
Please give the version of the installed nboot so I can give you the instructions for updating the nboot.
This seems to be a very old nboot version prior to V21. You have to update to a current nboot (V32 is current).
Please give the full serial output so I can see which nboot you are using.
Then I can give you some instructions for the update process.
The ASend option in HTrem seems a little bit slow (repetition rate of 100ms).
Are you using a USB-Serial dongle? Then there may be additional delays from the dongle.
There is only a short period of time where the serial port is read, this period was longer for older boards.
You have to use a different terminal program with a faster key repetition rate.
SD-Card is not supported in i.MX6 nboot
Have you tried a different baudrate?
There are two different nboots, one uses 38400, the other uses 115200.
the application "EVG.Embedded.WinCE.UI.Lamphouse.exe" is throwing a "Data Abort" exception, this means an access to a memory region not allocated by the application occurs. Please check, if all pointers are valid.
This error should be removed first, then check if the error still occurs.
NetDCUUSBLoader and DCUTermi are both working with Windows10.
Does the "Connected at high-speed" message appear to indicate the USB connection?
Does the "Waiting for EBoot, U-Boot, NBoot, M4 Image..." message appear after pressing 'd'` for serial download?
These pins are connected to LEDs and can't be read by the CPU.
Does the module use the PCIe interface or the USB interface? The miniPCIe connector has both signals.
The NEO-7 module from u-blox used on the EWM-G108H has UART/USB/SPI/I2C interfaces so I think USB is used.
For PCIe a separate chip has to be used to convert it to one of the interfaces of the NEO-7, but I don't think this is used.
Also on the pictures of the EWM-G108H you can see that the PCIe signals are not connected.
So you have to look for an USB device.
Is the 1.5V voltage used by the module? We found out that there are some armStoneA9r2 from the first production batch where the voltage regulator is not working.
See https://de.wikipedia.org/wiki/PCI_Express_Mini_Card for the connector pinout. If there is no voltage on the 1.5V pins you can send us the boards for repair with RMA.
efusA9 has only one camera port (MIPI-CSI or parallel as mounting option).
For MIPI-CSI you need external logic to multiplex the two camera ports to one port and use virtual channels.
You can try this solution, but we did not test it and there is no guarantee that it works.
1A is the theoretical maximum current when all components are working at maximum power.
This is unlikely to happen, but is an indication for the upper margin.
The typical values are the currents that are needed for static operation with no load or a cpu benchmark running, but these are average values and there can be much higher currents.
The most important value is the startup current. You must make sure that the voltage has a fast rise time and that there are no voltage drops during startup.
Make sure that your voltage regulator can meet these requirement.
The armStoneA9r2 has 4 USB Host ports.
Two are on the Dual USB A connector, one is on a pin header behind the USB connector and one on the miniPCIe connector.
The maximum current ist 500mA.
If you need more then you can use an external power supply and use VLCD to switch the voltage.
You need to add a pull-down resistor if you use VLCD as a switching signal.
The network connection is up and running and sending broadcasts.
You are using 192.168.0.101 as static IP address for the board, so you have to make sure that your PC is in the same network.
Please check the Windows firewall settings, if EShell is not blocked.
You can change the network parameters with 'N' in EBoot.
Disconnect pin 7 on the JTAG connector.
The DStream manual marks this pin as NC but it is used on the DStream.
On the efus this pin is also used as a reset input.
If you can connect in nboot then debugging works.
You also have to make sure that the security functions of the i.MX6 are disabled, because they can also prevent debugging.