TMS320F28375D: Failed setting full clock on custom board

I presume you have no issues whatsoever with using INTOSC1 as the clock source and you only face issues with the external crystal.

Can you provide the file reference (along with the complete path) for the SysCtl_setClock(DEVICE_SETCLOCK_CFG) function?

I doubt if connecting the VSSOSC to GND will actually prevent the connection of the CCS debugger. When the connection failed, did you probe the crystal pins to see if it is actually oscillating?

I just used a dma example from C2000Ware, and modified it for 20MHz crystal. Any other example behaves the same, and as seen in referenced topic, even Uniflash shows errors during FLASH and CRC opperations until clock divider is set provide 50MHz.

DISCONNECTING VSSOSC from GND prevents JTAG operations.

I will try to check oscillator with scope later today. Thank you.

Oleg Kobrin said:

I just used a dma example from C2000Ware, and modified it for 20MHz crystal.

Please provide the file reference (along with the complete path) for the SysCtl_setClock(DEVICE_SETCLOCK_CFG) function. 

Oleg Kobrin said:

DISCONNECTING VSSOSC from GND prevents JTAG operations.

It appears there is some hardware issue on your board.

Here I include the design files, Altium Designer format.

СРДН 127 510 001 Плата кондуктометра (05.03.2022 21-18-31).zip

Please send the schematics in PDF format. Also, please try an example from C2000ware. You could try something simple like

C:\ti\c2000\C2000Ware_4_00_00_00\driverlib\f2837xd\examples\cpu1\gpio\gpio_ex2_toggle.c

I tryed the example, it behaves in the same way.

СРДН 127 510 001 Плата кондуктометра.pdf

The C2000ware examples are tested examples. If they don't work, then definitely there is some issue with the hardware. 

I still don’t have an answer to my request "Please provide the file reference (along with the complete path) for the SysCtl_setClock(DEVICE_SETCLOCK_CFG) function." 

You also have not confirmed if everything works fine with INTOSC. 

I noticed one thing. You are using a 5v CAN transceiver. This is a violation of the datasheet specifications, specifically VIH. This is a 1.2v core, 3.3v I/O device. No I/O pin of this device can be driven in excess of VDDIO.

Of course, there are some hardware problem, so I ask for help to find what is it.

Sorry, I do not understand the request. SysCtl_setClock(DEVICE_SETCLOCK_CFG) is the function defined in device/device.c copied from dac example from C2000Ware. 

As for INTOSC - I will difinitely try it as I will visit my office next time, maybe tomorrow. Also I'll remove TJA1050 from the board (it can be easily replaced by SN65HVD230D later), it may be a clue, but we never had any problems with it before using it with other 3.3v MCUs.

I wil write upon getting any results. Thank you.

Hello!

Just set the clock sourse to INTOSC1, got the same error.

Removed the TIA1050, same error.

The SysCtl_setClock() is defined in C:\ti\c2000\C2000Ware_3_04_00_00\driverlib\f2837xd\driverlib\sysctl.h

Oleg Kobrin said:

Of course, there are some hardware problem, so I ask for help to find what is it.

We can provide  some guidance and tips but our ability to debug H/W problems remotely is very limited.  

Oleg Kobrin said:

Just set the clock sourse to INTOSC1, got the same error.

That is strange and indicates that the problem may not be related to the crystal oscillator as you had been thinking. 

Oleg Kobrin said:

Removed the TIA1050, same error.

I didn't mean to say that the TJA1050 is the cause of the error. I just noticed it and wanted to alert you that it is a violation of the datasheet specifications. That's all. 

Oleg Kobrin said:

but we never had any problems with it before using it with other 3.3v MCUs.

It is possible that those MCUs have 5v tolerant I/Os. This MCU does not.

Oleg Kobrin said:

The SysCtl_setClock() is defined in C:\ti\c2000\C2000Ware_3_04_00_00\driverlib\f2837xd\driverlib\sysctl.h

Request you to install C2000Ware v4.00_00_00 and try an example from C2000ware itself. Try a simple example like GPIO toggle.

Hareesh Janakiraman said:

Request you to install C2000Ware v4.00_00_00 and try an example from C2000ware itself. Try a simple example like GPIO toggle.

Will do today. But with 3_04_00_00 works well with LAUNCHXL_F28379D.

Anyway it's difinitely a hardware issue, as Uniflash also causes same errors unless I set /8 divider in FLASH settings.

Can you use the Launchpad crystal value in your board also? That way, the clock circuit becomes identical. Typically, issues surface when the clock frequencies at various stages violates the ranges shown in the datasheet. Not only is there a MIN & MAX value for the device system clock, you also need to meet the MIN & MAX values for the system PLL output. See page 66 of www.ti.com/lit/SPRS880. 

I do not have 10MHz crystall here, so I just removed crystall from the board. Switched to C2000Ware v4.00_00_00 too.

Same error.

If C2000ware examples themselves don’t work on your board, I am afraid there is not much I can do to help. See if you can resolve JTAG connectivity issues with https://www.ti.com/lit/pdf/spracf0 .

I know this is a hardware problem. So I seek here help to resolve it. Difinitely, there is no JTAG problem, as device stops working right upon setting the clock without JTAG - I did some tests.

As clarified before, our ability to help with H/W problems are limited. I regret I am unable to help.

In this case I just replaced 0.1 capacitors with 4.7. It is total of 42.3uF, and datasheet recomends at least 20uF of total capacitance.

Looks like the core is quite noisy, and require enough decopling capacitance. I think it is common for c2800 cores.