Is Ubuntu Linux distribution available for DM8148 or DM8168 kit?

DM8148 and DM8168 PSP is developed for Ubuntu Linux.  Please download its EZSDK from its product folder for detail.

Regards,

Viet

Hi Vancouver,

            The EZSDK releases target the Ubuntu Linux distribution and the same can be downloaded from http://software-dl.ti.com/dsps/dsps_public_sw/ezsdk/latest/index_FDS.html

Regards,

N.S.SriHarsha

Do you mean I can run Ubuntu 10.04 in DM8148 EVM? I plan to run Ubuntu in DM8148 EVM, but I can not find someone introduce how to do that.

Yes, you can. I did it before. You'll need to enable inotify  in the Kernel Filesystem support, otherwise Ubuntu's udev won't work right.

I posted some time ago how to get a Ubuntu ARM rootfs using rootstock (RootfsFromScratch). The problem I had with an Ubuntu Rootfs is that I was not able to use
the CMEM kernel module (C6Run, C6accel, ...)  as it would not insert it correctly, while it worked with the Arago(busybox) rootfs. I don't know if the error was due to precompiled
ARM(armv7) rootstock packages, since the kernel log only suggested problems when looking up certain adresses while inserting the module. Sometimes when you used different address ranges I was able to insert the module, but it crashed as soon as you used it (including the kernel).

I used the RFS over NFS. Furhtermore I couldn't get the kernel debugger (CS arm gcc toolchain) to work over the serial (altough I disabled session(getty) and kernel output on ttyO0).

But Syslink and the standard VPSS modules worked.

So besides the instructions in link above you'll need to:

• Enable inotify support in the kernel (rebuild the kernel) if you need udev
• Specify the serial line  if you want to be able to login on the serial console (see rootstock manpage, I think its --serial ttyO0)
• How to build the kernel and setup U-Boot or an SD-card, can be found in the EZSDK and PSP guides

This was with EZSDK <=5.02 and PSP <=....05.

Regards Markus

Markus,  I will try to use rootstock with TI's kernel. Thanks.

Regards,

Steve tsai 

Couple of more things

1. Under /etc/init, you will need to add a ttyO2.conf file to enable the uart console. You will need to refer the existing ttyXX.conf files for details

2. If you are planning to run x-windows then syslink, firmware and the vpss kernel objects would need to be loaded before runlevel 5.

Again these are things that I have tried and found to work, in general, but not fully tested or supported.

We already could run Ubuntu in DM8148 EMV and we are trying to start gstreamer plugin with OpenMAX in Ubuntu. We built gstreamer plugin and run gst-launch, but we got error in xdc.runtime package. Does anyone succeed to run gstreamer-plugin in Ubuntu? 

Anybody has got the graphic UI such as nano-X runing on ubuntu, on DM8148 kit?

Greetings,

I am fairly new at building custom kernel and never try to put and rootfs together.

I tried building ubuntu with ezsdk 5_03_01_15 and psp04.01.00.06.patch2 and I can't get this to work on a 8148 evm.

This are probably basic questions but I am stuck. Would someone post step by step or give more details instructions on how to get this to work?

I am using the following command for rootstock.

sudo rootstock --fqdn 8148evm --login username  --password temppwd --imagesize 4G ----seed ubuntu-server,build-essential,openssh-server,linux-image-omap

As soon as I add inotify (CONFIG_INOTIFY_USER=y) to the kernel .config seems to stop booting right after my rootfs mount over nfs. Then I took the rootstock fs out of the picture and I can't even get the system to come up when

Also I had to comment out this line of the main EZSDK makefile, because it wipes my changes kernel .config

linux:
#       $(MAKE) -C $(LINUXKERNEL_INSTALL_DIR) $(LINUXKERNEL_BUILD_VARS) $(DEFAULT_LINUXKERNEL_CONFIG)
        $(MAKE) -C $(LINUXKERNEL_INSTALL_DIR) $(LINUXKERNEL_BUILD_VARS) uImage
        $(MAKE) -C $(LINUXKERNEL_INSTALL_DIR) $(LINUXKERNEL_BUILD_VARS) modules

when i do make all everything looks fine, but on make install i get this errors.

install: cannot stat `/home/rbuteau/ti-ezsdk_dm814x-evm_5_03_01_15/component-sources/linuxutils_3_21_00_04/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.ko': No such file or directory
make: *** [cmem_install] Error 1

with rootstock fs:

VFS: Mounted root (nfs filesystem) on device 0:14.                              
devtmpfs: mounted                                                               
Freeing init memory: 200K                                                       
init: ureadahead main process (58) terminated with status 5                     
init: procps main process (86) terminated with status 255                       

With EXSDK/busybox filesystem:

VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing init memory: 200K
INIT: version 2.86 booting
Please wait: booting...
Error opening /dev/fb0: No such file or directory
Starting udev
udevd (82): /proc/82/oom_adj is deprecated, please use /proc/82/oom_score_adj i.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
EXT3-fs (mmcblk0): error: can't find ext3 filesystem on dev mmcblk0.
EXT2-fs (mmcblk0): error: can't find an ext2 filesystem on dev mmcblk0.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
ISOFS: Unable to identify CD-ROM format.
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
Root filesystem already rw, not remounting
Caching udev devnodes
ipv6: disagrees about version of symbol module_layout
ALSA: Restoring mixer settings...
NOT configuring network interfaces: / is an NFS mount
No state is present for card EVM
Found hardware: "" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card EVM
Fri Dec  9 18:22:00 UTC 2011
INIT: Entering runlevel: 5
Loading HDVICP2 Firmware
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
        PRCM for IVHD0 is in Progress, Please wait.....  
                        BW Phy Addr : 0x48180600 Data : 0x00000001
                        AW Phy Addr : 0x48180600 Data : 0x00000002
                        Phy Addr : 0x48180c04 Data : 0x00000037
                        BW Phy Addr : 0x48180620 Data : 0x00070000
                        AW Phy Addr : 0x48180620 Data : 0x00050002
                        BW Phy Addr : 0x48180624 Data : 0x00030000
                        AW Phy Addr : 0x48180624 Data : 0x00010002
                        Phy Addr : 0x48180600 Data : 0x00000102
                        BW Phy Addr : 0x48180c10 Data : 0x00000007
                        AW Phy Addr : 0x48180c10 Data : 0x00000003
                        Phy Addr : 0x48180c14 Data : 0x00000004
                        BW Phy Addr : 0x58088000 Data : 0xd03a0eaf
                        AW Phy Addr : 0x58088000 Data : 0xeafffffe
                        BW Phy Addr : 0x58098000 Data : 0xf8fcd895
                        AW Phy Addr : 0syslink: disagrees about version of symbt
x58098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180c10 Data : 0x00000003
                        AW Phy Addr : 0x48180c10 Data : 0x00000000
                        Phy Addr : 0x48180c14 Data : 0x00000007
        PRCM for IVHD0 is Done Successfully  
PRCM Initialization completed
FATAL: Error inserting syslink (/lib/modules/2.6.37/kernel/drivers/dsp/syslink.t

@Richard:

I'm not sure about linux-image-omap, because I don't know what this package includes. The rest looks fine except you need to specify the serial device on which the system takes over after the kernel finished booting. getty spawns on this serial line and will provide the shell login.

you either edit the config files of the rootfs (don't know the name right now) or rebuild the fs with --serial ttyO2 (I think that's the default on the evm). Be aware that newer versions of Ubuntu need the FS inotfy support, but you enabled that already. I didn't manage to get cmem working correctly on ubuntu, but I think others did.

You can build the module separately and look if it is at the location the makefile expects it to be. On the other hand you could skip it and copy it manually.

Regards,

Markus

Hey ,

i'm using this line to do capture from DM8148 , i'm streaming the capture data into windows pc .

streaming line is :

gst-launch v4l2src device="/dev/video0" always-copy=false queue-size=12 num-buffers=2000 ! 'video/x-raw-yuv-strided,format=(fourcc)NV12,width=1280,height=720,framerate=(fraction)25/1' ! omxbufferalloc numBuffers=12 ! omx_h264enc bitrate=5000000 ! gstperf ! h264parse output-format=0 ! rtph264pay ! udpsink host=192.168.16.106 port=5000

receiving line is :

gst-launch-0.10 udpsrc port=5000 ! 'application/x-rtp, media=(string)video, clock-rate=(int)90000, payload=(int)96' ! rtph264depay ! ffdec_h264 ! xvimagesink sync=false

the receiving line works great on linux system , but on windows system it doesn't

I got Ubuntu to come up with rootstock but I am missing most of the non arm changes.

If I tried  the command line above on the normal EZSDK rootfs I get this.

root@dm814x-evm:~# uname -a
Linux dm814x-evm 2.6.37 #1 Fri Dec 9 17:17:52 IST 2011 armv7l unknown

root@dm814x-evm:~# gst-launch v4l2src device="/dev/video0" always-copy=false que
ue-size=12 num-buffers=2000 ! 'video/x-raw-yuv-strided,format=(fourcc)NV12,width
=1280,height=720,framerate=(fraction)25/1' ! omxbufferalloc numBuffers=12 ! omx_
h264enc bitrate=5000000 ! gstperf ! h264parse output-format=0 ! rtph264pay ! udp
sink host=192.168.0.103 port=5000                                               
WARNING: erroneous pipeline: no element "omxbufferalloc"   

root@dm814x-evm:

Richard:

I am facing the same problem of "init: ureadahead main process (58) terminated with status 5 ", do you mind sharing how you fixed this problem?

I didn't. I am using RDK now instead of EZSDK.