• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 291 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.

DM3730 boot or powerup problem

bandini
Intellectual 630 points

Other Parts Discussed in Thread: DM3730, TPS65910

Hi,

I have a new custom board, but I can't get the DM3730 to boot.
All tensions ramp up in the correct order, and reset is released after that (we are using tps65910)
19,2 MHz crystal is oscillating.

If the nreswarm pin is monitored from start the following behaviour is observed :

- pin goes up for something like 360 milliseconds.
- pin is asserted and goes up again for 12 msec
- repeat stage 2 every 12 msec.

sysboot is 0101111 ie

- external oscillor
- peripheral boot mode
- USB UART3 MMC Nand order

What could cause the DM to reset itself after 360 msec ? 

  • 0
    Guru 31670 points

    Bandini,

    I believe you are facing similar issue here.

    http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/p/226073/797365.aspx#797365

  • 0 in reply to Renjith Thomas
    Intellectual 630 points

    The timing looks similar, but there is a major difference : I am not booting from Nand, unless my boot configration is not sampled correctly. I SHOULD be booting from usb (not connected), then UART3 (no activity seen) then MMC (no activity either) and finally nand (not soldered yet).

    I will check the nand footprint for activity and come back. Thank you for your interest.

    By the way, you mentionned a thread, but the solution to their problem is not really discussed in the thread. 

  • 0 in reply to bandini
    Guru 31670 points

    Bandini,

    I'm sorry, I forgot to check the thread completely. The solution is this according to Steve.

    "We solved the problem last night. We made a schematic error with the boot configuration pins. I knew this a week ago but last night I discovered that the rework to correct this was done incorrectly."