Testing

[Ralim]

Soo..... This code should now be into the territory of testable.
I've tested on 3x TS100's so far.

To test still:

• TS80
• TS80P
• MHP30

If anyone out there wants to give it a shot to just test the runtime version 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.

[discip]

runtime worked for me! 👍

DFU 3.5

MD5 1805EC83F64C74DD89F87A1B57B7E631

@Ralim

😭Apparently, I bricked my beautiful TS80P!

I did follow all the instructions you provided, starting with flashing runtime, backing up the original bootloader and finally flashing your bootloader.
The result showed up as you predicted:

flash log

Match vendor ID from file: 0483
Match product ID from file: df11
Multiple alternate interfaces for DfuSe file
Opening DFU capable USB device...
Device ID 28e9:0189
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
File contains 1 DFU images
Parsing DFU image 1
Target name: ST...
Image for alternate setting 0, (1 elements, total size = 5400)
Setting Alternate Interface #0 ...
Parsing element 1, address = 0x08000000, size = 5392
Erase           [=========================] 100%         5392 bytes
Erase    done.
Download        [=========================] 100%         5392 bytes
Download done.
Done parsing DfuSe file

... but after unpluging and repluging the USB cable the screen stayed black! 😔🤷‍♂️

Is there any chance of reviving the TS80P?
Which st-link would I need?

Is this one sufficient?

Please don't get me wrong, I know that this is my fault, since you only asked to test runtime.
But honestly: I was that much excited, that I did not read the text carefully the first time, because I wanted to get this immediately onto my iron. 😩🤦‍♂️

thanks in advance

[Ralim]

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.

[Ralim]

Don't panic I'll help get this fixed up, worst case is the st-link but that's all

[discip]

@Ralim
Good morning Sir,
thank you for replying in time. 😃

I already tried to reflash runtime, but unfortunately no luck what so ever.
So next step is to buy the st-link?
Do I need any adapter apart from this?

[Ralim]

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

[discip]

Thanks!
As soon as I get the needed parts, I think I will have to ask you about the what and how once more. 😃

[discip]

@Ralim

Good news! 😁

My TS80P is alive again!

[Ralim]

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.

[discip]

Yes that worked! The hardest part was to get the STM32 ST-LINK Utility software, though! 😓

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!
What's next?

[Ralim]

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 done testing on my TS80 and TS80P now and they also work fine 😓
If you can reproduce the issue, could you save our your flash as a hex for the case where it doesnt boot ?

[Ralim]

I've cleaned up the ci builds to prevent any accidental contamination between them, but even still not sure what could have gone wrong :/

[discip]

@Ralim

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:

1. Orientation being in lefty mode (Maybe you could provide 2 separate builds left and right.)
2. Logo not centered

[Ralim]

I dont know if its worth doing lefty/righty modes 😁 Its just more firmwares to confuse people :P

Should probably centre the logo though

[discip]

@Ralim
Would you mind telling me what I need to change,

1. to get righty mode? (Are there not more righties than lefties out there?) 😁
2. to set the brightness to the lowest possible value?

IronOS-dfu/src/oled.c

Line 14 in 5b662a7

0x80, 0x0F, /*16 == max brightness,39==dimmest*/

or / and

IronOS-dfu/src/oled.c

Line 24 in 5b662a7

0x80, 0x81, /*Brightness*/

I would like to adapt my fork only.