trying to flash DM355EVM software to custom board

Jorge15379

Other Parts Discussed in Thread: TLV320AIC33

Hi,

I am trying to use the EVM default demo software as a quick validation for my own board. My board differs from the EVM in that no ethernet is available, and a different NAND (Numonyx 1Gb) and video decoder is being used.

I have been successful in programming the EVM software to my board using the Serial Flash Loading Utility

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

However, when I try to boot from flash, the system shows the following info and then freezes:

--------------------------------------

Valid magicnum, 0xA1ACED66, found in block 0x00000019.

DONE

Jumping to entry point at 0x81080000.

U-Boot 1.2.0 (Feb 2 2008 - 23:52:10)

DRAM: 128 MB

NAND: NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3

,3V 8-bit)

Bad block table found at page 65472, version 0x01

Bad block table found at page 65408, version 0x01

No NAND device found!!!

128 MiB

*** Warning - bad CRC or NAND, using default environment

In: serial

Out: serial

Err: serial

ARM Clock :- 216MHz

DDR Clock :- 171MHz

Hit any key to stop autoboot: 0

BOOTP broadcast 1

----------------------------------------

I have noticed that the device ID for the flash indicates a different Flash than the one I am using:

The device id detected 1F is for a 32 pages per block, 2048bytes per page memory, however the Datasheet of the Numonyx NAND I am using says that the memory is a 32 pages per block, 512 bytes per page.

Please let me know if what I am trying to do is unfeasible, or if you can suggest me any modifications to this approach to make this work.

Thanks!

over 15 years ago

0 Bernie Thompson TI over 15 years ago

TI__Mastermind 41665 points

I am guessing you are using the UBL and U-Boot images that were built for the EVM?

Jorge said:
Hit any key to stop autoboot: 0

At this point in the boot, if you hit a key can you actually get to the U-Boot prompt? Assuming so I am somewhat interested in your boot arguments, due to the next message.

Jorge said:
BOOTP broadcast 1

If this is the final message, there is a good chance the lock up is stemming from a lack of Ethernet hardware, as this message indicates it is trying to obtain network information via DHCP, I am not sure what happens when you don't have an external EMAC hooked up to the EMIF.

In general you may have to modify the U-Boot sources to take out any dependencies that it has on the EVM, likely adjusting how it manages flash, and ensuring that it does not get hung on the network side of things.

0 Jorge15379 over 15 years ago in reply to Bernie Thompson TI

Prodigy 250 points

Hi Bernie,

Thank you so much for your help. Yes I am using the UBL nad U-boot images (with the encode decode demos) that are available for the EVM.

I have tried different environments with varying results:

-------------------------------------------------------------------------------------

1) The defaul environment is the following:

bootargs=ip=dhcp mem=120M console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x82000000,4M

bootcmd=dhcp;tftpboot 0x82000000 initrd.image;setenv addip setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname)::off eth=$(ethaddr) video=dm64xxfb:output=$(videostd);run addip;bootm 0x80700000 bootdelay=3

baudrate=115200

bootfile="uImage"

stdin=serial

stdout=serial

stderr=serial

videostd=ntsc

THIS GIVES THE RESULT THAT I POSTED BEFORE.

------------------------------------------------------------------------------------------------------------------------------------

2) The suggested environment in the EVM getting started guide with the small modification of turning IP off.

bootargs console=ttyS0,115200n8 ip=off root=/dev/mtdblock3 rw rootfstype=yaffs2 mem=120M video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=(videostd)

bootcmd 'nboot 0x80700000 0 0x400000; bootm'

THE RESULT OF THIS ENVIRONMENT WAS AN INVALID MAGIC NUMBER WHEN LOOKING FOR CODE FROM THE NAND:

DM35x initialization passed!

TI UBL Version: 1.50

Booting Catalog Boot Loader

BootMode = NAND

Starting NAND Copy...

Valid magicnum, 0xA1ACED66, found in block 0x00000019.

DONE

Jumping to entry point at 0x81080000.

U-Boot 1.2.0 (Feb 2 2008 - 23:52:10)

DRAM: 128 MB

NAND: NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3

,3V 8-bit)

Bad block table found at page 65472, version 0x01

Bad block table found at page 65408, version 0x01

No NAND device found!!!

128 MiB

In: serial

Out: serial

Err: serial

ARM Clock :- 216MHz

DDR Clock :- 171MHz

Hit any key to stop autoboot: 0

Loading from NAND 128MiB 3,3V 8-bit, offset 0x400000

** Bad Magic Number 0xa1aced66 **

## Booting image at 80700000 ...

Bad Magic Number

DM355 EVM #

--------------------------------------------------------------------------------------------------------------

3) A modified version of the default environment without IP arguments (at least those I though were IP related)

bootcmd=bootm 0x80700000 bootdelay=3

baudrate=115200

bootfile="uImage"

stdin=serial

stdout=serial

stderr=serial

videostd=ntsc

bootcmd=bootm 0x80700000 bootdelay=3

THE RESULT OF THIS WAS A BAD MAGIC NUMBER AS WELL (SAME PROMPT OUTPUT AS OPTION NUMBER 2)

--------------------------------------------------------------------------------------------------------------

I am aware the I have modified several variable at a time so I may have changed something that I shouldn't have.

Is there any useful information here???

Is there any documentation available that can help me understand how to handle the environments in u-boot???

Thanks,

Jorge

0 Josef Kohler12051 over 15 years ago

Intellectual 655 points

Jorge said:

Valid magicnum, 0xA1ACED66, found in block 0x00000019.

DONE

Jumping to entry point at 0x81080000.

U-Boot 1.2.0 (Feb 2 2008 - 23:52:10)

DRAM: 128 MB

NAND: NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3

,3V 8-bit)

Is this realy not the device you are using? If not: Is your device supported by DM355?

Jorge said:

Bad block table found at page 65472, version 0x01

Bad block table found at page 65408, version 0x01

No NAND device found!!!

Looks goot until here.

You can change this by modifying "CFG_MAX_NAND_DEVICE" in u-boot-source-dir/include/configs/davincie_dm355.h, so u-boot will no longer search for a second NAND device.

Jorge said:

128 MiB

*** Warning - bad CRC or NAND, using default environment

this happens on first boot up. use "saveenv" command in u-boot and this message will be gone

Jorge said:

BOOTP broadcast 1

typical error when your network isnt set up correctly. try using static ip like A.4.4 in Getting Started Guide describes.

Jorge said:

Loading from NAND 128MiB 3,3V 8-bit, offset 0x400000

** Bad Magic Number 0xa1aced66 **

## Booting image at 80700000 ...

Bad Magic Number

this means that your Linux image is corrupted/not present

0 Jorge15379 over 15 years ago in reply to Josef Kohler12051

Prodigy 250 points

Hi Josef, Thank you so much,

Turns out my supplier gave me a slightly different memory from the one I requested. Both are supported so that was not the issue. The issue was that my image was corrupted.

I think I fixed it (partially). The board is now "partially" booting It loads most of the kernel but it panics at some point. It gives me a lot of warnings most of them caused by the differences between my board and the EVM.

The message I get at the end is the following:

"Warning: Cannot create /dev/console: -2Warning: unable to open an initial console.

Kernel panic - not syncing: No init found. Try passing init= option to kernel."

Could you please tell me what could cause this?

Many thanks,

Jorge

0 Jorge15379 over 15 years ago in reply to Jorge15379

Prodigy 250 points

Hi, Thank you so much for your help.

I am still stuck with the Kernel Panic. I have found that similar errors may be caused by:

1) Incompatible filesystem.

2) Corrupt Kernel/

3) Filesystem not at mount point.

However most of the posts I found deal with booting from NFS which is not available in my system (My system does not have ethernet, nor audio).

Before the Kernel panics I get a couple of warning related with the console. Is that possibly related?

Here is the boot sequence:

"DM35x initialization passed!

TI UBL Version: 1.50

Booting Catalog Boot Loader

BootMode = NAND

Starting NAND Copy...

Valid magicnum, 0xA1ACED66, found in block 0x00000019.

DONE

Jumping to entry point at 0x81080000.

U-Boot 1.2.0 (Feb 2 2008 - 23:52:10)

DRAM: 128 MB

NAND: NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3

,3V 8-bit)

Bad block table found at page 65472, version 0x01

Bad block table found at page 65408, version 0x01

No NAND device found!!!

128 MiB

In: serial

Out: serial

Err: serial

ARM Clock :- 216MHz

DDR Clock :- 171MHz

Hit any key to stop autoboot: 0

Loading from NAND 128MiB 3,3V 8-bit, offset 0x400000

Image Name: Linux-2.6.10_mvl401

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1578988 Bytes = 1.5 MB

Load Address: 80008000

Entry Point: 80008000

## Booting image at 80700000 ...

Image Name: Linux-2.6.10_mvl401

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1578988 Bytes = 1.5 MB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux.............................................................

Linux version 2.6.10_mvl401 (a0868396@gtcmbuild3.gt.design.ti.com) (gcc version

3.4.3 (MontaVista 3.4.3-25.0.104.0600975 2006-07-06)) #1 Sat Feb 2 23:59:35 EST

2008

CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)

CPU0: D VIVT write-back cache

CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets

CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets

Machine: DaVinci DM355 EVM

Memory policy: ECC disabled, Data cache writeback

DM0350

Built 1 zonelists

Kernel command line: console=ttyS0,115200n8 ip=off root=/dev/mtdblock3 rw rootfs

type=yaffs2 mem=116M video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K

:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch

0_mode=(videostd)

PID hash table entries: 512 (order: 9, 8192 bytes)

Console: colour dummy device 80x30

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Memory: 116MB = 116MB total

Memory: 114176KB available (2748K code, 570K data, 180K init)

Mount-cache hash table entries: 512 (order: 0, 4096 bytes)

CPU: Testing write buffer coherency: ok

spawn_desched_task(00000000)

desched cpu_callback 3/00000000

ksoftirqd started up.

desched cpu_callback 2/00000000

desched thread 0 started up.

NET: Registered protocol family 16

DaVinci: 104 gpio irqs

Registering platform device 'serial8250.0'. Parent at platform

Registering platform device 'musb_hdrc'. Parent at platform

Registering platform device 'nand_davinci.0'. Parent at platform

Registering platform device 'dm9000.0'. Parent at platform

Registering platform device 'mmc.0'. Parent at platform

Registering platform device 'mmc.1'. Parent at platform

DaVinci I2C DEBUG: 23:57:20 Feb 2 2008

Registering platform device 'i2c'. Parent at platform

ch0 default output "COMPOSITE", mode "NTSC"

VPBE Encoder Initialized

LogicPD encoder initialized

SCSI subsystem initialized

usbcore: registered new driver usbfs

usbcore: registered new driver hub

musb_hdrc: version 2.2a/db-0.4.8 [cppi-dma] [host] [debug=0]

musb_hdrc: ConfigData=0x06 (UTMI-8, dyn FIFOs, SoftConn)

musb_hdrc: MHDRC RTL version 1.300

musb_hdrc: USB Host mode controller at c7802000 using DMA, IRQ 12

musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

DaVinci I2C WARNING: i2c: NACK detected

Registering platform device 'dm_spi.0'. Parent at platform

NetWinder Floating Point Emulator V0.97 (double precision)

yaffs Feb 2 2008 23:56:53 Installing.

Initializing Cryptographic API

Registering platform device 'davincifb.0'. Parent at platform

davincifb davincifb.0: dm_osd0_fb: Initial window configuration is invalid.

davincifb davincifb.0: dm_osd0_fb: 720x576x16@0,0 with framebuffer size 2025KB

davincifb davincifb.0: dm_vid0_fb: Initial window configuration is invalid.

davincifb davincifb.0: dm_vid0_fb: 720x576x16@0,0 with framebuffer size 2500KB

davincifb davincifb.0: dm_osd1_fb: 720x480x4@0,0 with framebuffer size 1350KB

davincifb davincifb.0: dm_vid1_fb: Initial window configuration is invalid.

davincifb davincifb.0: dm_vid1_fb: 720x576x16@0,0 with framebuffer size 2500KB

watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec

Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled

Registering platform device 'serial8250'. Parent at platform

ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A

ttyS1 at MMIO 0x1c20400 (irq = 41) is a 16550A

ttyS2 at MMIO 0x1e06000 (irq = 14) is a 16550A

io scheduler noop registered

io scheduler anticipatory registered

RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize

loop: loaded (max 8 devices)

dm9000 Ethernet Driver

dm9000: read wrong id 0x2b2a2928

dm9000: wrong id: 0x2b2a2928

dm9000: not found (-19).

i2c /dev entries driver

Linux video capture interface: v1.00

Registering platform device 'vpfe.1'. Parent at platform

vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded

Registering platform device 'DavinciDisplay.1'. Parent at platform

Trying to register davinci display video device.

layer=c0bf3c00,layer->video_dev=c0bf3d64

Trying to register davinci display video device.

layer=c0bf3a00,layer->video_dev=c0bf3b64

davinci_init:DaVinci V4L2 Display Driver V1.0 loaded

ipipe major#: 254, minor# 0

Registering platform device 'dm355_ipipe.2'. Parent at platform

ipipe driver registered

af major#: 253, minor# 0

Registering platform device 'dm355_af.2'. Parent at platform

aew major#: 252, minor# 0

Registering platform device 'dm355_aew.2'. Parent at platform

elevator: using anticipatory as default io scheduler

nand_davinci nand_davinci.0: Using 4-bit hardware ECC

NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3,3V 8-b

it)

nand_bbt: ECC error while reading bad block table

Creating 5 MTD partitions on "nand_davinci.0":

0x00000000-0x003c0000 : "bootloader"

0x003c0000-0x00400000 : "params"

0x00400000-0x00800000 : "kernel"

0x00800000-0x20800000 : "filesystem1"

mtd: partition "filesystem1" extends beyond the end of device "nand_davinci.0" -

- size truncated to 0x7800000

0x20800000-0x08000000 : "filesystem2"

mtd: partition "filesystem2" is out of reach -- disabled

nand_davinci nand_davinci.0: hardware revision: 2.3

dm_spi.0: davinci SPI Controller driver at 0xc7862000 (irq = 42) use_dma=0

Initializing USB Mass Storage driver...

usbcore: registered new driver usb-storage

USB Mass Storage support registered.

usbcore: registered new driver usbhid

drivers/usb/input/hid-core.c: v2.0:USB HID core driver

mice: PS/2 mouse device common for all mice

mmc mmc.0: Supporting 4-bit mode

mmc mmc.0: Using DMA mode

mmc mmc.1: Supporting 4-bit mode

mmc mmc.1: Using DMA mode

Registering platform device 'davinci-audio.0'. Parent at platform

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 0

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 42

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 51

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 65

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 86

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 93

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 37

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 8

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 15

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 16

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 47

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 64

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 82

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 92

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 19

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 22

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 17

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 18

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 26

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 27

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 28

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 29

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 30

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 31

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 43

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 44

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 25

NET: Registered protocol family 2

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 8192 bind 16384)

Initializing XFRM netlink socket

NET: Registered protocol family 1

NET: Registered protocol family 10

IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

yaffs: dev is 32505859 name is "mtdblock3"

yaffs: Attempting MTD mount on 31.3, "mtdblock3"

block 957 is bad

block 958 is bad

block 959 is bad

block 960 is bad

VFS: Mounted root (yaffs2 filesystem).

Freeing init memory: 180K

Warning: Cannot create /dev/console: -2Warning: unable to open an initial consol

Kernel panic - not syncing: No init found. Try passing init= option to kernel."

The boot variables from u-bot are:

"bootcmd=nboot 0x80700000 0 0x400000; bootm

"bootargs=console=ttyS0,115200n8 ip=off root=/dev/mtdblock3 rw rootfstype=yaffs2 mem=116M video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x57 6x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=(videostd) stdin=serial stdout=serial stderr=serial videostd=ntsc"

Please let me know if there is anything you can suggest me. Thanks,

Jorge

0 Josef Kohler12051 over 15 years ago in reply to Jorge15379

Intellectual 655 points

Jorge said:

Registering platform device 'davinci-audio.0'. Parent at platform

DaVinci I2C WARNING: i2c: NACK detected

DaVinci I2C WARNING: i2c: NACK detected

DaVinci I2C WARNING: i2c: NACK detected

DaVinci I2C WARNING: i2c: NACK detected

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

aic33 write failed for reg = 0

DaVinci I2C WARNING: i2c: NACK detected

DaVinci I2C WARNING: i2c: NACK detected

DaVinci I2C WARNING: i2c: NACK detected

DaVinci I2C WARNING: i2c: NACK detected

DaVinci I2C WARNING: i2c: NACK detected

i2c write: error = -121

tlv320aic33_write_value: aic33 write failed

no sound device present, rebuild your kernel without sound support

Jorge said:

yaffs: dev is 32505859 name is "mtdblock3"

yaffs: Attempting MTD mount on 31.3, "mtdblock3"

block 957 is bad

block 958 is bad

block 959 is bad

block 960 is bad

VFS: Mounted root (yaffs2 filesystem).

4 bad blocks in a row? no other bad blocks? sounds unusual. how did you flash your filesystem?

Jorge said:

Warning: Cannot create /dev/console: -2Warning: unable to open an initial consol

e.

Kernel panic - not syncing: No init found. Try passing init= option to kernel."

could be a problem with your filesystem, as you said.

0 Jorge15379 over 15 years ago in reply to Josef Kohler12051

Prodigy 250 points

Thanks a lot.

I am working on that removing the software components that are not present in hardware .

In the mean time here is the info you asked.

flashed everything through UART.

For U-boot I used the TI Serial Flashing utilities from http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility

For the image I used Ymodem, and then nand write. My NAND is 128MB. Here are the specifics:

"loady 0x80700000 115200

nand erase 0x400000 0x200000

nand write 0x80700000 0x400000 0x200000"

Does the environment I posted earlier fits the board configuration?

Thanks,

Jorge

0 Josef Kohler12051 over 15 years ago in reply to Jorge15379

Intellectual 655 points

Jorge said:

For U-boot I used the TI Serial Flashing utilities from http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility

For the image I used Ymodem, and then nand write. My NAND is 128MB. Here are the specifics:

"loady 0x80700000 115200

nand erase 0x400000 0x200000

nand write 0x80700000 0x400000 0x200000"

This is only how you flash your Linux Kernel which seems to work fine. How did you flash your filesystem?

Jorge said:

Does the environment I posted earlier fits the board configuration?

Yes it looks good

Processors

Processors forum

trying to flash DM355EVM software to custom board