Testing #2
Comments
|
|
I did just say runtime mode :/ mostly as I've not finished testing it across all my devices. Have you checked that if you hold the front button and plug it in that it doesn't appear in device manager / lsusb ? If it does show up but the screen stays black then you can probably just reflash runtime and then flash it with the screen starting off vasc it's most likely the thing that's dodgy is the OLED code. But yes that st-link or the many like it will work, is it doesn't show up on USB. Not sure what the easiest way for you to buy locally is but those units work great as little clones. Often they are $3-4 USD ish around here fwiw. |
|
Don't panic I'll help get this fixed up, worst case is the st-link but that's all |
|
@Ralim I already tried to reflash |
|
Yeah okay if that's not working, an st-link, and you also want a USB breakout so that you can access the USB pins . I use a USB-A socket breakout that gives me the VCC,D+,D- and GND pins. I then supply 5v,GND from the st-link. And wire up D+ and D- to the SWD pins and then you can reprogram it without opening. Alternatively one could cut up a USB cable, but if you can buy a cheap breakout that is easiest |
|
Thanks! |
Good news! 😁My TS80P is alive again! |
|
Excellent :D You managed to restore the bootloader fine? :) Glad you managed to get it going before I woke up. Sorry about the mess of having to buy an st-link. |
|
Yes that worked! The hardest part was to get the No reason for you to feel bad however! 😃This was clearly my fault and obviously the consequence of my impatience! 😁 So I am here for more testing! |
|
You have found something interesting.. Could I ask you to repeat what you did last time with the latest action builds; and also record the commands you run? |
|
I've cleaned up the ci builds to prevent any accidental contamination between them, but even still not sure what could have gone wrong :/ |
Thank you, this time it worked immediately! 😃👍I like the instant powerup very much! A lot better than the stock bootloader. ❤2 things I would like to issue though are:
|
|
I dont know if its worth doing lefty/righty modes 😁 Its just more firmwares to confuse people :P Should probably centre the logo though |
|
I dont want to go minimum brightness, but rather middle of the range :) I'll update to make it flipped for the TS80's so its the right way around for righties. |
|
@Ralim
Yeah I got that, but as mentioned above, I wanted to only apply this to my fork. I will not start a PR to the mainline. 😊Unless you do not want me to build my own.
That would be great! |
|
trying runtime.hex - flashed ok. dfu-util -d 28e9:0189 -U backup.bin -s 0x08000000:0x4000 here is dmesg output [ 27.077322] usb 1-10.4: new full-speed USB device number 10 using xhci_hcd |
This is the bootloader Can you provide output of Noting your dfu-util is older but it should work fine for this. You may need to run |
dfu-util installed to ubuntu 20 lts via apt-install. will try to update. lsusb 28e9:0189 connected directly to motherboard with good working usb-cable which worked ok flashing runtime.hex. |
|
Downloaded .11 binaries: |
|
For in ubuntu you copy the hex twice to get it to flash (first will .err, second works) So its showing up on usb, so it may be either sudo access or out of date dfu-util i'm afraid |
|
Oh! Problem solved - sudo! Please add it to .md |
|
@JugglerLKR Thank you for the MD5 and for testing. |
|
TS100 3.43 STM32: |
|
|
I have backed up TS80 DFU 3.45, no one else uploaded his fw hash yet, is there any way to be sure it is ok? I don't fully understand the bytes thing. Maybe @Ralim would you mind checking if I send the file directly to you? My sum is fadae45b4249d4f156c30b7d4b0a853e. The runtime works perfectly. |
|
Happy to inspect and test the backup for you if desired. |
|
I may have something odd going on with my TS100, when it's in DFU mode it says it's 3.45 but the md5sum of the backup matches the one listed for 3.42. Fun bit of trivia I noticed while checking this out: |
|
upgrading my Miniware TS80P with DFU 3.50 to IronOS-DFU 0.2 worked like a charm. I have used macOS 11.6 and usb-c -> usb-c 2.0 cable connected to one of the ports on my Mac. I did boot new boot loader at runtime, made a backup, checksum did confirm 3.50 dfu version and then flash boot loader in place of existing one. all I had to do after is flash firmware itself using dfu mode. |
|
hi, trying runtime version on mhp30 and it gets renamed to RUNTIME.NOT instead of err or rdy extension. all i do is copy runtime.hex to device. is there anything else i could try? |
|
Running DFU: 3.45 currently Anyone have thoughts on why I'd get a black screen after flashing runtime.hex? dfu-util also doesn't see any usb device when booting the runtime.hex after flash. |
|
tested and fully working on TS-100 stm32f103 As reported by other users, the md5 hash appears to match v3.42 despite the oled displaying DFU v3.45. |
Same here!!!!😭
|
|
@L1cardo This solved my problem. |
|
i tried and Sequre S60 and it works well with IronOS-dfu runtime worked like charm but flashing bootloader triggered some protection in my case (turns out read out protection bit was set) and triggered erase. restoration was all about opening, connecting STLINK/SWD (there is pads with D=SWDIO, V=3.3V, G=GND, C=SWCLK under display) and shorting 44th (boot0) and 43rd (gnd available there, somehow actual ground didn't work here) pin permits for iron to be detected by STLINK. for whoever needs help locating pins - they are 5th and 6th pin counted from bottom up on the left side of iron when you hold iron tip holder toward yourself and usb port outward. when you hold iron like this - chip gonna have round/dot indent indicating first pin in left bottom corner. read out protection could be removed either by older ST-LINK utility or by OpenOCD. anyway, IronOS-DFU works well on Sequre S60 :) |
|
i have got second ts80p since i did like original one... and looks like they changed some things. i have DFU bootloader 3.50 (1.30 firmware) with 1805EC83F64C74DD89F87A1B57B7E631 MD5 and it can not flash any IronOS firmware by drag and drop. i tried IronOS-dfu and it is the same. i did connect it through SWD and got a bootloader and 'full dump' from there. i tried different usb ports, different connections (usbA / usbC), different cables (thunderbolt3, thunderbolt4, usb2 usbC/usbA, usb3 usb-C/usbA) and still get bad file descriptor. any suggestion what else i could try? do i need to provide dumps? no wonder it retails for half of its original price now. |
i was able to flash using st-link instead of cube programmer and it booted bootloader with working display. flashing correct ironos was straightforward. something something hardware changes, something something compatibility gets worse (quirky?) this ts80p with 3.50 dfu had v1.3 board revision. |
Soo..... This code should now be into the territory of testable.
I've tested on 3x TS100's so far.
To test still:
If anyone out there wants to give it a shot to just test the
runtimeversion would be fantastic.Just grab the runtime.hex from the latest action
If you can run runtime and make a bootloader backup would be fantastic, and if you could note the md5sum of your backup + your bootloader version would be awesome.
The text was updated successfully, but these errors were encountered: