Search Results

That's a good question, Arne. Thank you for your advice. Of course the memory is limited, I didn't think of that. In order to debug I've started having ten Putty windows open to listen to each of the Flasher ATE modules. There's all the debug data I need. Thanks again. I'm happy with the product, and I appreicate that Segger staff is available on the forum!

Hi, I'm struggling to debug my project, and I check Flasher.log, and all it says is: SN: 3 - Failed SN: 3 - Failed SN: 3 - Failed I wish it would be more specific. Why can't it have at least the same amount of information as the error in the TCP terminal? Target has no power, etc.. such errors.

Hi Arne, Thank you very much for your reply. My colleague who has more experience with this than me, also gave me the same tip. My problem is solved. Thank you.

Hi, I'm using a Flasher ATE to program my J-Flash generated files. pex, dat, cfg files. #AUTO PATCH 13,100010EC,4:7014A777,100010F0,4:0101E968,100010F4,4:31330F42 Something like this. It works fine. The thing is, during the test some new information is revealed, and I want to write that into another registry, without changing anything else, and without programming the firmware again. Speed is my concern. Is there a command for this? I'm picturing something like: #PATCH, which only does this. I k…