more question on usb direct

[virmaior]

Been hoping to switch to thingino for a while but many things to do. Today, a power cycle borked a wyze +wz_mini camera, moving it up on the priority list.

Goal is to get 5 wyze v3s and 1 atom v2 all running thingino with NCM usb direct. Things done so far:

1. installed thingino on previously borked camera.
2. confirmed working over wifi
3. looked at USB Direct Supported? #213
4. found a way to compile inside of a docker image on an x86 server to enable BR2_PACKAGE_USBNET=y and BR2_PACKAGE_USBNET_USB_DIRECT_NCM=y (had to set make on moderately low settings to not overload the server I've got).
5. attempted to update thingino using SD card method with this newly created firmware by renaming it to autoupdate-full.bin

After this,
(1) autoupdate-full.done file created suggesting it did reload.
(2) inaccessible both via usb direct and wifi
(3) creates a USB device (or maybe thingino always does?)

[47552.047631] usb 1-1.2.1.2: USB disconnect, device number 28
[48104.864898] usb 1-1.2.1.2: new high-speed USB device number 29 using xhci_hcd
[48104.996538] usb 1-1.2.1.2: New USB device found, idVendor=a108, idProduct=c309, bcdDevice= 1.00
[48104.996556] usb 1-1.2.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[48104.996570] usb 1-1.2.1.2: Product: \xc3\x83	 USB Boot Device
[48104.996584] usb 1-1.2.1.2: Manufacturer: Ingenic

(4) tried adding a run.sh (https://github.com/themactep/thingino-firmware/wiki/Automation#upgrade-from-binary-images-on-sd-card) with the following:

#!/bin/bash

usb-role -m device
ifconfig usb0 hw ether 00:15:de:ad:be:ef
ifconfig usb0 up
dhclient usb0

with no effect
(5) also tried reverting to the thingino-flasher firmware with seemingly no effect.

@clee604 or @gtxaspec any ideas?

[wltechblog]

If you're seeing a usb boot device, your cam is bricked and waiting for Cloner to revive it.

[virmaior]

is there any way to do that headless?
no monitor on the only linux machine in the house.

[virmaior]

so the script I initially used that you wrote can't resuscitate it?
anyway to run this on OSX or a raspberry pi (mkosi says "Don't know the armv7l architecture") when I start trying to put together (https://github.com/themactep/thingino-firmware/wiki/Ingenic-USB-Cloner) or alternately "cloner: 56: cloner: /home/pi/mkosi.extra/cloner-2.5.43-ubuntu_thingino/bin/32bit/cloner_32: Exec format error" if I try to run the script directly.

[wltechblog]

Cloner is a gui application that runs on Windows or Linux, x86 only. Its not a script and won't run on other architectures, and its utilization of USB prevents it from working in a virtual machine (so far). it's not an open source tool unfortunately so we are limited there.

[virmaior]

@wltechblog got cloner up and running.
to get it work had to reboot windows 8.1 in non-driver signing and then reboot in turn off anti-malware to run
important moment I forgot until rewatching your video was unplug and replug while cloner is open to get it started.

[clee604]

Recent builds don't need usb-role -m device script anymore for usb-ncm, it's been built into the firmware.

However for your custom compile, the values to put into your local.fragment are

BR2_PACKAGE_USBNET=y
BR2_PACKAGE_USBNET_USB_DIRECT_NCM_CLIENT=y

I believe it was renamed when NCM was split into host/client.

You probably don't need to use cloner (yet) if autoupdate-full.bin still works. Try compiling a new build with the above parameters, when ncm is working, your linux host lsusb should show
Bus 003 Device 05 ID 0525:a4a1 Netchip Technology, Inc. Linux-USB Ethernet Gadget

[gtxaspec]

fixed in latest sources.

[clee604]

@virmaior let me know if you need me to upload the newer build if you haven't got your build environment working

[virmaior]

@clee604 that would be great!

[clee604]

new build compiled and uploaded to https://github.com/clee604/thingino-firmware/releases/tag/ncm-builds

I haven't flashed any of my cameras with it yet but don't see any significant commits that would break the wyze v3 build

[virmaior]

one of the places I may have gone wrong is the flashing method.

1. I had initially installed stock thingino (seemed to be working)
2. then I built on a server (possibly point of error)
3. then I tried flashing via the web interface (failed in multiple ways -- viz., camera wifi subnet had no internet but the web interface update expected one)
4. Then I tried working around this from the command line
5. then I used the SD card method.
6. then camera was borked.
7. got help -- deborked camera, installed clee604 NCM build

How do you update your cameras?

[clee604]

there's a lot of breaking changes lately so either don't update if it's working fine... or if you do update, do full updates.

If the cameras are on no-internet network (i do this as well).. you have a few options to update.

1. Upload the firmware file to /tmp via SCP (i use winscp) on camera and then ssh in to run sysupgrade -x /tmp/firmwarename.bin
2. If your server machine has access to the camera network, you can push update by IP address in the user menu
3. use autoupdate-full.bin on sd card
4. Last option doesn't work well with NCM builds but for generic builds that you can just pull from github, you could turn on wifi temporarily to connect to internet ssid, update then disable

[virmaior]

you can set static in /etc/network/interfaces.d/usb0
@gtxaspec
put in a pull request to fix the behavior of S36cdcnet so that it actually uses values set in the env / /x/config-network.cgi

[gtxaspec]

merged.