Thanks for your job Ake!
I have some technikal problems. I'm using at now Debian Etch (stable 9.3) architecture amd64 and i386.
gdb and binutils installed are slightly different version and target, also I have use binutils-avr but those are have different names. What would happen if I install your modified versions over them? I still need those version and architecture and I have plans for armeabi or eabihf. What I can do to keep my packages consistent?
You propose SDCC 3.6.0 but I have use 3.6.9 (the latest for now)?
Patched openodc 0.10.0 would not be a problem - I have make it without error. I hope it wouléd work for arm mcu's too.
The last question is that can I use for debugger fronted ddd?
(Eclipse is nice, many people around use it, but not my favorit. I hope that ddd is good enough for this job.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello and thanks for your interest in the stm8 binutils project.
Nothing terrible will happen if you install the stm8-binutils in parallel with your avr tools. The stm8-binutils tools will be prefixed with stm8- and so it will not clash.
The latest release for sdcc is 3.6.0 as far as I know. If you pulled the source from the repository (trunk) there is support for DWARF debugging already in there. How ever it is not compatible with the released version of the stm8-binutils tools. I plan to relase a new version very soon taking care of that. In the mean while I could send you a patch for you to try.
You could use any gdb front end that use gdb MI interface.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your job Ake!
I have some technikal problems. I'm using at now Debian Etch (stable 9.3) architecture amd64 and i386.
gdb and binutils installed are slightly different version and target, also I have use binutils-avr but those are have different names. What would happen if I install your modified versions over them? I still need those version and architecture and I have plans for armeabi or eabihf. What I can do to keep my packages consistent?
You propose SDCC 3.6.0 but I have use 3.6.9 (the latest for now)?
Patched openodc 0.10.0 would not be a problem - I have make it without error. I hope it wouléd work for arm mcu's too.
The last question is that can I use for debugger fronted ddd?
(Eclipse is nice, many people around use it, but not my favorit. I hope that ddd is good enough for this job.)
Hello and thanks for your interest in the stm8 binutils project.
Nothing terrible will happen if you install the stm8-binutils in parallel with your avr tools. The stm8-binutils tools will be prefixed with stm8- and so it will not clash.
The latest release for sdcc is 3.6.0 as far as I know. If you pulled the source from the repository (trunk) there is support for DWARF debugging already in there. How ever it is not compatible with the released version of the stm8-binutils tools. I plan to relase a new version very soon taking care of that. In the mean while I could send you a patch for you to try.
You could use any gdb front end that use gdb MI interface.