• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 67 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LM3S6950: What is "BIOS_exit(0)" ?

K.Z
Expert 2480 points
Part Number: LM3S6950

Tool/software:

Hi All,

This will be a fault after mass production.
LAN communication with the host system is not possible due to an initialisation failure on the microcontroller side.
As a results in an error where the target unit is not activated.

Are there any items to check ?

I am concerned about the ‘BIOS_exit(0)’ at initialisation failure.
Please tell me what this ‘BIOS_exit(0)’ is.

Best Regards,

Ito

  • +1
    TI__Guru**** 191486 points

    Hi Ito-san,

    K.Z said:
    This will be a fault after mass production.
    LAN communication with the host system is not possible due to an initialisation failure on the microcontroller side.
    As a results in an error where the target unit is not activated.

    How many units failed as described? Is this a just one unit that failed? What is the percentage of failures?

    K.Z said:
    I am concerned about the ‘BIOS_exit(0)’ at initialisation failure.
    Please tell me what this ‘BIOS_exit(0)’ is.

      Please refer to the SYS/BIOS user's guide for details on BIOS_exit(). 

    BIOS_exit() — Call this function when you want a SYS/BIOS application to terminate. BIOS_exit() does not return to the function that called BIOS_start(). Instead, BIOS_exit() calls System_exit() and aborts. All functions bound via System_atexit() or the ANSI C Standard Library atexit() function are then executed. Calling BIOS_exit() is recommended over calling System_exit() for SYS/BIOS applications, because BIOS_exit() performs internal cleanup before calling System_exit(). If an application needs to terminate with an error condition, it should call System_abort() or System_abortSpin().