Andrey Skvortsov

Results 31 comments of Andrey Skvortsov

I think, I've experienced similar problem. Here is my test code ``` static void __attribute__((__noinline__)) test_call(void) { static volatile int x=0; x++; } /* void __is_ramfunc __attribute__((__noinline__)) init(void) */ void...

@eldarkg, why do you think that commit bae2538 gives wrong solution of this issue?

Interesting. Do you remember were intermediate functions for EEPROM_* generated by the compiler and used when the issue happened?

I've tried boot.scr, but unfortunatelly it's tried after extlinux. So it will not help either, imho. https://source.denx.de/u-boot/u-boot/-/blob/master/include/config_distro_bootcmd.h#L473

Thanks for the help. As a quick workaround, I've binary patched tow-boot image. I've changed command order to check for scripts first. ``` "run scan_dev_for_scripts; " "run scan_dev_for_extlinux; " ```...

I've paired using bluetoothctl, not Amazfish. ``` mobian@mobian:~ $ bluetoothctl Agent registered [CHG] Controller 00:E0:XX:XX:XX:XX Pairable: yes [InfiniTime]# info Device E2:C8:XX:XX:XX:XX (random) Name: InfiniTime Alias: InfiniTime Appearance: 0x00c2 Paired: no...

> Please also establish a GATT connection where encryption is used. ``` root@mobian:/home/mobian# gatttool --sec-level=high -b E2:C8:XX:XX:XX:XX -t random -I [E2:C8:XX:XX:XX:XX][LE]> connect Attempting to connect to E2:C8:XX:XX:XX:XX Connection successful [E2:C8:XX:XX:XX:XX][LE]>...

@Avamander IMHO, it doesn't help. I've paired with pinetime and after setting sec-level to high see enabled encryption in btmon. ``` < HCI Command: LE Start Encryption (0x08|0x0019) plen 28...

Because it's happening not only with Amazfish, do we need to reopen this issue?

I've seen the problem with 1.9 and probably with 1.8 in the past. I can reproduce reset by watchdog by flooding PineTime with notifications. See following video: https://www.youtube.com/watch?v=APFLuV7WYLc