zamniah Community Member
- Member since Mar 9th 2020
- Last Activity
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
zamniah -
Replied to the thread [SOLVED] Reset device from Ozone vs from JLinkExe (JTrace).
PostI think I solved it, adding: Source Code (32 lines)I have no idea why I can't indent the code or remove the comments, but it just works this way ¯\_(ツ)_/¯ -
zamniah -
Replied to the thread [SOLVED] Reset device from Ozone vs from JLinkExe (JTrace).
PostFor some time I've been using this to correctly reset device to "boardloader" (first execution stage, we have two additional, bootloader and firmware, each in separate ELF file): Source Code (17 lines) It worked quite well, though for some reason it… -
zamniah -
Posted the thread [SOLVED] Reset device from Ozone vs from JLinkExe (JTrace).
ThreadI think I solved it, adding: Source Code (32 lines)I have no idea why I can't indent the code or remove the comments, but it just works this way ¯\_(ツ)_/¯ -
zamniah -
Replied to the thread [SOLVED] JTrace keeps reflashing/upgrading itself without confirmation and I have no idea how to stop it.
PostQuote from SEGGER - Alex: “You have the possibility to downgrade (see UM08001 which explains how to do it). However, in your case, it looks like something inhibits further FW replacement (no matter if a new or an old FW shall be flashed). So even your… -
zamniah -
Replied to the thread [SOLVED] JTrace keeps reflashing/upgrading itself without confirmation and I have no idea how to stop it.
PostYes, it seems that reflashing loop stopped. However for future it would be best if it was possible to flash a specific version of firmware (from JLink Commander for example, from a FW image file). Forced upgrade without possibility of downgrade is… -
zamniah -
Posted the thread [SOLVED] JTrace keeps reflashing/upgrading itself without confirmation and I have no idea how to stop it.
ThreadI noticed this message at least 3 times this week: Source Code (8 lines) Also I have no idea what causes it, is it Ozone, JLink Commander or something else? Nevertheless there was never any confirmation. The firmware I bought it with worked fine, but…