Hello,
I installed the EZSDK and built an image by following "EZ Software Developer Guide.pdf". ( and booted from an SD image which contains the newly built image. )
Now, what I want to do is to try some source code, build it and try to debug it to get familiar with the environment.
However, I'm stuck with very early stage.
Here are my goals and problems I see.
1. Goal
Would like to boot from Linux kernel is either from TFTP or SD image and mount a file system on a directory on my Linux host. According to the document, it's said "NSF mounting" or something like that in the document.
2. Problems
I believe that setup is easier to develop S/W for. By issuing "setup.sh" in a ti-ezsdk)dm816x-evm..." directory, it allowed to set those : where a linux image is ( either TFTP or SD card ) and where a file system is ( SD card and NFS ). After doing that, as a last step, it invoked a minicom with setup_uimage-tftp_fs-nfs.minicom. But it hangs there.
I confirmed that the serial connection is established Ok by booting from a bundled SD card and I could connect from a Windows host over RS-232C.
But if I do it on a Linux ( living in a Virtual Box ), it doesn't /dev/ttyS0 was changed to /dev/ttyO2 and tried it, but it didn't work also. In one of the document, in recent SDK, ttyS0 is changed to ttyO2. Anyway, the setup.sh said it would automatically detect a right one. but it hangs. I checked if ttyO2 was really there in /dev but it didn't. Probably ttyO2 is a kind of alias in TI's environment setup script. Am I right?
I figured out that the port is not /dev/ttyS0, but /dev/ttyUSB0, because I use a USB->Serial cable.Although the VirtualBox setting is COM6 ( which is the recognized COM port on Windows side. ) and assigned it as COM1, inside of Linux, it is only recognized when /dev/ttyUSB0 is used. Then I need to map ttyUSB0 to ttyO2, right?
When using a sample SD card, I could connect it on a Linux (in a virtualBox) using /dev/ttyUSB0.
However, when it is turned off and the SD card is pulled out and turned on ( hoping that it is to be booted from TFTP and the NFS fileshare on the Linux), it didn't look to be booted correctly. I can't see any prompt when using minicom or Windows based terminal program. Can you tell me what to do?
Additionally, according to the document, it said :
"Boot the Linux file system from your development host using NFS. On your development host the
Linux target file system is located at ${HOME}/targetfs" -- from the Software Developer Guide
But when I looked up "T181XX_PSP_U-Boot.pdf" or "T181XX_PSP_User_Guide.pdf", there doesn't look to have any special dip switch setting for NFS boot. Actually there are only NOR/NAND/SPI/UART/SD/EMAC boot options for SW3 and SW4.
Proably it is UART because UART is a chip for RS232C? But anyway, it's not clear. So, if there is a dip switch setting, what is it?
Also, according to the "U-Boot.pdf", it says :
"Note: Uboot supports only Ethernet on Port 1 (J14), Port 2 (J27) is not supported in current release. ( on page 30, U-Boot Network configuration )"
However, on a DaVinci board, there is no J27 port. I have J10 and J10 Ethernet port. The J10 is on a mainboard on which an ARM processor is, while J14 is on its daughter board.
However, when I used a sample SD card, it's the J10 ethernet port is enabled and gets IP address from my NAT box.
So, are you sure only J14 is allowed for "SDK" although the built image enables "J10"?
Or does it just happen to contain sentence for older board?
Is the document up-to-date?
Please, somebody turn a guiding light for me.
Thank you.