Hi Marcio, I'm replying to the mailing list too because it is important. Yes, it is possible to use SEGGER RTT console with SEGGER SystemView. SystemView is using a different channel than the console. And you can use it on my branch because SystemView was added on top of RTT.
Best regards, Michał 2017-03-09 17:23 GMT+01:00 Marcio Montenegro <[email protected]>: > Hi, > Congratulations.Nice job😃 > So using you branch it is possible to use Segger RTT console also? > Best regards, > Marcio > > Sent from my iPad > >> On 9 Mar 2017, at 09:32, Michał Narajowski <[email protected]> >> wrote: >> >> Hi, >> I'm working on wiring SEGGER SystemView to Mynewt. "SystemView can >> record data from the target system while it is running. The recorded >> data is analyzed and the system behavior is visualized in different >> views." More info here: https://www.segger.com/systemview.html >> >> Right now it is possible to run the app and see some events, tasks, >> interrupts. It's still work in progress and some things might be off. >> I include a screenshot of the application. It shows the visualization >> of events when using bletiny app. >> >> I would love to get your feedback on some things: >> - package structure, file and folder naming >> - tracing api >> - (current and future) placement of tracing api calls >> >> I'm also having some issues with unexpected ISR events showing up. As >> you can see in the screenshot there are some PWM, PDM, SWI4_EGU4 and >> QDEC. The problem is I never made trace calls from these ISRs. In >> fact, I couldn't find any usages of ISR with these IDs in the source >> tree. ISR trace functions do not have ISR ID as an argument. >> SystemView checks specific address when receiving ISR event, so maybe >> there is something wrong with this address. >> >> Anyway, here is the link to my branch: >> https://github.com/michal-narajowski/incubator-mynewt-core/tree/systemview. >> I'm looking forward to any comments. >> >> Best regards, >> Michał Narajowski
