Search Results

Search results 1-3 of 3.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Thank you for your response. I think the documentation is clear. Is there a case when SEGGER_RTT_MAX_INTERRUPT_PRIORITY can have a different value than configMAX_SYSCALL_INTERRUPT_PRIORITY? If yes, then I agree that RTT sources cannot have that assert. Alternatively, is it possible to add an assert in SeggerSystemView or do something else to catch this mis-configuration?

  • I recently debugged this hard-to-debug issue which turned out to be incorrect value of SEGGER_RTT_MAX_INTERRUPT_PRIORITY-…getting-disabled/17676/13. I think adding an assert to ensure that SEGGER_RTT_MAX_INTERRUPT_PRIORITY is set to the value of configMAX_SYSCALL_INTERRUPT_PRIORITY will make detecting these kind of mis-configurations much easier. Thanks.

  • Segger J-Link Ultra Plus external probe does not work with the RISC-V SiFive HiFive1 Rev. B board. The board has a Segger OB and Ozone is able to detect both the Segger probes (OB as well as Ultra Plus) but none of them is able to connect to the target. I get the following log: Source Code (10 lines) When I remove the external probe, the OB works. What do I need to do make the external probe work? Thanks.