DRA71XEVM: Board does not boot

Sergey_Buloshnikov

Part Number: DRA71XEVM

Hello,

I have a problem with the Jacinto 6 Entry evm (DRA71x, DRA79x).
There is no output to the terminal that is connected to serial port over the mini USB (debug) port, all I'm seeing is the USB debug and power LEDs turned on.

Trying to boot from micro SD card: SD was prepared according to "Processor SDK Linux Automotive Software Developers Guide".

According to User's Guide "DRA71x EVM CPU Board" no EVM configuration is required, all is needed is to ensure the correct SoC boot mode is set using the SYS_BOOT switches.
There is no description of every switch of SW3 and SW4, only table of factory default SW settings:
SW3[1-8] SW4[1-8] = 10101000 10000001
SW8[1-10] = 0000000000

Thanks,

Sergey

over 6 years ago

0 Yordan Kamenov over 6 years ago

TI__Mastermind 42515 points

Hi Sergey,

which SDK you use?

Regards,
Yordan

0 Sergey_Buloshnikov over 6 years ago in reply to Yordan Kamenov

Prodigy 70 points

Hi Yordan,

I use "PROCESSOR-SDK-LINUX-AUTOMOTIVE 03_02_00_03" that is downloaded from:
software-dl.ti.com/.../index_FDS.html

I used pre-built Linux Boot Partition and Linux Target FS in order to see first debugging information on terminal.

Regards,

Sergey

0 Stanislav Stilyanov over 6 years ago

TI__Genius 15120 points

Hi Sergey,
For sys_boot pin description, please refer to section 33.2.4 Sysboot Configuration in the DRA72x_DRA71x Technical Reference Manual.
Make sure you find out the correct mapping of the pins on the switches, and, as well, the switch polarity (ON=1=high --- OR --- ON=0=low) on your board.
It looks to me you are on option 'boot from SD card', then 'boot from USB', selected through sys_boot[5:0] = 010101. I.e. your switches are low-to-high [0-15], and the normal polarity - ON=high.

I'm not sure why SD card does not boot. Did you format the card with FAT32, with primary partition, and 'active bit' set?

Regards,
Stan

0 Sergey_Buloshnikov over 6 years ago in reply to Stanislav Stilyanov

Prodigy 70 points

Hi Stan,

The Reference Manual was very helpful for understanding pins combination.
On SD I made 2 primary partitions fat32 for boot and ext3 for rootfs.
What do you mean by 'active bit' ?

Regards,

Sergey

0 Stanislav Stilyanov over 6 years ago in reply to Sergey_Buloshnikov

TI__Genius 15120 points

Sergey,
A partition can be set to 'active' in your formatting tool. Many SD formatters do not support this. For example windows Disk Management does it with the right-click.
I'm not sure this is causing the problem but it is still a requirement in the TRM, so it is a good idea to try.
See below an excerpt from the TRM.

Regards,
Stan

"The eMMC / SD cards can hold a file system that the ROM code reads. The image used by the booting
procedure is taken from a booting file named MLO. This file must be in the root directory on an active
primary partition of type FAT12/16 or FAT32."

0 Sergey_Buloshnikov over 6 years ago in reply to Stanislav Stilyanov

Prodigy 70 points

Hi Stanislav,

I have already done this. In GParted app I added boot flag to the boot partition. Fdisk app does the same work.
The boot partition is of type FAT32 and defined as primary.
It not resolves the issue.

The P/N of our SDK is: EVMX777G-01-00-00-KIT.
Are there any features of working with this SDK?
We also can't specify the CPU P/N, we know only that it is from DRA71x series.

Regards,

Sergey

0 Stanislav Stilyanov over 6 years ago in reply to Sergey_Buloshnikov

TI__Genius 15120 points

Sergey,

You said previously that you a monitoring the serial console, however, did you try with HDMI cable to see if GUI appears.

regards,
Stan

0 Sergey_Buloshnikov over 6 years ago in reply to Stanislav Stilyanov

Prodigy 70 points

Hi Stan,

Serial console is the most basic thing for debugging. If it does not work how boot can come to the stage of GUI?

Regards,

Sergey

0 Sergey_Buloshnikov over 6 years ago in reply to Sergey_Buloshnikov

Prodigy 70 points

Eventually issue solved. All was about setting active partition and proper managing of partitions and file systems.
Fdisk in Linux doesn't do the work. Need to work with chain fdisk + mkfs.

Regards,

Sergey

0 Stanislav Stilyanov over 6 years ago in reply to Sergey_Buloshnikov

TI__Genius 15120 points

Sergey,

Glad to hear you have solved the issue.

I wanted to say in my previous post, that serial console may not show up for one reason or another, but the board actually boots fine. I just wanted to eliminate this possibility.

Best Regards,

Stan

Processors

Processors forum

DRA71XEVM: Board does not boot