CCS/TMS320F28379D: Serial Flash Programmer Attempting Autobaud to load kernel

Furkan YUMBUL

Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hi,

I try to test SCI flash kernel example using serial flash programmer. The program stucks on "attempting autobaud to load kernel" message. I am using controlCARD docking station with F2837x Controlcard.

Before running serial flash programmer, I power off device and controlCARD docking station to reset.

The blink_dc_cpu01.txt and F2837xD_sci_flash_kernels_cpu02.txt files which are in c2000 serial flash programmer file.

What can be problem ?

Thanks and regards.

over 6 years ago

0 Sal Pezzino over 6 years ago

TI__Mastermind 32995 points

Hi,

It appears the SCI connection is not correct.

You need to confirm that you are using the right SCI pins. The bootloader uses 2 SCI pins. Make sure you are connected to the SCI pins which the bootloader boot mode option is using.

You can check your connection with the SCI echoback example in C2000Ware.

On your board, you may need to use the alternate SCI boot mode if the default SCI boot mode pins are not pinned out to the USB connector.

sal

0 Furkan YUMBUL over 6 years ago in reply to Sal Pezzino

Intellectual 360 points

Hi Sal,

Are these pins boot mode pins (S1) or any other GPIO pins ?

For S1 pins on GPIO72 = 0 GPIO84 = 1 currently. And the F2837x Controlcard is connected to controlCARD docking station. Both of F2837x Controlcard and controlCARD docking station are connected to PC with two different USB cables.

0 Sal Pezzino over 6 years ago in reply to Furkan YUMBUL

TI__Mastermind 32995 points

Hi Furkan,

I am not referring to the GPIO72/84 pins. Those are the boot mode select pins used to select the boot mode. You do need to make sure they select the SCI boot mode you want.

But, I mean that you have to make sure the SCI boot loader pins are the pins you are trying to use for SCI communication.

sal

0 Furkan YUMBUL over 6 years ago in reply to Sal Pezzino

Intellectual 360 points

Thanks a lot Sal. How can I use these pins ? What should I do ?

0 Sal Pezzino over 6 years ago in reply to Furkan YUMBUL

TI__Mastermind 32995 points

I am not sure what you are asking...

What GPIO pins is the SCI boot loader using?
What GPIO pins are you trying to use for SCI communication on your board?

sal

0 Furkan YUMBUL over 6 years ago in reply to Sal Pezzino

Intellectual 360 points

Hi Sal,

I tried the sci_echoback example. I sent some characters via PuTTY. And I received successfully.

Also I used SCI_BOOT_ALTERNATE(GPIO28-GPIO29) instead of SCI_BOOT(GPIO84-GPIO85) in flash kernel example.After I converted the out file for kernel format using hex2000. But the sci flash kernel program still stucks at "attempting autobaud to load kernel message."

Do you refer SCITXDA and SCIRXDA pins ? In TRM, they are GPIO84 and GPIO85.

You said that SCI connection is not correctly. What kind of connection should I do ? I am using hardware like below. And both of them are connected to PC via mini-USB cables. I didn't make any other connections other than this.

0 Sal Pezzino over 6 years ago in reply to Furkan YUMBUL

TI__Mastermind 32995 points

When you boot the device to SCI boot mode which runs the SCI bootloader, the SCI bootloader is using different SCI pins then you are connected to.

Please make sure the bootloader and the kernel are using the same pins which you are using (28/29).

sal

0 Furkan YUMBUL over 6 years ago in reply to Sal Pezzino

Intellectual 360 points

In sci_echoback example, SCI communication uses (28/29) pins. And it works successfully. So, I should use (28/29) pins in kernel,right ?

0 Sal Pezzino over 6 years ago in reply to Furkan YUMBUL

TI__Mastermind 32995 points

Yes. But the default SCI boot mode does not use 28/29.

You need to use the alternate SCI boot mode.

OR you need to use the default SCI boot mode and switch to using GPIO84/85 in the kernel and in your connections.

sal

0 Furkan YUMBUL over 6 years ago in reply to Sal Pezzino

Intellectual 360 points

I tried both of GPIO pins (28/29, 84/85) in kernel code, for both situations the program still stucks on "attempting autobaud load to kernel" message.