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.

TM4C129ENCPDT: BIOS start Failing - How to solve this issue?

Part Number: TM4C129ENCPDT
Other Parts Discussed in Thread: SYSBIOS

Dear expert

BIOS start is failing with the TM4C129ENCPDT, 

I have two boards

1. Old board

2. Newly populated board.

Old board is working fine ,

New board "BIOS start" is not working ( When I am doing in circuit debug it fails and abort from BIOS Start ). 

The error reply is 

Using MAC address in flash

Network Added: If-1:192.168.79.20

ti.sysbios.family.arm.m3.Hwi: line 1277: E_noIsr: id = 94, pc = 00003ad8

Exception occurred in background thread at PC = 0x00003ad8.

Core 0: Exception occurred in ThreadType_Task.

Task name: {unknown-instance-name}, handle: 0x20000d08.

Task stack base: 0x20000d58.

Task stack size: 0x800.

R0 = 0xe000e108  R8  = 0xffffffff

R1 = 0x00004000  R9  = 0xffffffff

R2 = 0xe000e108  R10 = 0xffffffff

R3 = 0x00000001  R11 = 0xffffffff

R4 = 0xffffffff  R12 = 0x00000001

R5 = 0xffffffff  SP(R13) = 0x200014a8

R6 = 0xffffffff  LR(R14) = 0x00003ad9

R7 = 0xffffffff  PC(R15) = 0x00003ad8

PSR = 0x01000000

ICSR = 0x0042385e

MMFSR = 0x00

BFSR = 0x00

UFSR = 0x0000

HFSR = 0x00000000

DFSR = 0x0000000b

MMAR = 0xe000ed34

BFAR = 0xe000ed38

AFSR = 0x00000000

Terminating execution...

  • Hi,

      Can you provide more information?

     - Are the two boards identical?

     - Are you running exactly the same code on both board where the old board is working while the new board is giving the above error?

     - If the code running on the old and new boards is different then what is the difference between them? 

     - You said the new board will fail in debug mode. Does it work when you let the processor free run?

  • Hi charles,
    Thanks for your reply.
    1.Are the two boards identical?
                Layout wise identical boards, but Old board has 4 LTC2500-32bit ADCs, New board is populated with 2 LTC2500-32bit ADCs, and the other two ADC slots are left blank.
                 New board - ADCs connected in Slot 2 and 3. Slot 1 and 4 are left blank.
     
    2. Are you running exactly the same code on both board where the old board is working while the new board is giving the above error?
               Except the below change all are the same. 
               With the old board the data ready interrupt is configured with ADC 1 (GPIO_PIN_1), Since it is not connected for the new board it is changed to ADC2 (GPIO_PIN_2)
     
    3.  You said the new board will fail in debug mode. Does it work when you let the processor free run?
               No ,New board doesn't transfer the data to the PC, So i checked it in Debug mode, It is failing in BIOS start.
     
  •  With the old board the data ready interrupt is configured with ADC 1 (GPIO_PIN_1), Since it is not connected for the new board it is changed to ADC2 (GPIO_PIN_2)

    Please be specific on which GPIO pin (e.g. which port) you use for ADC1 and ADC2. Did you enable the corresponding GPIO port that is connected to your ADC2? Any peripheral that is not enabled will cause a fault. 

  • Yes the Initialization is done for all ADCS - it is configured with Port P, ( All 4 ADCs interrupt  are connect to Port P  and all are initialized ,  but interrupt is enabled for only ADC2)

    Below findings I did , This will give any lead to the reason. 

    1. Bios Start is not throwing any error in debug mode if it is connected only with Debugger .

    2. BIOS start is throwing error if the board is powered with external source. 

  • Hi,

    1. Bios Start is not throwing any error in debug mode if it is connected only with Debugger .

    2. BIOS start is throwing error if the board is powered with external source. 

    It is hard to know what really caused the exception when one board works but not the other especially the one that fails only fails in power up and not in debug mode. If it only fails in power up then how did you know that it fails immediately after BIOS_Start(). Can you try the free run mode from CCS? See below. What is the result compared to Power Up?

    Can you take a look at these posts and see if you can diagnose the problem.

    https://training.ti.com/debugging-common-application-issues-ti-rtos

    https://e2e.ti.com/support/processors/f/791/t/854484

    https://e2e.ti.com/support/processors/f/791/t/816720