Hacking Build your own dongle (Research and development thread)

[smf]

The A5V11 hardware is like, 7$.

Contains a battery already, comes in an injection molded housing already, and is completely solderless. Just needs a custom firmware flashed onto it, and a pigtail cable.

I can't find any aliexpress listings that say they come with a battery. With so many sellers and so many brand names, it's impossible to know what to buy as nobody posts a link.

 

[OllieD]

@
Here is a bin to flash to this device that will allow it to run the fusee-nano binaries @OllieD There is no root pw on this OpenWrt Linux instance

Doesn't work
Even built my own image with luci to be sure.
Fusee-nano throws an error, something like unable to open/find/connect to the USB device.

Don't have the specific error as it's been a few hours since I tested it.

In addition to this error it seems to break rcm from accepting any payloads until the device is reset.
USB descriptor fails etc.

 

[xeswitched]

Thx for share, it's great. Mybe next step is to put trinket m0 inside the console~

 

[james12]

what do you think about this board, can we use it?

WEMOS D1 Mini Pro 16M Bytes External Antenna Connector NodeMCU Based ESP8266 ESP-8266EX CP2104 WIFI Development Board Micro USB
aliexpress(dot)com/QriU7Ffy?

 

[M-O-B]

thanks for posting that, it has saved me a lot of time trying to figure it out, now I give this a try once the tools get delivered to open the switch.

have sorted some payloads out for this method.

if anyone wants them.

 

[xeswitched]

thanks for posting that, it has saved me a lot of time trying to figure it out, now I give this a try once the tools get delivered to open the switch.

have sorted some payloads out for this method.

if anyone wants them.

So you must use the github code for the trinket m0. The code here works in theory however the github is programmed to use the RCM strap as well as some nifty modification to the lights on the chip to show status and pass/fails

 

[Kelly525]

Doesn't work
Even built my own image with luci to be sure.
Fusee-nano throws an error, something like unable to open/find/connect to the USB device.

Don't have the specific error as it's been a few hours since I tested it.

In addition to this error it seems to break rcm from accepting any payloads until the device is reset.
USB descriptor fails etc.

I am using this for my switch now with the WD03, there is no payload on the bin, just the image to flash that has the USB patch in it. I can get you my scripts and payload for SX OS to install if that would help.

 

[metaljay]

thanks for posting that, it has saved me a lot of time trying to figure it out, now I give this a try once the tools get delivered to open the switch.

have sorted some payloads out for this method.

if anyone wants them.

this is incredible? Do you have any material/ guide we can follow?

 

[8BitWonder]

this is incredible? Do you have any material/ guide we can follow?

There are installation instructions on github: https://github.com/Quantum-cross/sam-fusee-launcher-internal/blob/master/INSTALL.md

 

[M-O-B]

So you must use the github code for the trinket m0. The code here works in theory however the github is programmed to use the RCM strap as well as some nifty modification to the lights on the chip to show status and pass/fails

yeah I have the trinket files already created, I just tested the sxos one I created and it works fine.

how I tested was plug a usb lead into the trinket with only the data wires connected, the external power to bat pad and gnd pad,I didn't have pads 3 and 4 connected.

pressed and held volume up button and power button, released then I touched one off the pads that need to be connected to mobo and sx os booted up.

hopefully my switch opening kit turns up tomorrow so I can do the install properly.

i copy his guide but colour coded the points for ease of use for myself.

 

[Rainbowfied Pokemaster]

That's OK

Found out that openwrt (and thus likely lede) defaults to 192.168.1.X network not 0.X network. So, if you ever get an ethernet cable going, give that a shot.

Ok this is what I get:

usb 2-1: new high speed USB device using rt3xxx-ehci and address 2
usb 2-1: device descriptor read/all, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 3
usb 2-1: device not accepting address 3, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 4
usb 2-1: device not accepting address 4, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 5
usb 2-1: device not accepting address 5, error -71

 

[Wierd_w]

Ok this is what I get:

usb 2-1: new high speed USB device using rt3xxx-ehci and address 2
usb 2-1: device descriptor read/all, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 3
usb 2-1: device not accepting address 3, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 4
usb 2-1: device not accepting address 4, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 5
usb 2-1: device not accepting address 5, error -71

As best I can evaluate that error number, it looks like the root hub is not getting a response from the device in what it considers to be a timely manner, then throwing a protocol error (-71)

Things to check:

1) NX really is in RCM mode?
2) Cable is good? (tested with other devices)

 

[Rainbowfied Pokemaster]

As best I can evaluate that error number, it looks like the root hub is not getting a response from the device in what it considers to be a timely manner, then throwing a protocol error (-71)

Things to check:

1) NX really is in RCM mode?
2) Cable is good? (tested with other devices)

Yes to both, I use the cable with my switch and computer all the time. I don't have another usb-c device so I haven't been able to test it on other devices, but it's been reliable.

 

[Wierd_w]

Yes to both, I use the cable with my switch and computer all the time. I don't have another usb-c device so I haven't been able to test it on other devices, but it's been reliable.

Plug some other random device into the port, and check dmesg. See if say-- a flash drive or a keyboard or something is able to register with the root hub.

 

[Rainbowfied Pokemaster]

I get the same thing:

usb 2-1: new high speed USB device using rt3xxx-ehci and address 2
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 3
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 4
usb 2-1: device not accepting address 4, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 5
usb 2-1: device not accepting address 5, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 6
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 7
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 8
usb 2-1: device not accepting address 8, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 9
usb 2-1: device not accepting address 9, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 10
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 11
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 12
usb 2-1: device not accepting address 12, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 13
usb 2-1: device not accepting address 13, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 14
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 15
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 16
usb 2-1: device not accepting address 16, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 17
usb 2-1: device not accepting address 17, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 18
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 19
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 20
usb 2-1: device not accepting address 20, error -71
usb 2-1: new high speed USB device using rt3xxx-ehci and address 21

more or less

 

[Wierd_w]

I get the same thing:

<snip>

more or less

Ok, the device is either loading the wrong driver (which is unlikely?) for that usb chipset, or the chip is not in a sane state.

Power off the device, and remove all source of power, then wait a few minutes. Power it back up, and test with the mundane hardware you just tested against.

 

[carney]

My device get this infomation,but NS is not working.

Ok, the device is either loading the wrong driver (which is unlikely?) for that usb chipset, or the chip is not in a sane state.

Power off the device, and remove all source of power, then wait a few minutes. Power it back up, and test with the mundane hardware you just tested against.

[ 1510.766503] usb 1-1: new high-speed USB device number 2 using ehci-platform
[ 1510.917316] usb 1-1: New USB device found, idVendor=0955, idProduct=7321
[ 1510.922584] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1510.929752] usb 1-1: Product: APX
[ 1510.932994] usb 1-1: Manufacturer: NVIDIA Corp.
[ 1587.643307] usb 1-1: USB disconnect, device number 2

 

[Wierd_w]

My device get this infomation,but NS is not working.

[ 1510.766503] usb 1-1: new high-speed USB device number 2 using ehci-platform
[ 1510.917316] usb 1-1: New USB device found, idVendor=0955, idProduct=7321
[ 1510.922584] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1510.929752] usb 1-1: Product: APX
[ 1510.932994] usb 1-1: Manufacturer: NVIDIA Corp.
[ 1587.643307] usb 1-1: USB disconnect, device number 2

This is a question for Retr0id. I suspect that your NX has a slightly different ID number, and that is throwing it off.

 

[OllieD]

I am using this for my switch now with the WD03, there is no payload on the bin, just the image to flash that has the USB patch in it. I can get you my scripts and payload for SX OS to install if that would help.

Yeah that would be great.
I tried your bin with the fusee-nano ipkg generated from when i built my own lede image with luci and got the same error on both.

 

[M-O-B]

just prep my trinket for installing into the switch, haven't removed resistor yet as I forgot about that, waiting on the screwdriver set now to be delivered.

 

[Hodorian]

just prep my trinket for installing into the switch, haven't removed resistor yet as I forgot about that, waiting on the screwdriver set now to be delivered.

View attachment 133509 View attachment 133510

Do you know why you need to remove the resistor? Is it to deactivate the power led?