Saturday, April 21st 2018, 2:22am UTC+2

You are not logged in.

  • Login
  • Register

[SOLVED] Getting output from user actions in Ozone

v01d

Beginner

Date of registration: Feb 29th 2016

Posts: 105

1

Sunday, February 11th 2018, 6:55am

[SOLVED] Getting output from user actions in Ozone

Is it possible to get the output of the User Actions command inside Ozone?

E.g. I do Target.ReadU32( 0x80000004) .

When I do this from Ozone's Console window, command seems runs, but I get no output. Is there special window .. ?

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 938

2

Monday, February 12th 2018, 5:14pm

Hello,

Thank you for your inquiry.

To enable Ozone log do the following:
launch "Ozone --logfile <logfile>" where <logfile> is the logfile path. More information are available in the Ozone manual.

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/

v01d

Beginner

Date of registration: Feb 29th 2016

Posts: 105

3

Tuesday, February 13th 2018, 12:18pm

Does this mean you cannot get output of those commands in Ozone 's console .. ?
(Same as with JLink commander : read memory, it prints output ).

Did not plan to log anything ..

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 938

4

Wednesday, February 14th 2018, 12:05pm

Hi,

Quoted

Does this mean you cannot get output of those commands in Ozone 's console .. ?

Correct.
The Ozone log will log everything that you see and enter in the Ozone Console.

Most commands you see in the action table of the Ozone user manual will not print any return value in the Console as they are meant to be used with the Ozone scripting interface.
For memory reads and writes while debugging we suggest using the memory window.

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/

Similar threads