• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 278 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.

TM4C1294NCPDT: TM4C1294NCPDT initializing Ethernet?

kevin.huang_FJXM
Expert 2925 points
Part Number: TM4C1294NCPDT

hi Teams:

TM4C1294NCPDTT3

1. Ohm measurement, normal chip measurement, internal resistance of 3.3V power supply to ground 1.016k The internal resistance of the power supply to the ground is only 19 ohms,

2. The kernel works normally, the program can be burned, the chip falls into an endless loop when initializing Ethernet, and the shielded Ethernet module program can run normally.

3.Defective rate: 1 / 26 tablets = 4%.

  • 0
    TI__Guru*** 135355 points

    Hello Kevin,

    This is not a common fail case so there is likely something specific to either your software setup or your board that is the root cause here. With that in mind, I have some initial questions to help start debugging what is going on here.

    First off, are you running a software example from our TivaWare SDK that is known good software on this board? Or at least software that you validated on a LaunchPad which has all the Ethernet elements running identically?

    Secondly, when the chip falls into an endless loop, where does it get caught up? On a specific API call? Inside of an ISR? Details here can help narrow down possible reasons for the issue.

    Next, given the low fail rate on a small batch of boards, have you had a check at the soldering of the MCU? We have seen at times just one cold joint can cause issues like this on initial batches of PCBs.

    Also, can you explain what you mean by

    kevin.huang_FJXM said:
    the shielded Ethernet module program can run normally.

    Does this mean there is an Ethernet code you can load into the device and run which works properly then? Or were you trying to indicate that after cutting out the Ethernet code that the program then runs fine? I'm not really clear on this part.

    Best Regards,

    Ralph Jacobi