AM1806 u-boot board port

Moving this to the AM18X forum.

Hi Miroslav,

http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/p/312497/1091823.aspx#1091823

I have 2 queries for you based on your previous thread.

1) Have you tried serial flash utility to flash your u-boot into SPI?

I can't add AM1806 as "-flashType", is it Ok to put AM1808 as "-flashType" and change clock frequency of the processor to 300MHz?

2) Did you try "AM1808" as a "-targetType"  and not a "flashType"?

Ex:

In inux PC

mono ./sfh_OMAP-L138.exe -erase -flashType SPI_MEM -targetType AM1808    >>> To erase SPI flash

In windows PC

./sfh_OMAP-L138.exe -erase -flashType SPI_MEM -targetType AM1808  

In Linux PC

mono ./sfh_OMAP-L138.exe -flash_noubl u-boot.ais  -flashType NAND -targetType AM1808  >>> To flash AIS signed u-boot into SPI flash

In Windows PC

./sfh_OMAP-L138.exe -flash_noubl u-boot.ais  -flashType NAND -targetType AM1808

Go to u-boot source directory and do the following command to build u-boot:

make distclean ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-      >>> To Clean old configs

make clean ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-   >>> To Clean previous builded object files

make da850evm_config ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-  >>> To configure the u-boot source for "da850evm" board

make u-boot.ais ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-   >>> To build u-boot with AIS format

When I flash UBL.bin and u-boot.bin to SPI Flash and turn on board I got next message on serial port terminal:

You have to convert the u-boot.bin into AIS signed format to flash into SPI (plz follow above procedure)

You dont want to flash ubl instead you can use the above procedure to flash only u-boot with AIS signed format into SPI flash.

If you face any hang problem at "Waiting for SFT on the OMAP-L138..."  try all the target types like  OMAPL138, OMAPL138_LCDK, AM1808, AM1810,

Refer the below TI wiki links,

http://processors.wiki.ti.com/index.php/GSG:_DA8x/OMAP-L1/AM1x_DVEVM_Additional_Procedures

http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138

http://processors.wiki.ti.com/index.php/Running_PSP_Components_on_da850_Spectrum_Digital_EVM

Hi Stalin,

1) I changed device frequency to 300Mhz and set uart port to UART0 in serial flash and utility source code and I rebuild Serial flash utility. After that I had proper sfh and sft application. After that I used CCS to rebuild UBL. Again I used UART0 as debug port and 300MHz as processor frequency and I rebuild UBL source. To check is the sfh_OMAP-L138.exe working properly I connected my custom board with AM1806 via UART port to the PC host. I type sfh_OMAP-L138.exe -erase and everything goes well. That means my hardware and sfh are working.

2) I used am1808 as targetType, nothing chaged with that.

Today I made changes on several things in u-boot source.

In da850evm.h I changed:

/*
* Serial Driver info
*/
#define CONFIG_SYS_NS16550
#define CONFIG_SYS_NS16550_SERIAL
#define CONFIG_SYS_NS16550_REG_SIZE -4 /* NS16550 register size */
#define CONFIG_SYS_NS16550_COM1 DAVINCI_UART0_BASE /* It was UART2 but I need UART0*/
#define CONFIG_SYS_NS16550_CLK clk_get(DAVINCI_UART0_CLKID) 
#define CONFIG_CONS_INDEX 1 /* use UART0 for console */
#define CONFIG_BAUDRATE 115200 /* Default baud rate */
#define CONFIG_SYS_BAUDRATE_TABLE { 9600, 19200, 38400, 57600, 115200 }

...

/*
* Network & Ethernet Configuration
*/
#undef CONFIG_DRIVER_TI_EMAC /*it was #define but because AM1806 doesn't have EMAC I disable this*/ /*feature. Also UART0 pins and EMAC hardware pins has colision in PINMUX3 register*/
#ifdef CONFIG_DRIVER_TI_EMAC
#define CONFIG_MII
#undef CONFIG_DRIVER_TI_EMAC_USE_RMII
#define CONFIG_BOOTP_DEFAULT
#define CONFIG_BOOTP_DNS
#define CONFIG_BOOTP_DNS2
#define CONFIG_BOOTP_SEND_HOSTNAME
#define CONFIG_NET_RETRY_COUNT 10
#define CONFIG_NET_MULTI
#endif

In da850evm.c I changed:

/* UART0 pin muxer settings, settings was for UART2*/
const struct pinmux_config uart_pins[] = {
{ pinmux[3], 2, 4 },
{ pinmux[3], 2, 5 },
{ pinmux[3], 2, 6 },
{ pinmux[3], 2, 7 }
};

...

/*
* Power on required peripherals
* ARM does not have access by default to PSC0 and PSC1
* assuming here that the DSP bootloader has set the IOPU
* such that PSC access is available to ARM
*/
lpsc_on(DAVINCI_LPSC_AEMIF); /* NAND, NOR */
lpsc_on(DAVINCI_LPSC_SPI1); /* Serial Flash */
//lpsc_on(DAVINCI_LPSC_EMAC); /* disable this */
lpsc_on(DAVINCI_LPSC_UART0); /* enable UART0 instead of UART2*/
lpsc_on(DAVINCI_LPSC_GPIO);
#ifdef CONFIG_DAVINCI_MMC
lpsc_on(DAVINCI_LPSC_MMC_SD);
#endif

/* setup the SUSPSRC for ARM to control emulation suspend */
writel(readl(&davinci_syscfg_regs->suspsrc) &
~(DAVINCI_SYSCFG_SUSPSRC_EMAC | DAVINCI_SYSCFG_SUSPSRC_I2C |
DAVINCI_SYSCFG_SUSPSRC_SPI1 | DAVINCI_SYSCFG_SUSPSRC_TIMER0 |
DAVINCI_SYSCFG_SUSPSRC_UART0), /*it was UART2*/
&davinci_syscfg_regs->suspsrc);

...

/* enable the console UART0 */
writel((DAVINCI_UART_PWREMU_MGMT_FREE | DAVINCI_UART_PWREMU_MGMT_URRST |
DAVINCI_UART_PWREMU_MGMT_UTRST),
&davinci_uart0_ctrl_regs->pwremu_mgmt); 

In hardware.h I changed:

/* Emulation suspend bits */
#define DAVINCI_SYSCFG_SUSPSRC_EMAC (1 << 5)
#define DAVINCI_SYSCFG_SUSPSRC_I2C (1 << 16)
#define DAVINCI_SYSCFG_SUSPSRC_SPI0 (1 << 21)
#define DAVINCI_SYSCFG_SUSPSRC_SPI1 (1 << 22)
#define DAVINCI_SYSCFG_SUSPSRC_UART0 (1 << 18)
#define DAVINCI_SYSCFG_SUSPSRC_UART2 (1 << 20)
#define DAVINCI_SYSCFG_SUSPSRC_TIMER0 (1 << 27)

I rebuild u-boot with this settings and flash it together with UBL in SPI Flash memory using serial flash utility. Everything went well. After that I changed BOOT pins on custom board with AM1806 to boot from SPI1 Flash and I got next on my host terminal:

OMAP-L138 initialization passed!
Booting TI User Boot Loader
UBL Version: 1.65
Device OPP (300MHz, 1.2V)
UBL Flashtype: SPI
Starting SPI Memory Copy...
Valid magicnum, 0x55424CBB, found at offset 0x00010000.
DONE
Jumping to entry point at 0xC1080000.
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

I got some strange symbols after Jumping to entry point as 0x00010000. I think that now I enabled UART0 port but that the speed isn't 115200 baud and because of that I'm getting this characters. Every time when I press enter on my host keyboard I'm getting some strange characters on terminal, and I think that u-boot is working but that the communication speed is problem.

In UBL I set proccessor frequency to 300MHz. I didn't find that parameter in u-boot. Is it possible that the processor speed is not set to 300MHz in u-boot and because of that baud rate of UART0 is not 115200 baud?

Is somebody had the same problem?

Regards.

Hi Miroslav,

I have modified u-boot source for using UART0,

Please fins the attachment of modified u-boot source files,

7026.u-boot_uart0_mod.tar.gz

Please let me the know the result,

Hi Stalin,

I used files you changed and build u-boot from source again. Firstly I tried to rebuild u-boot-2010.12-psp03.21.00.04 version with files you changed. I had problem firstly with cpu.c file in:

int set_cpu_clk_info(void)
{
gd->bd->bi_arm_freq = clk_get(DAVINCI_ARM_CLKID) /   1000000;
/* DDR PHY uses an x2 input clock */
gd->bd->bi_ddr_freq = cpu_is_da830() ? 0 : (clk_get(DAVINCI_DDR_CLKID) / 1000000);
gd->bd->bi_dsp_freq = 0;
return 0;
}

The problem was with DAVINCI_DDR_CLKID and error log is below:

cpu.c: In function 'set_cpu_clk_info':
cpu.c:125: error: 'DAVINCI_DDR_CLKID' undeclared (first use in this function)
cpu.c:125: error: (Each undeclared identifier is reported only once
cpu.c:125: error: for each function it appears in.)
make[1]: *** [cpu.o] Error 1
make[1]: Leaving directory `/home/miroslav/Desktop/myskin_tools/sitara-board-port-uboot/arch/arm/cpu/arm926ejs/davinci'
make: *** [arch/arm/cpu/arm926ejs/davinci/libdavinci.o] Error 2

Than I put 0 instead of (clk_get(DAVINCI_DDR_CLKID) / 1000000) and build again. The build wasn't succeed but I got u-boot bin file.

da850_lowlevel.c: In function 'da850_ddr_setup':
da850_lowlevel.c:201: error: 'DDR_SLEW_DDR_PDENA_BIT' undeclared (first use in this function)
da850_lowlevel.c:201: error: (Each undeclared identifier is reported only once
da850_lowlevel.c:201: error: for each function it appears in.)
make[2]: *** [/home/miroslav/Desktop/myskin_tools/sitara-board-port-uboot/spl/arch/arm/cpu/arm926ejs/davinci/da850_lowlevel.o] Error 1
make[2]: Leaving directory `/home/miroslav/Desktop/myskin_tools/sitara-board-port-uboot/arch/arm/cpu/arm926ejs/davinci'
make[1]: *** [/home/miroslav/Desktop/myskin_tools/sitara-board-port-uboot/spl/arch/arm/cpu/arm926ejs/davinci/libdavinci.o] Error 2
make[1]: Leaving directory `/home/miroslav/Desktop/myskin_tools/sitara-board-port-uboot/spl'
make: *** [spl/u-boot-spl.bin] Error 2

Again I had problem with DDR parameter DDR_SLEW_DDR_PDENA_BIT.

I flashed u-boot I got in SPI Flash and power on processor. UBL start ok but after Jumping at entry point 0xc1080000 processor restart itself and UBL is started again and again.

After looking into changes you made for UART0 port I saw that only difference beetwen your and my files is in hardware.h file, parameter DAVINCI_UART0_CLKID = 0. I changed that in u-boot-2009.11-psp03.20.00.13 and build it. I got u-boot.bin without errors and after flashing it into SPI Flash, UBL start but after Jumping at entry point 0xc1080000 I got nothing, device stock here.

For which version of u-boot you made changes? Do you have any idea what can be a problem. For building u-boot I used ubuntu 10.04 and arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu sdk.

Regards Miroslav.

Hi Miroslav,

I have builded u-boot from "mcsdk_1_01_00_01" release,

My concern is that SDK is not a problem.

1) Please find the attachment of 2 files which include AIS format,

Rename the files like below and flash one by one & let me the results:

6404.u-boot.ais.txt

3731.u-boot_bin.txt

7343.u-boot_bin2.txt

u-boot.ais.txt --> u-boot.bin

u-boot_bin2.txt  --> u-boot.bin

u-boot_bin.txt ---> u-boot.bin

2) Flash only with u-boot (without ubl)  in AIS format on SPI flash.

You are hangout this memory address " Jumping to entry point at 0xC1080000."

So my suspection is that due to not using the AIS format (could not find u-boot with correct format)

Generally ubl & u-boot binaries has been used only when restoring is required.

Serial Flasher Options

There are three modes for using the serial flasher:

    Erase the target flash type - This will erase the entire contents of the flash.
        ..\sfh_OMAP-L138.exe -erase
    Flash the memory with a single application image - This will place an application image at address 0x0 of the flash. This must be an AIS format binary, which can be created with the AISgen utilities bundled with the Bootloader User Guide and associated files.
        ..\sfh_OMAP-L138.exe -flash_noubl <binary application file>
    Flash the memory with a UBL and application image - This will place a UBL at address 0x0 of the flash and an application image, such as u-boot, at address 0x10000. In general, a UBL is not required, and this mode is only used when restoring the default flash contents, as explained in the following section.
        ..\sfh_OMAP-L138.exe -flash <UBL binary file> <binary application file>

Refer the below link,

3) Remove your ubl binary & flash your u-boot with AIS format as i said old reply

./sfh_OMAP-L138.exe -flash_noubl u-boot.ais  -flashType SPI_MEM -targetType AM1808

Note:

Here plz mention "-flash_noubl" with AIS signed format

Q1) Is there any specifc reason to use UBL ?

When I flash UBL.bin and u-boot.bin to SPI Flash and turn on board I got next message on serial port terminal:

Q2) How do you flashing ubl  & u-boot  into SPI flash ?

Q3) Have you tried/used AIS signed binaries before for ubl or u-boot ?

To know more please refer the below link.

http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138

Hi Stalin,

firstly thank you very much for trying to help me.

I will use files you sent me and I will test my device with them as soon as possible.

A1) There is no specific reason to use UBL, I'm really new in these waters and I read a bunch of tutorials and guides how to make my hardware to work. In some of these guides I read that I need UBL first and because of that I use it.

A2) For flashing UBL & u-boot into SPI Flash I use Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138. Because I'm used UART0 port for debug, firstly I re builded Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138 with settings for UART0 debug port and than I enable UART0 boot mode and than I used sfh_OMAP-L138.exe to flash UBL & u-boot to SPI Flash. After booting the device from UART0, I got progerss bar with download information. When the programming is complete 100% I got confirmation that programming is successful.
A3) I didn't used AIS binaries for ubl or u-boot before.

I will test bin files you sent me and give you feedback soon.

Regards. Miroslav.

Hi Stalin,

I test bin files you sent me.

First file:

terminal window looking like this in programming process:

C:\flasher\OMAP-L138_FlashAndBootUtils_2_40\OMAP-L138\GNU>sfh_OMAP-L138.exe -flash_noubl u-boot.ais -flashType SPI_MEM -targetType AM1808
-----------------------------------------------------
TI Serial Flasher Host Program for OMAP-L138
(C) 2014, Texas Instruments, Inc.
Ver. 1.67
-----------------------------------------------------

Platform is Windows.
[TYPE] Single boot image
[BOOT IMAGE] u-boot.ais
[TARGET] AM1808
[DEVICE] SPI_MEM
[SPI Block] 0

Attempting to connect to device COM1...
Press any key to end this program at any time.

(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 9012-Byte section to address 0x80000000.
(AIS Parse): Processing command 1: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 748-Byte section to address 0x80002334.
(AIS Parse): Processing command 2: 0x58535906.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Performing jump and close...
(AIS Parse): AIS complete. Jump to address 0x80000000.
(AIS Parse): Waiting for DONE...
(AIS Parse): Boot completed successfully.

Waiting for SFT on the OMAP-L138...

Flashing application u-boot.ais (222824 bytes)

100% [ ████████████████████████████████████████████████████████████ ]
Image data transmitted over UART.

100% [ ████████████████████████████████████████████████████████████ ]
Application programming complete

Operation completed successfully.

After changing the dip switch position to boot from SPI Flash, in terminal window which is connected to UART0 port of processor nothing happened. I'm powering board from laboratory power supply and I mentioned that with this binary current consumption going from 28mA to 60mA. It's look like that board start to boot and then for some reason reset is occurred. 

With second image you sent me again nothing happened in terminal, and current is constantly 28mA

C:\flasher\OMAP-L138_FlashAndBootUtils_2_40\OMAP-L138\GNU>sfh_OMAP-L138.exe -flash_noubl u-boot.bin -flashType SPI_MEM -targetType AM1808
-----------------------------------------------------
TI Serial Flasher Host Program for OMAP-L138
(C) 2014, Texas Instruments, Inc.
Ver. 1.67
-----------------------------------------------------

Platform is Windows.
[TYPE] Single boot image
[BOOT IMAGE] u-boot.bin
[TARGET] AM1808
[DEVICE] SPI_MEM
[SPI Block] 0

Attempting to connect to device COM1...
Press any key to end this program at any time.

(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 9012-Byte section to address 0x80000000.
(AIS Parse): Processing command 1: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 748-Byte section to address 0x80002334.
(AIS Parse): Processing command 2: 0x58535906.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Performing jump and close...
(AIS Parse): AIS complete. Jump to address 0x80000000.
(AIS Parse): Waiting for DONE...
(AIS Parse): Boot completed successfully.

Waiting for SFT on the OMAP-L138...

Flashing application u-boot.bin (190056 bytes)

100% [ ████████████████████████████████████████████████████████████ ]
Image data transmitted over UART.

100% [ ████████████████████████████████████████████████████████████ ]
Application programming complete

Operation completed successfully.

With third image again the processor going from try to boot to reset state, current going from 28mA to 60mA.

C:\flasher\OMAP-L138_FlashAndBootUtils_2_40\OMAP-L138\GNU>sfh_OMAP-L138.exe -flash_noubl u-boot1.bin -flashType SPI_MEM -targetType AM1808
-----------------------------------------------------
TI Serial Flasher Host Program for OMAP-L138
(C) 2014, Texas Instruments, Inc.
Ver. 1.67
-----------------------------------------------------

Platform is Windows.
[TYPE] Single boot image
[BOOT IMAGE] u-boot1.bin
[TARGET] AM1808
[DEVICE] SPI_MEM
[SPI Block] 0

Attempting to connect to device COM1...
Press any key to end this program at any time.

(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 9012-Byte section to address 0x80000000.
(AIS Parse): Processing command 1: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 748-Byte section to address 0x80002334.
(AIS Parse): Processing command 2: 0x58535906.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Performing jump and close...
(AIS Parse): AIS complete. Jump to address 0x80000000.
(AIS Parse): Waiting for DONE...
(AIS Parse): Boot completed successfully.

Waiting for SFT on the OMAP-L138...

Flashing application u-boot1.bin (222824 bytes)

100% [ ████████████████████████████████████████████████████████████ ]
Image data transmitted over UART.

100% [ ████████████████████████████████████████████████████████████ ]
Application programming complete

Operation completed successfully.

I'm using AM1806 processor. I saw that EMAC and UART0 use same pins pinmux(3) - 4 and 5. Did you undef use EMAC in u-boot source before build? Is this can be the problem because processor is reseting?

Regards. M. 

Hi Miroslav,

I gave 2 files (u-boot.ais & u-boot_bin2.txt)  with AIS formated binaries to you which you mentioned resetting is happening because of the EMAC periph, and 3rd file is simple binary (u-boot.bin) which you said nothing is happening.

So, Build u-boot yourself with AIS formatted, mean while i ll update you modifed u-boot AIS binary,

Building u-boot source with AIS format:

make u-boot.ais ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

It wil provide you u-boot.ais as well as u-boot.bin

Use AIS formated u-boot binary & let me the know the result..

Note:

change "CROSS_COMPILE" for your toolchain.

Please continue the same procedure to load u-boot.ais file to SPI.

C:\flasher\OMAP-L138_FlashAndBootUtils_2_40\OMAP-L138\GNU>sfh_OMAP-L138.exe -flash_noubl u-boot.ais -flashType SPI_MEM -targetType AM1808

Hi Stalin,

I tried what you said to me. Firstly I rebuild uboot.ais without emac. I #undef CONFIG_DRIVER_TI_EMAC, #undef CONFIG_CMD_NFS and change board.cfg by delete option MAC_ADDR_IN_SPIFLASH for da850evm config. After that I successfully rebuild u-boot and I got u-boot.ais. I build u-boot.ais for DAVINCI_UART0_CLKID = 0, and for DAVINCI_UART0_CLKID = 2. Than I used procedure you told me to flash u-boot ais to spi flash. After that for first case  DAVINCI_UART0_CLKID = 0 after power on the board, current is 64mA but nothing is receive on my host terminal. For second case DAVINCI_UART0_CLKID = 2 the processor going from try to boot to reset state, current going from 28mA to 60mA.

I can't realise what is the problem. In attach you can find files I changed to enable UART0 console.

 6472.u-boot.rar

One more time, my hardware consist of:

AM1806 Sitara processor 300MHz

TPS65070 PMIC

Micron MT46H64M16LFBF-6 IT

M25P64-VME6TG SPI Flash

Everything is connected according to AM1808eXperimenter evm design from logic PD except UART port, I used UART0 instead of UART2.

Regards. Miroslav.

Hi Miroslav,

Can you please configure your u-boot source for am18x & do changes for UART0, EMAC then build it and run .

Do the following commands,

make clean  ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

make distclean  ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

make da850_am18xxevm_config  ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

make u-boot.ais  ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

Let me know the result,

Hi Stalin,

I solved the problem.

As you know, first problem was with pinmux for EMAC and UART0. I solved that with your help and thank you very much for that. After that I had a problem with processor reset. I used one of processor gpio pin as SoftReset signal and the problem was that in initialization process the logic state of the pin was high and it caused processor reset. After power on the hardware, SoftReset pin was high Z state, but after that when u-boot start I found that it's went to high state and reset the processor. After cutting that trace on PCB I got working u-boot.

Next thing is porting and building linux for my hardware. I hope that I will find good reference guide to do that. I don't have EMAC to transfer uImage on SDcard but I hope that I will find the way how to do that without it, using only host pc and sdcard.

If you have some advice for future work I'd be happy to listen.
Once more time thank you very much for helping me.

Best regards Miroslav.

Hi,

I am trying to use the u-boot version 2014.01 on OMAPL138. I followed the README.davinci and created u-boot.ais image. Now when I flash this onto SPIflash, I get messages

U-Boot SPL 2014.01 (Mar 11 2014 - 16:38:20)

continuously.

Please provide me info on what is missing.

thanks

sangeeta

Hi Sangeeta,

Can you please create a new thread for this issue as posting on the same thread will get only less attention when compared to the new one. And as well, this thread seems to be a closed one.