SW Tools Solutions for DA8x. Linux by Degrees (updated) Part II

Transcription

1 SW Tools Solutions for DA8x Linux by Degrees (updated) Part II (Using Primus DSK LSP and MontaVista Pro Version 5.0) January 30, 2009 Joe George (with material stolen from all over) 1

2 Various Hints DSP TEXAS INSTRUMENTS TECHNOLOGY 2 8

3 Router Hints Switch easily between local and corporate networks by: In 1 PC Config (Corp) connect Ethernet drop to one of the LAN ports (so Corp DHCO). Thus: DVEVM and PC on Corporate Network (so you can get , print, etc.) Not isolated and might be slower If LAN then got Corp network access but some delay and certain local resources (i.e. DevRocket Target filesystem might not work) DSP TEXAS INSTRUMENTS TECHNOLOGY In 2 PC Config (Local) connect Ethernet drop to the WAN/Internet ports (so Router DHCP). Thus: DVEVM and 2 nd PC isolated on local network for speed First PC on Corporate Network (so you can get , print, etc.) and talk to DVEVM over COM1/Teraterm/Hyperterminal If WAN/Internet then local router with MAC address filtering isolates from Corp network, but tough to use Outlook, SNAP servers, and other network resources (turn off DHCP to keep your IT people happy, though turning back on DHCP will require a Router hard reset) 3 8

4 VMWare Hints With VM Player version VMware-player exe if you get the error on the left, then crank DOWN the memory below the Max recommended memory on the right. If anyone is using WinXP "hibernate" with VMWare open, don't do it! I hibernated and booted successfully multiple times. Then the one time when my laptop would not boot, the fresh boot would not open the.vmx file. Re-installing was not fun). DSP TEXAS INSTRUMENTS TECHNOLOGY 4 8

5 VMWare Hints Deep thoughts by Mohsen Khayami: The bridge option is that it act s like a hub and it does not change your IP address that you assign to the VMware. But with NAT(This is used when you are at home and are using the cable router with only one IP address) it does a translation on the address before it goes out to the network. My VMware with the load I had always came up with the NAT and I did not notice this until I had a bunch of problems with getting VMware to connect to the network. So now I can easily use samba server and able to transfer files between VMware and my PC by just using window explorer. 5

6 Build Hints uimage kernel and Decode app Bash shell is nice to debug build by writing outputs to file such as: make ARCH=arm CROSS_COMPILE=arm_v5t_le- uimage > output.txt Look for SYMLINK in Console to make sure correct davinci arch is generated SYMLINK include/asm-arm/arch -> include/asm-arm/arch-davinci Shortcut should show up like this in WinXP You must have uimage/kernal built to then use for app like decode./decoded2 -a data/sounds/davincieffect.aac gdb & 6

7 CCS Interaction Make DSP.wav player or port lab Due to codec engine errors with AAC decode, moved to all.x64p that copies a speech file. Used sphdec_copy to playback some audio content:./decoded2 -l -s sin.raw.g711 nogdb dspoff Putting it in CCS gives the above with KOV, memory, and some C source/function level debug DSP TEXAS INSTRUMENTS TECHNOLOGY 7 8

8 WinXP DaVinci Tips DevRocket + nfsaxe + Putty = Hello World nfsaxe allows WinXP NFS connection for DV EVM Note that C:\mvcyg4.0\home\a \workdir becomes /c/mvcyg4.0/home/a /workdir on Linux You MUST Add User Access for each directory nfsaxe On Target DVEVM you can easily mount :/c/mvcyg4.0/home/a /workdir /misc/winxpnfs DevRocket connects to the DVEVM with Target TCP/IP address and: Lets you browse the DaVinci filesystem (left where /misc/winxpnfs on DVEVM=C:\mvcyg4.0\home\a \workdir on WinXP) Lets you run Hello World (middle of screen) similar to PuttyTelnet window (upper right a little nicer than 8 Teraterm or Hyperterminal)

9 GUI based File Browsing DevRocket Hints To browse files on the on target Window->Show View->Other>-Target List View Put in Target IP Address (sometimes had trouble on Corp Network) Ignore RS-232 settings /misc/winxpnfs/decodeaac/demos/decode/debug/decoded 9

10 MV DevRocket Debug/Setup For Kernal Setup Brijesh, Good talking to you on the phone and thanks for the clarifications. For posterity (and things I might try), here are my notes: The below steps are for building file system from DevRocket only. 1. You can build kernel (uimage) from DevRocket, but need to pick File->New->Other->C/C++->Kernal Project. 2. TI supports Linux version of DevRocket only. 3. If not on the various VMWare images, you must install from MV Pro. 4. WinXP version might work. But a safer method (though 3. preferred) would be to File->Import the TI LSP. ps e kill -9 PID 10

11 CCS Interaction Hints DVEVM ARM works on CCS on lab laptop with SDUSB510GEL (ON OFF ON OFF ALLON). Then GEL -> "turn_on_dsp" followed by "GEL" -> "Release_DSP_Reset Works on BH (Rev D cable and Rev B) with laptop after fixing "the ICEPICK_C is set to XDS560 0 instead of BH560USBM 0" on regedit. Slow down TCLK in CCS setup? DSP TEXAS INSTRUMENTS TECHNOLOGY 11 8

12 Marketing Backup DSP TEXAS INSTRUMENTS TECHNOLOGY 12 8

13 Tools vs Target Bridging the Islands DaVinci ARM/Linux (Catalog ARM for Video) Traditional DSP Customers left on a island with DaVinci Tools Not a bad thing going after Linux/ARM market, but no bridge to/from embedded base -Do you know any DM642 customers porting to DaVinci? DaVinci videocentricity also limits customers -What DaVinci does a C6412 customer port to? Linux ARM market more comfortable with DM355 because NO DSP to deal with Make a bridge for DA8x customer using: Linux AND WinXP build platforms for target Linux (Montavista) Linux O/S Awareness in CCS debug (keep CCS WinXP only) BIOS on ARM (and start adding obvious drivers NDK, ATA/FAT32, etc.) Maybe it is time to rethink tools for our legacy and non-audio customers. DA8x ARM+DSP (Catalog ARM+DSP) DSPLINK? Tools O/S ARM Target O/S DSP Target O/S Linux AND WinXP build platforms Linux O/S Awareness in CCS debug BIOS on ARM Traditional TI DSP DaVinci ARM/Linux (Catalog ARM for Video) Windows (CCS) Linux (Red Hat 3 or 4, Suse) (and WinXP, too) Linux (MontaVista) BIOS (Linux - Virtuallogix) xdm/codec Engine Traditional TI DSP customers. DA8x ARM+DSP (Catalog ARM+DSP) Linux (Red Hat 3 or 4, Suse) and WinXP (CCS?) Linux (MontaVista) and BIOS on ARM? DSP/BIOS 13

14 Remember this picture (Ref Frmwrks)? Grow Your Own... alg too costly to develop too costly to enhance too costly to maintain TTO Technical Training Organization application application alg alg alg alg scheduler application scheduler application alg alg I/O alg DSP app + alg app + alga + algb +... app + sched + alga n + algb n +... app + sched + I/O + alga n + algb n +... app + sched + I/O + comm + alga n + algb n

15 Have we made development flow too hard? Traditional TI DSP customers. DaVinci ARM/Linux (Catalog ARM for Video) Customer Algorithm Drivers, framework, etc. O/S (or not) Development Tools Individual Development Time/Difficulty Development Timeline Customer Algorithm Drivers, framework, etc. O/S Development Tools Tools vs. Target Development Pyramid Traditional DSP Customers spend LESS of a ratio of development time on tools, O/S, etc. and MORE of a ratio of development time on their algorithms DaVinci (and even Performance Audio Framework) customers spend MORE of a ratio of development time on tools, O/S, etc. and spend LESS of a ration of development time on their algorithms. Again not a bad thing going after Linux/ARM market. LOTS of options for tools. O/S drivers., etc. But have we made development flow too hard? 15

16 DaVinci Traditional DaVinci Tool Summary DM644x Target Linux (ARM) DSP/BIOS (C64x+ DSP) Command Line (Linux) Compiler: GCC, MV-Pro? Debug: printf, GDB, KGDB? Build: gmake, xdm/rpc? GUI (Linux) Build/Compile/Debug: MV DevRocket?? CCS?? Command Line (Linux, Win) Compiler: TI Debug: printf, load6x Build: gmake, TImake GUI Build/Compile/Debug: CCS (Win) GreenHills Multi (Linux, Win) PA, Lester, Somnath, Yoshii-san, etc. have looked at the traditional DaVinci ARM/Linux for Cedia demo. 16

17 Operating Systems Tools Cost Total Size Tools O/S Target O/S Total Tools Tool Cost (Gigabyte) Total Time (Install) Traditional TI DSP WinXP BIOS CCS+XDS $3K+$2K= $5K = 1.5 GB = 0.6 hours DaVinci ARM/Linux (Catalog ARM for Video) Linux (Red Hat 3 or 4, Suse) MV Linux Linux + MV Linux $1K+$7K= $8K 15+2= 17 GB = 2.0 hours Linux + MV Linux + DaVinci ARM/Linux + 3rd Party Debug Linux (Red Hat 3 or 4, Suse) MV Linux GH Multi + GH Probe/XDS $1K+$7K+$15K+$2K= $25K = 18.1 GB = 2.5 hours DaVinci ARM/Linux WinXP MV Linux MV Linux $7K= $7K 2= 2 GB 5.0= 5 hours DaVinci ARM/Linux + 3rd Party Debug WinXP MV Linux MV Linux + GH Multi + GH Probe/XDS $7K+$15K+$2K= $24K = 3.1 GB = 5.5 hours DaVinci ARM/Linux + TI Debug?? WinXP MV Linux MV Linux + CCS+XDS $7K+$3K+$2K= $12K = 3.5 GB = 5.6 hours DA8x ARM+DSP (Catalog ARM+DSP) Linux (Red Hat 3 or 4, Suse) MV Linux Linux + MV Linux $1K+$7K= $8K 15+2= 17 GB = 2.0 hours DA8x ARM+DSP + 3rd Party Debug Linux (Red Hat 3 or 4, Suse) MV Linux Linux + MV Linux + GH Multi + GH Probe/XDS $1K+$7K+$15K+$2K= $25K = 18.1 GB = 2.5 hours DA8x ARM+DSP + 3rd Party Debug WinXP MV Linux MV Linux + GH Multi + GH Probe/XDS $7K+$15K+$2K= $24K = 3.1 GB = 5.5 hours MV Linux + DA8x ARM+DSP + TI Debug?? WinXP MV Linux CCS+XDS $7K+$3K+$2K= $12K = 3.5 GB = 5.6 hours DA8x ARM+DSP + TI Debug?? WinXP BIOS on ARM CCS+XDS $3K+$2K= $5K = 1.5 GB = 0.6 hours If Target development tools run under Windows, why use Linux as Tools O/S? Maybe it is time to rethink this for our legacy and non-audio customers. Key Cost Size Time CCS $3K XDS $2K Linux (Red Hat 3 or 4, Suse) $1K MV Linux (Pro for Linux) $7K 2 1 (5 for WinXP) GH Multi $15K Especially as cost as $$, Gigabytes, installation time, and learning curve all go up. 17