196 lines
8.5 KiB
Markdown
196 lines
8.5 KiB
Markdown
ha Willkommen im Wiki.
|
||
|
||
Hier wird ein Sammelsurium angelegt, welches Snippets für alles enthält, was mir über den Weg läuft.
|
||
#### TS100 soldering iron
|
||
https://github.com/Ralim/IronOS
|
||
|
||
Hold B
|
||
v2.11.372F8E3
|
||
29-08-20
|
||
Hold A
|
||
DFU:3.45
|
||
New drive available: 7BA978B8
|
||
put hex file there, systems reboots, a file with the ending .RDY or .ERR is placed.
|
||
|
||
#### Moto X4
|
||
```
|
||
*#*#4636#*#* --> Telefonwartungsmenü
|
||
```
|
||
```
|
||
VoLTE sowie WiFiCall kann erst mit neuem Update kommen, da der APN von 07 auf 03 geändert wurde und die carrier-Datei muss in der Firmware abgeändert werden.
|
||
```
|
||
[Nachweis VoLTE](https://forums.lenovo.com/t5/Moto-X4/VoLTE-on-ALDI-TALK/m-p/4228082)
|
||
|
||
|
||
##### bootloader unlock
|
||
disable USB3
|
||
https://www.reddit.com/r/LineageOS/comments/gofxb6/fastboot_oem_get_unlock_data_outputs_nothing/
|
||
|
||
|
||
```
|
||
sudo mfastboot oem 'get_unlock_data'
|
||
...
|
||
(bootloader) Unlock data:
|
||
(bootloader) 3A65150608772667#5A593232344839
|
||
(bootloader) 44324D006D6F746F2078340000#AA84
|
||
(bootloader) 541345CCD69E97EE7882B62DEF550E9
|
||
(bootloader) 811B9#900E428D00000000000000000
|
||
(bootloader) 0000000
|
||
OKAY [ 0.014s]
|
||
finished. total time: 0.014s
|
||
|
||
3A65150608772667#5A59323234483944324D006D6F746F2078340000#AA84541345CCD69E97EE7882B62DEF550E9811B9#900E428D000000000000000000000000
|
||
```
|
||
https://en-us.support.motorola.com/cc/productRegistration/unlockPhone/3A65150608772667/900E428D000000000000000000000000/AA84541345CCD69E97EE7882B62DEF550E9811B9/?rad=Yes
|
||
|
||
```
|
||
fastboot oem 'unlock LCGYFJAJE2SSWYAG36FG'
|
||
(bootloader) ***************************************
|
||
(bootloader) WARNING: This command erases user data!
|
||
(bootloader) WARNING: This command voids warranty!
|
||
(bootloader) Please re-run this command to confirm.
|
||
(bootloader) ***************************************
|
||
OKAY [ 0.001s]
|
||
Finished. Total time: 0.001s
|
||
✔ [19:09|koelner@koelner-think ~]$ fastboot oem 'unlock LCGYFJAJE2SSWYAG36FG'
|
||
FAILED (remote: 'unknown command')
|
||
fastboot: error: Command failed
|
||
✔ [19:09|koelner@koelner-think ~]$ fastboot oem 'unlock LCGYFJAJE2SSWYAG36FG'
|
||
(bootloader) Bootloader is unlocked!
|
||
OKAY [ 1.448s]
|
||
Finished. Total time: 1.448s
|
||
```
|
||
|
||
https://wiki.lineageos.org/devices/payton/install
|
||
|
||
#### Odroid HC1 sdcard handling
|
||
Mirror second bootstage
|
||
`dd if=/dev/mmcblk0 of=/dev/sdc bs=512 count=8192`
|
||
partclone (maybe some resize due different sdcard size is required)
|
||
`partclone.ext4 -N -b -s /dev/mmcblk0p1 -o /dev/sdc1`
|
||
|
||
|
||
##### STM32 F103 clones
|
||
https://www.blaatschaap.be/?p=120
|
||
|
||
#### nrf51822 board
|
||
Das Board ist ein übliches nrf51822 board, welches mit der Waveshare BLE400 Platform zum SDK wird. Das Rastermaß scheint kleiner zu sein.
|
||
Mit einem ST-Link V2 konnte über die beiden Pins SWCLK und SWIO geflasht werden.
|
||
```
|
||
openocd -f interface/stlink-v2.cfg -f target/nrf51.cfg
|
||
|
||
telnet localhost 4444
|
||
Trying ::1...
|
||
Connection failed: Verbindungsaufbau abgelehnt
|
||
Trying 127.0.0.1...
|
||
Connected to localhost.
|
||
Escape character is '^]'.
|
||
Open On-Chip Debugger
|
||
> halt
|
||
target halted due to debug-request, current mode: Handler HardFault
|
||
xPSR: 0xc1000003 pc: 0xfffffffe msp: 0xffffffd8
|
||
> nrf51 mass_erase
|
||
|
||
> flash banks
|
||
#0 : nrf51.flash (nrf51) at 0x00000000, size 0x00040000, buswidth 1, chipwidth 1
|
||
#1 : nrf51.uicr (nrf51) at 0x10001000, size 0x00000100, buswidth 1, chipwidth 1
|
||
> flash write_image /home/koelner/Downloads/btlejack-firmware-ble400.hex
|
||
Padding image section 0 with 2112 bytes
|
||
Padding image section 1 with 5864 bytes
|
||
Padding image section 2 with 81204 bytes
|
||
Padding image section 3 with 908 bytes
|
||
using fast async flash loader. This is currently supported
|
||
only with ST-Link and CMSIS-DAP. If you have issues, add
|
||
"set WORKAREASIZE 0" before sourcing nrf51.cfg to disable it
|
||
target halted due to breakpoint, current mode: Handler HardFault
|
||
xPSR: 0x61000003 pc: 0x2000001e msp: 0xffffffd8
|
||
using fast async flash loader. This is currently supported
|
||
only with ST-Link and CMSIS-DAP. If you have issues, add
|
||
"set WORKAREASIZE 0" before sourcing nrf51.cfg to disable it
|
||
target halted due to breakpoint, current mode: Handler HardFault
|
||
xPSR: 0x61000003 pc: 0x2000001e msp: 0xffffffd8
|
||
wrote 261156 bytes from file /home/koelner/Downloads/btlejack-firmware-ble400.hex in 4.912921s (51.911 KiB/s)
|
||
> reset
|
||
|
||
```
|
||
Der CP2102 Adapter TTL kann wohl an P0.09 und P0.11 angeschlossen werden.
|
||
https://github.com/virtualabs/btlejack-firmware/blob/master/config/ble400.json
|
||
|
||
### shelly H&T
|
||
![38343fdf2b38df296baf380fbda7e292.png](38343fdf2b38df296baf380fbda7e292.png)
|
||
```
|
||
sudo bt -L 1 /dev/ttyUSB0
|
||
esp_main.c:157 ht-sensor 1.0 (20220324-134040/v1.11.8-HT-fix-g60b9bd1)
|
||
esp_main.c:159 Mongoose OS 202107262051 (20220324-134039/2.19.1-42-ga0be0b3e) sp 0x3fffff50
|
||
esp_main.c:161 CPU: ESP8266EX, 160 MHz, RAM: 51520 total, 48500 free
|
||
esp_main.c:165 SDK 3.0.5-dev(81bde69); flash: 2M
|
||
esp_exc.c:236 Reset cause: 0 (power on)
|
||
mongoose.c:15761 Mongoose 6.18, LwIP 1.4.0
|
||
mgos_vfs_dev.c:72 sfl0: sysflash (), size 2097152
|
||
mgos_vfs_dev.c:72 root: part ({"dev": "sfl0", "offset": 765952, "size": 262144}), size 262144
|
||
mgos_vfs.c:173 /: SPIFFS @ root, opts {"bs":4096,"ps":256,"es":4096}
|
||
mgos_vfs.c:344 /: size 233681, used: 79818, free: 153863
|
||
mgos_sys_config.c:232 Loading conf3.json
|
||
mgos_sys_config.c:232 Loading conf9.json
|
||
mgos_sys_config.c:306 Switching debug to UART-1
|
||
```
|
||
|
||
well, that it's all folks. The device can not connect to a wifi AP. The self-owned AP works so far, but it can not connect to a different AP, more precisely, it can not get an IP. the guide explains it well: https://asperti.com/2022/shelly-firmware/
|
||
```
|
||
rBoot v1.2.1-cesanta1 - richardaburton@gmail.com
|
||
Flash Size: unknown
|
||
Flash Mode: DOUT
|
||
Flash Speed: 80 MHz
|
||
rBoot Option: Big flash
|
||
|
||
Writing default boot config @ 0x7000.
|
||
Booting rom 0 (0x8000).
|
||
syѕ<EFBFBD><EFBFBD>param error, use last saved param!
|
||
mismatch map 1,spi_size_map 15
|
||
emap1
|
||
map 1 err
|
||
system param partition error
|
||
ota2 partition <20>V2
|
||
Mo
|
||
Backup
|
||
|
||
Exception 20 @ 0x00000023, vaddr 0x00000020
|
||
A0: 0x4027d46a A1: 0x3fffeac0 A2: 0x0001c610 A3: 0x00000088
|
||
A4: 0x3ffe9818 A5: 0x00000004 A6: 0x40000000 A7: 0x3fffdca0
|
||
A8: 0x0000001e A9: 0x00000000 A10: 0x00000000 A11: 0x00000002
|
||
A12: 0x3ffee8ac A13: 0x3ffef024 A14: 0x3ffef0c2 A15: 0x00000023
|
||
|
||
(exc SP: 0x3fffe920)
|
||
```
|
||
however, the guide is not working completely. Some research later, I found out that rboot needs the flash size detection. Otherwise it seems to fail. you need to add `--fs detect` to get the flash size into rboot.
|
||
```
|
||
esptool -p /dev/ttyUSB0 --baud 115200 write_flash -fm dout --flash_freq 80m --fs detect 0x0 rboot.bin 0xBB000 fs.bin 0x8000 shelly-plug-s.bin 0x1FC000 esp_init_data_default_v08.bin
|
||
```
|
||
and should see this:
|
||
```
|
||
rBoot v1.2.1-cesanta1 - richardaburton@gmail.com
|
||
Flash Size: 16 Mbit
|
||
Flash Mode: DOUT
|
||
Flash Speed: 80 MHz
|
||
rBoot Option: Big flash
|
||
|
||
Booting rom 0 (0x8000).
|
||
V2
|
||
Mo
|
||
Backup
|
||
```
|
||
#### MateView
|
||
`Bus 001 Device 018: ID 12d1:10b5 Huawei Technologies Co., Ltd. MateView`
|
||
1. Connect the Windows host to the monitor using a USB-C to USB-C cable or an HDMI/DP+ USB-A to USB-C cable (with the USB-C end connected to the monitor and the USB-A end connected to the host). After the screen is cast normally, right-click the icon in the lower right corner of the desktop, select Open Sound settings to enter the sound settings screen, and then select Microphone (MateView GT) under Choose your input device.
|
||
2. Download the MateView GT HwMateViewGT-CAA Audio Firmware 1.0.zip at https://consumer.huawei.com/my/support/monitors/mateview-gt/
|
||
3. To download the firmware update tool, may visit https://drive.google.com/drive/folders/1j5reoECesfaabvKl_GtARPwlVXf6fLoB
|
||
4. Place the decompressed HwMateViewGT-CAA Audio Firmware 1.0.fwu and the update tool SophiaFwUpd.exe in the same folder. Double-click MateViewGT_Update.bat in the folder to start updating the firmware. Alternatively, press Shift while right-clicking the folder to open the Powershell window. In the displayed Powershell window, run .\SophiaFwUpd.exe -i ‘.\HwMateViewGT-CAA Audio Firmware 1.0.fwu’ -v 0x12d1 –p 0x10b6 and press Enter to start updating the firmware. During the update, do not remove the power cable or signal cable and keep the monitor in projection mode.
|
||
5. The message "Firmware update SUCC." will be displayed after the execution is complete. The message "Please restart monitor." indicates that the audio firmware update is successful. Restart the monitor and try again.
|
||
|
||
|
||
#### wellue pulsoximeter
|
||
https://github.com/zh2x/BCI_Protocol/
|
||
https://pastebin.com/QTeAA3jv
|
||
https://github.com/sza2/viatom_pc60fw/
|
||
https://anaesthetics.app/blog/posts/2020/bluetooth/
|
||
https://github.com/anaestheticsapp/bluetooth/ |