[ABANDONED] Hard fault happened once application elf download and run by Ozone on S32K312 MCU

  • Hello, my issue :

    . Hard fault happened once application elf download and run by Ozone on S32K312 MCU
    MCU : NXP S32K312
    Compiler : IAR ANSI C/C++ Compiler V9.20.4.327/W64 for ARM
    Ozone : V3.38
    Bootloader existing : yes

    I have another project also on S32K312, but compiler is GreenHill, there is not any problem with Ozone debugging, also bootloader present.
    Do you think it's some problem with the IAR compiler generated elf format?
    For example, Ozone can not read out image start or end address of elf.
    When Ozone flashing the elf, it did not preserve memory outside the image area, like bootloader erased, then fault happened after flashing done and reset.

  • Hi Hudson,

    there are 2 things participating in your scenarios:
    1) The ELF file
    2) The Ozone project file

    If the Ozone project file is exactly the same in both your projects for IAR and GreenHill, then the root cause must be sought in the ELF file. It may be possible that IAR is lacking some information that must be reported to Ozone via the Ozone project file.

    Since you state that you are targeting a system with boot loader, some special considerations must be done, which are described in this knowledge base article: https://kb.segger.com/Debug_on_a_Target_with_Bootloader. Could you please have a look and check if everything is set-up as described there?

    Best regards
    -- AlexD

    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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 you can contact us via our support system: https://www.segger.com/ticket/

    Or you can contact us via e-mail.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!