When i interfaced the board with the PC, set it in UART boot mode and
then on the UartHost i got a no. of message saying "Loading boot
table" and at the end "JUMP TO address 0x80000000". it would wait here
for sometime (timeout) and then show a "Closing COM1"
I used the AISgen to operate on a uboot that i compiled. And then used
this file in the Uarthost program i got the following stuff.
>(File IO): Read 414952 bytes from file C:\u-boot_AIS.bin.
>(Serial Port): Opening COM1 at 115200 baud...
>(AIS Parse): Waiting for BOOTME... (power on or reset target now)
>(AIS Parse): BOOTME received!
>(AIS Parse): Executing function...
>(AIS Parse): Executing function...
(IT WAITED FOR A VERY LONG TIME HERE, AND THEN)
>(AIS Parse): Boot aborted.
>(Serial Port): Closing COM1.
Repeatedly it kept giving me this status.
Again, i tried the program in linux (Fedora 9) where i had already
installed the mono packages,
used the OMAP-L138_FlashAndBootUtils_2_10.tar.gz file to get the
AISgen and UART_Host
The AISgen was located in:
/root/Download/OMAP-L138_FlashAndBootUtils_2_10/OMAP-L138/GNU/
AISUtils/
edited the OMAP-L138.ini in the same folder (with relevant reg values
as per that mentioned on the hawkboard site; attached with this mail)
command to run the AISgen
#> mono HexAIS_OMAP-L138.exe -ini /root/Download/OMAP-
L138_FlashAndBootUtils_2_10/OMAP-L138/GNU/AISUtils/OMAP-L138.ini -
otype binary /root/Documents/workdir/u-boot
>OUTPUT ON TERMINAL as follows:
>
>-----------------------------------------------------
> TI AIS Hex File Generator for OMAP-L138
> (C) 2010, Texas Instruments, Inc.
> Ver. 1.17
>-----------------------------------------------------
>
>
>Begining the AIS file generation.
>AIS file being generated for bootmode: UART.
>Parsing the input object file, ARM_AISExtra_OMAP-L138.out.
>Parsing the input object file, /root/Documents/workdir/u-boot.
>AIS file generation was successful.
>Wrote 414952 bytes to file u-boot.bin.
>Conversion is complete.
>
>
After this i started the Uart_host as follows:
#> mono UartHost.exe
Then pointing to the proper file and COM port in the GUI, i got the
following messages.
>(File IO): Read 414952 bytes from file /root/Documents/workdir/u-boot.bin.
>(Serial Port): Opening /dev/ttyS0 at 115200 baud...
>(AIS Parse): Waiting for BOOTME... (power on or reset target now)
>(AIS Parse): BOOTME received!
>(AIS Parse): Executing function...
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(Serial Port): Read error! (The operation has timed-out.)
>(AIS Parse): I/O Error in read!
>(AIS Parse): Opcode Sync failed after 11 consecutive I/O failures.
>(AIS Parse): Boot aborted.
>(Serial Port): Closing /dev/ttyS0.
After all this i am still not able to load the uboot...
Am i doing something wrong here, or is there some hardware problem.
Awaiting your reply
Sachin
sachin
On Feb 4, 7:46 am, Stuart Gray <stuar...@gmail.com> wrote:
> Hi Sachin,
>
> I had the same problem with Windows Vista. I had to switch to use an older
> XP machine.
>
> I cannot sa anything about using Linux as I haven't tried this yetbut it
> seems to me that it would be the best route forward as I am sure we all
> develop on Linux and it would be easier to keep everything in that
> environment.
>
> Sorry I cannot give you an answer, but try another Windows machine if you
> can with an older OS.
>
> Hope this helps,
> Stuart
>
> > Sachin- Hide quoted text -
>
> - Show quoted text -
it also says
U-Boot 2009.01-dirty always withe some locations as bad
U-Boot 2009.01-dirty (Nov 18 2009 - 23:30:48)
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xa1 (Micron NAND
128MiB 1,8V 8-bit)
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x008a0000
nand_read_bbt: Bad block at 0x014e0000
128 MiB
*** Warning - bad CRC or NAND, using default environment
In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 150000000 Hz
Ethernet PHY: GENERIC @ 0x07
and thus unable to load u-boot
please help
sachin
> > - Show quoted text -- Hide quoted text -
For Bad Blocks, the blocks shown your log doesn't affect u-boot
locations. ( 0 - 70000)
Regards,
Khasim
please go through my post down and for your ref. i am copying the part
of said post again here
On Feb 5, 9:52 am, "Syed Mohammed, Khasim " <sm.kha...@gmail.com>
wrote:
> I did forward a tool for command line to the list, please see through
> if that helps.
>
> http://sourceforge.net/projects/dvflashutils/files/OMAP-L138/v2.10/OM...