Project

General

Profile

MityDSP-L138 Boot Problem

Added by Anton Kitai over 7 years ago

We are using the L138-FX-225-RC on a new custom baseboard and are having trouble with boot:
- no UART activity in normal SPI boot
- UART boot mode sends "BOOTME"
We attempted to erase and flash the bootloader using the WinCE boot package contents and instructions:
- running "sfh_OMAP-L138.exe erase -p COM1" shows expected activity until erasing progress bar appears, then hangs at 0% complete.
running "sfh_OMAP-L138.exe -flash -p COM1 -appStartAddr 0xc7f60000 -appLoadAddr 0xc7f60000 arm-spi-ais.bin EBOOTSPIFLASH.nb0" shows expected activity, transfers image, but hangs at writing flash progress bar.

There are no other peripherals connected to SPI1 data, clock, or SCS0 signals, or to I2C0. We are using the LCD interface, but the LCD is not connected during these tests. Probing SPI1_SCS0 shows change from 3.3V to ~1.7V at the time when the flash is being accessed - should this not be ~0V? Are there any other interface signals that could cause this problem?

Thanks,
Anton


Replies (1)

RE: MityDSP-L138 Boot Problem - Added by Anton Kitai over 7 years ago

This issue has been resolved - we had left an uterminated SPI1_CLK signal trace on our base board at an unpopulated device.
Anton

    (1-1/1)
    Go to top
    Add picture from clipboard (Maximum size: 600 MB)