00:17 <mawk> thanks zapb_ I'll try

02:47 <fenugrec> Hi, I'm trying to "profile 2 test.mon" on a cortex-M0, and getting " src/target/target.c:4213: write_gmon: Assertion `addressSpace >= 2' failed "

02:48 <fenugrec> couldn't find a related issue on the SF bugtracker, has this been fixed between 0.11 and the lastest ?

02:48 <fenugrec> *latest

07:54 <PaulFertser> fenugrec: oh hey

07:55 <PaulFertser> fenugrec: hard to tell, 0.11 was a year ago, it would be easiest if you build current master to test tbh.

15:17 <fenugrec> Hi PaulFertser , agreed I should try current master. May find time in the next few days

15:38 <PaulFertser> fenugrec: especially given we are in release candidate stage atm, so testing that would be much appreciated.

15:38 <Haohmaru> what's new in it?

15:39 <PaulFertser> Haohmaru: there's NEWS with highlights

15:45 <Haohmaru> ..lot's of things

15:45 <Haohmaru> * lots

16:05 <fenugrec> PaulFertser, still getting the Assertion failed on oocd @9d925776b

16:05 <fenugrec> (that is, if I don't specify start and end args to the Profile command)

16:06 <PaulFertser> fenugrec: thanks for testing, do you feel like sending a debug log to the mailing list or probably a ticket at SF.net?

16:07 <fenugrec> I don't follow the ML so better be a ticket I guess

16:07 <PaulFertser> The ticket will get sent to the ML automatically then.

16:10 <fenugrec> done

16:14 <PaulFertser> fenugrec: all cool, thank you!

22:49 <tuxd3v> hello guys

22:49 <tuxd3v> is there any support for swim protocol via openocd(using stlinkv2)?

22:50 <tuxd3v> I see that there are several /usr/share/openocd/scripts/target/stm8*.cfg files in openocd in debian 11

22:50 <tuxd3v> but can we flash, and debug via swim?

22:54 <tuxd3v> I mean in linux :)

23:36 <borneoa_> tuxd3v: yes, stm8 swim is supported with stlink v2 and v3. Debug is ok, but you need a special build of fsbl as stm8 should not be upstream. Flashing should work too

23:37 <borneoa_> tuxd3v: sorry, typo. You need special build of GDB .

23:49 <tuxd3v> borneoa_, many thanks.

23:55 <tuxd3v> for what I understand sdcdb debugger dpesn't had support at least in 2018, so you need to compile one from here: https://stm8-binutils-gdb.sourceforge.io/

23:55 <tuxd3v> I don'tknow if this situation was already solved in sdcc

23:58 <Guest22> Hi all,

23:58 <Guest22> I have spent some time working on developing a working version of TMS570 Flash Support with using an RPi 4's GPIO as the interface. For those unfamiliar, there is unofficial support for TMS570 flash support, and the patches can be found here: https://cmp.felk.cvut.cz/~pisa/tms570/. I was able to successfully test the flash capabilities with the

23:58 <Guest22> XDS100v2 inteface and was able to probe, erase, and write to flash using my host computer. I was also able to properly interact with flash on the RPi 4 with the XDS100v2. However, when I attempted to use the RPi 4's GPIO, I was able to find the TAP, probe the flash, erase the flash, but not write to the flash. I consistently got the error:

23:58 <Guest22> "> flash fillw 0x00100000 0xabcd1234 128

23:58 <Guest22> Filling odd buffer 512 bytes

23:58 <Guest22> Write helper code returned -258

23:58 <Guest22> error writing to flash at address 0x00000000 at offset 0x00100000

23:58 <Guest22> in procedure 'flash'"

23:58 <Guest22> Not sure why the XDS100v2 interface works well but the RPi GPIO does not completely work. I have been thinking it may be something to do with RPi configuration like perhaps the speed coeffs or something with my reset_config?

23:58 <Guest22> openocd.cfg file: https://traff.co/KGUgJy80

23:58 <Guest22> raspberrypi-native.cfg file: https://traff.co/227pFS84

23:58 <Guest22> Can anyone help me understand as to why this flash write error is popping up for the RPi GPIO interface? Any help regarding this issue would be greatly appreciated as I have been debugging this issue for quite some time.