Sunday, December 17th 2017, 2:33pm UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Aryan438

Beginner

Date of registration: May 25th 2016

Posts: 6

1

Wednesday, May 25th 2016, 9:33am

[Solved] Name the ISR

Hi,

I am using the NoOS port of the SystemView and I want to monitor some interrupt routines.
I haven't looked much into the code but I want to name the interrupt routines so that I can differentiate them correctly on the GUI. Right now I see that the are named ISR #22 and ISR #33 which is kind of confusing. Can you tell me how I can name my ISR as SEGGER_SYSVIEW_RecordEnterISR() does not take any arguments. I tried putting SEGGER_SYSVIEW_NameResource(SEGGER_SYSVIEW_EVENT_ID_ISR_ENTER, "GPIOTE_ISR"); but that only shows up in the log and not on the tasks list.

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 366

2

Wednesday, May 25th 2016, 10:21am

Hi,

Interrupts can be named in the System Description String.

Have a look at SEGGER_SYSVIEW_Config_NoOS.c:
SEGGER_SYSVIEW_SendSysDesc("I#15=SysTick");

To define multiple interrupts, add them in a comma separated list:
SEGGER_SYSVIEW_SendSysDesc("I#15=SysTick,I#99=ETH");

Regards
Johannes

Aryan438

Beginner

Date of registration: May 25th 2016

Posts: 6

3

Wednesday, May 25th 2016, 10:52am

fantastic, works like a charm.
And thank you for super fast response.
I am working in Nordic Semiconductor tech support and evaluating this tool. So far it has been great.

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 366

4

Wednesday, June 1st 2016, 5:41pm

Hi,

Thanks for the positive feedback.
Great to read you like it.

Regards
Johannes

rols

Beginner

Date of registration: Jan 15th 2014

Posts: 43

5

Saturday, June 4th 2016, 3:57am

It would be a very handy enhancement if you were able to name the interrupts in the .txt file as well. With the latest enhancements I've managed to move almost all the strings to the .txt file, saving code size and bandwidth. The only strings left in the instrumentation code are now the IRQ names and you have to decide how often to send them. If SystemView read them from the .txt file, it would always have them available no matter when it started up.

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 366

6

Monday, June 6th 2016, 10:54am

In contrast to the API description, interrupt Ids are device specific. #31 isn't the same on nRF51 as on STM32F4.
Therefore the interrupt description should be provided by the application.

We might add description files for devices in a future version,
but for now they should be recorded in the system description callback, which is called when SystemViewer connects.

Regards
Johannes