Sunday, November 19th 2017, 8:57pm 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.

Message information
Automatically converts internet addresses into links by adding [url] and [/url] around them.
Smiley code in your message such as :) is automatically displayed as image.
You can use BBCode to format your message, if this option is enabled.
Security measure

Please enter the letters that are shown in the picture below (without spaces, and upper or lower case can be used).

The last 2 posts

Monday, November 13th 2017, 2:18pm

by SEGGER - Nino

Hello Henry,

Thank you for your inquiry.
Such behaviour is not known to us.
What target device are you trying to debug?
Does it happen during debug session too or is it shown then correctly?
If not could you provide us with the elf file and your jdebug file?

Best regards,

Sunday, November 12th 2017, 5:26pm

by henry10210

How to disassemble cross-compiled ELF in ozone?

Hello, I was looking for a better side-by-side (C-and-assembly) view of the code than what gdb give you, so I am trying out ozone (other people apparently got it to work as you can see here). But after loading up my u-boot ELF file, ozone does NOT show me the assembly (only the machine code) as you can see in the attached picture.

I would guess this is because ozone doesn't know where my cross-tool chain is--even though I have an environment variable called CROSS_COMPILE. How can I tell Ozone to use this toolchain (I would guess it has to call the right readelf and objdump)?

Thanks for reading.
henry10210 has attached the following image:
  • OzoneDisassemble.png