[SOLVED] Not expected behaviour when opening ELF file with Ozone

andypandy · April 1, 2025 at 1:06 PM

Hi there,

I have an ELF file of the u-boot bootloader, that I'd like to debug.

Code

aarch64-poky-linux-readelf -h u-boot 
ELF Header:
  Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 
  Class:                             ELF64
  Data:                              2's complement, little endian
  Version:                           1 (current)
  OS/ABI:                            UNIX - System V
  ABI Version:                       0
  Type:                              EXEC (Executable file)
  Machine:                           AArch64
  Version:                           0x1
  Entry point address:               0x40200000
  Start of program headers:          64 (bytes into file)
  Start of section headers:          5552136 (bytes into file)
  Flags:                             0x0
  Size of this header:               64 (bytes)
  Size of program headers:           56 (bytes)
  Number of program headers:         2
  Size of section headers:           64 (bytes)
  Number of section headers:         27
  Section header string table index: 26

Display More

Compiled by aarch64-poky-linux-gcc (GCC) 11.2.0.

When I open it with the Ozone, it prints the following in the console, no errors are seen there, but shows content of the file as an editor that opened a binary file, not the source code expected:

Code

Disabled output of control characters
SEGGER Ozone - The J-Link Debugger V3.38d
J-Link software found at: /opt/SEGGER/Ozone_V338d/Lib/libjlinkarm.so
File.NewProject();
File.NewProject();
File.NewProjectWizard();
Target core support plugin loaded.: /opt/SEGGER/Ozone_V338d/Plugins/Core/CorePluginARM.so
Project.SetDevice ("MIMX8MQ5_A53_0");
Project.SetHostIF ("USB", "");
Project.SetTargetIF ("JTAG");
Project.SetTIFSpeed ("4 MHz");
Project.AddSvdFile ("$(InstallDir)/Config/CPU/Cortex-A53_AArch64.svd");
File path resolved: "$(InstallDir)/Config/CPU/Cortex-A53_AArch64.svd" was found at "/opt/SEGGER/Ozone_V338d/Config/CPU/Cortex-A53_AArch64.svd"
File.Open ("/tmp/u-boot");

Display More

What did I miss?

Thank you for your help

Cheers,
Andy

SEGGER - AlexD · April 2, 2025 at 9:45 AM

Hi andypandy,
in general loading an ELF file should work as you expect it. According to the given information the ELF file should be digestible by Ozone. You may check if changing the file extension to ".elf" does have a positive effect. If not, could you please share your ELF file with us for further analysis?
Best regards
-- AlexD

andypandy · April 2, 2025 at 10:24 AM

Hi AlexD,

You are magician.
Adding elf extension to the file name did the trick!

Thank you,
Andy

SEGGER - AlexD · April 2, 2025 at 11:48 AM

Hi andypandy,

thank you for the flowers and good to see you are up and running again.

Actually, Ozone should be able to cope with ELF files not coming with a file name extension. In that case ELF file detection is supposed to operate on the ELF file header information, which, according to your initial post, appears to be OK. So if you could provide your ELF file we could check if we can reproduce your observation.

Best regards
-- AlexD

andypandy · April 2, 2025 at 1:46 PM

Hi AlexD,

I spent some time to find out what might have caused the issue.

My findings:

If there is the dot in the directory name (in my case it was 2021.04-r0) in the path leading to the elf file (.) it opens it as a binary file unless .elf extension is present.
So, if you put the u-boot to /tmp/1.1/ directory it will open it as binary, if you put there u-boot.elf it will open it as ELF, on the other hand if you copy the u-boot to /tmp/1/ it will open it as ELF.

I hope it helps, it doesn't seem to depend on the content as much as the directory names, and the elf file name.

P.S. I am running the Ozone in Linux

Cheers,
Andy

SEGGER - AlexD · April 3, 2025 at 9:12 AM

Hi Andy,
thanks for the details. Might well be that Ozone gets a hick-up when handling file names as you did. We will check if we can reproduce that locally. Stay tuned, we will report back.
Best regards
-- AlexD

SEGGER - SebastianB · April 7, 2025 at 10:11 AM

Hi Andy,

quick update: We were able to reproduce the issue.
We will of course have a closer look and provide a fix in a future Ozone release.

Thank you for making us aware of this!

Kind regards,
SebastianB

andypandy · April 7, 2025 at 2:25 PM

Hi SebastianB,

Good to know!
Thank you for your support.

Cheers,
Andy

[SOLVED] Not expected behaviour when opening ELF file with Ozone

Participate now!

Tags

Users Viewing This Thread