AM3359ZCZ issue having

Jason Teoh

Hi Guys,

I had a concern on the AM3359ZCZ.

We have built 4 prototype boards with beagle board BONE as reference. We tried to power up the board and it’s not able to boot through the UART.

Currently our prototype have the following SYSBOOT pin configured.

SYSBOOT[15:14]	SYSBOOT[13:12]	SYSBOOT[11:10]	SYSBOOT[9]	SYSBOOT[8]	SYSBOOT[7:6]	SYSBOOT[5]	SYSBOOT[4:0]	Boot sequence
01b = 24MHz	00b	00b	0 = ECC done by ROM	0 = 8-bit device	this two pin NC	1 = CLKOUT1	000010b	1. UART0 2. SPI0 3. NAND 4. NANDI2C

We have verified our power up sequence as inside the AM335x datasheet page 91 - 95.

We are able to probe the following behavior from the IC:

CLKOUT1 : this output pin have a 24MHz clock transmitting from it, prove that the IC has powered up.
nRESETIN_OUT : this output have the behaviour stated in “8.1.1.7.14 PORz Sequence” of the technical manual.

For a normal boot process from UART0, the UART0 TXD will be transmitting a “C” character. We are unable to observe the event, either in console terminal or oscilloscope.

Any idea of what is the problem the IC is not transmitting “C”?

Regard's

Jason

over 13 years ago

0 peaves over 13 years ago

TI__Guru 62855 points

I do not think your issue is related to the state of SYSBOOT[7:6], but it is not a good pratice to leave these inputs floating.

The CLKOUT1 output being present does not indicate the processor is executing code. CLKOUT1 is just a buffered output of the OSC0 reference clock and hardware enables this output mode without any intervention of the processor.

Verify all power supplies inputs. For example, another customer recently discovered the PLL power supply pins were not sourced on his custom board design.

Regards,
Paul

0 Jason Teoh over 13 years ago in reply to peaves

Intellectual 400 points

Hi Paul,

We are using the JTAG to check the status of the chips. Using the XDS100V2, it fail to connect to the custom board and AM335x EVM.

We have setup the connection from the JTAG to our target board (AM335x EVM) by connecting the TI-20 connector to the target board.

By running the CCSv5, we are able to detect the JTAG, but connecting to the target board will yield the following error.

Below is the error message for running the CCSv5.

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.

This utility will load the adapter 'jioserdesusb.dll'.

The library build date was 'Dec 19 2011'.

The library build time was '21:32:12'.

The library package version is '5.0.569.0'.

The library component version is '35.34.39.0'.

The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-180' (0xffffff4c).

The title is 'SC_ERR_CTL_NO_TRG_POWER'.

The explanation is:

The controller has detected a target power loss.

The user must turn-on or connect the power supply for the target.

[End]

This error is the same error even there is no target connected to the JTAG.

Our current connection between the JTAG to the EVM is Pin to Pin connection ( Pin 1 to Pin 1, and etc.)

From the XDS100 schematic, the JTAG connector is 20-PIN TI, the EVM schematic is having the same 20-PIN TI connector as well.

Is there anyone you can link up to help us on the issue? Please advise.

0 peaves over 13 years ago in reply to Jason Teoh

TI__Guru 62855 points

I have minimum knowledge about CCS. Therefore, I will not be able to answer your last question.

Hopefully one of the software guys can chime in and help you.

Regards,
Paul

Processors

Processors forum

AM3359ZCZ issue having