Page 1 of 1

New debug option

Posted: Thu Apr 28, 2016 11:58 am
by Jacon
Quite interesting :D :

http://www.edn-europe.com/news/seggers- ... mcu-boards

especially, you may always reverse this to original one...

Re: New debug option

Posted: Thu Apr 28, 2016 1:02 pm
by Giovanni
hi,

Smart move on their side, to be tested for sure.

Giovanni

Re: New debug option

Posted: Tue May 17, 2016 11:41 am
by RoccoMarco
Hi, indeed I received a comment from a Segger guy just below my latest review on PLAY Embedded (STM32 Nucleo144 review).

He said that system view could be integrated into eclipse. I have continued the conversation privately and they have decided to send us a JLink Pro as sample asking us to write a review.

I will try it and I will try to flash the STLink with their firmware. I do not deny that it would be more exciting if Segger would also support ChibiOS in their system view, especially because the ChibiOS statistic module is considerably detailed (even if its style is... minimal :mrgreen:).
Ciao,
RM

Re: New debug option

Posted: Sat Apr 14, 2018 1:40 am
by faisal
BEWARE using j-link flashed st-link debugger. I have had success with several of them, but I now have 2 solid data points showing that the j-link flashed st-link debugger resulted in a corrupted flash image when programming the target. When reverted back to st-link firmware, the same .elf file was flashed correctly to the target.

Saw this thread while I was googling for something. I know I'm bringing this thread up from the dead - but I did have something to share :) .

Re: New debug option

Posted: Sun Apr 15, 2018 12:09 pm
by rew
It would be interesting to see the image that ends up in the MCU with the different flashing methods. You can simply read the CPU to produce a binary file.

Re: New debug option

Posted: Sun Apr 15, 2018 3:31 pm
by faisal
rew wrote:It would be interesting to see the image that ends up in the MCU with the different flashing methods. You can simply read the CPU to produce a binary file.


I did compare the images, definitely corruption. Unfortunately can't share the binary.