• State Resolved
  • Locked Locked
  • Replies 32 replies
  • Subscribers 102 subscribers
  • Views 7178 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

k2 66AK2H12 evm mpmcl cannot load dsp .out file?

steve zhang
Expert 1690 points
Other Parts Discussed in Thread: 66AK2H12

hi,ti experts:

Now I run demos on 66AK2H12 evm,but I have problem.like below:

when I run demo_ipc.sh in the directory  

/usr/share/matrix-gui-2.0/apps/demo_ipc/

the content of the demo_ipc.sh was like this :

mpmcl  reset dsp0

...................

mpmcl  reset dsp7

mpmcl  load  dsp0   a.out

 ............................

mpmcl  load  dsp7   a.out

mpmcl   run dsp0

.......................................

mpmcl   run dsp7

I get many errors! I cannot understand how to slove these errors! thank you very much!

errors:

Loading DSP Images
Resetting core 0...
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
reset failed (error: 0)
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
status failed
Resetting core 1...
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
reset failed (error: 0)
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
status failed
Resetting core 2...
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
reset failed (error: 0)
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
status failed
Resetting core 3...
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
reset failed (error: 0)
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
status failed
Resetting core 4...
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
reset failed (error: 0)
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
status failed
Resetting core 5...
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
reset failed (error: 0)
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
status failed
Resetting core 6...
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
reset failed (error: 0)
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
status failed
Resetting core 7...
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
reset failed (error: 0)
can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
status failed

  • 0
    TI__Guru 50170 points

    Hi, Steve,

    I think your mpmsrv is not running or for some reason, it didn't get autostarted. You should see the following during Linux boot up in the console. What version of the MCSDK are you running, I am running 3.0.1.12.

    NIT: Entering runlevel: 5
    Starting system message bus: dbus.
    Starting Dropbear SSH server: dropbear.
    Starting mpmsrv daemon.
    Starting telnet daemon.

    Rex

  • 0 in reply to Rex Chang
    Expert 1690 points

    Rex:

    thx!

    1.

    I didn't see any infos you supplied above during Linux boot up in the console

    2.

    the old kernel images - supplied with EVM,run mpmcl ok.and had no infos

    you supplied above. like below. why the kernel I build myself no work?why

    mpmcl didn't run ok with the kernel build myself.

    Loading DSP Images
    Resetting core 0...
    reset succeeded
    dsp0 is in reset state
    Resetting core 1...
    reset succeeded
    dsp1 is in reset state
    Resetting core 2...

  • 0 in reply to Rex Chang
    Expert 1690 points

    Rex：

    Following your advice, I stop and start mpmsrv-daemon manually.and then I

    run mpmcl reset  or load or run . But Errors remained.The steps I carried out.

    step1:

    /etc/init.d/mpmsrv-daemon.sh  stop      

    then display:

    Stopping mpmsrv daemon

    step2:

    /etc/init.d/mpmsrv-daemon.sh  start

    then display:

     Starting mpmsrv daemon

    step3:

    ./demo_ipc.sh

    then display:

    Loading DSP Images
    Resetting core 0...
    Timeout in reading from socket
    reset failed (error: 0)
    can't send data to /var/run/mpm/mpm_daemon (error: Connection refused)
    status failed

  • 0 in reply to steve zhang
    Guru 13915 points

    Steve,

    Are you running this EVM:

     

    http://www.advantech.com/Support/TI-EVM/EVMK2HX.aspx

    ? 

    Regards,
    johnw 

  • 0 in reply to John Westmoreland43
    TI__Guru 50170 points

    Hi, Steve,

    You can manually run /usr/bin/mpmsrv to see if the server started and if mpmcl works. "ps -ef" would show you if mpmsrv process is running. Did you get the kernel from arago git server? What version are you building? How about the file system? Prebuild? Which MCSDK release is it from?

    Rex

  • 0 in reply to Rex Chang
    Expert 1690 points

    Rex:

    1.

    I did follow your advice,I use "ps -aux" and it show that  mpmsrv daemon process

    is running.but when I run demo_ipc.sh,failed again.

    2.

    kernel source code was downloaded from arago git server,The Version was

    linux-3.8.4-dirty.

    3.

    tisdk-rootfs.cpio.gz   was the rootfs which was supplied in the folder

    C:\ti\mcsdk_linux_3_00_01_12\images by EVM

    4.

    MCSDK  3_00_01_12  was downloaded from www.ti.com

     

  • 0 in reply to steve zhang
    TI__Genius 9065 points

    Steve,

    I think if we can send a complete log from power on to failure, it will hep to debug. Once powered on, stop the autoboot and do a printenv and then boot.

    regards,

    David

  • 0 in reply to dzhou
    Expert 1690 points

    dzhou said:

    Steve,

    I think if we can send a complete log from power on to failure, it will hep to debug. Once powered on, stop the autoboot and do a printenv and then boot.

    regards,

    David

    hi David:

    I posted console infomation in the attached files.including:

    1.printenv  info

    2.kernel boot info

    3.after kernel boot

    Any help would be greatly appreciated!

  • 0 in reply to dzhou
    Expert 1690 points

    dzhou said:

    Steve,

    I think if we can send a complete log from power on to failure, it will hep to debug. Once powered on, stop the autoboot and do a printenv and then boot.

    regards,

    David

    Sorry! David

    forget to attached files right now.

  • 0 in reply to steve zhang
    TI__Guru 50170 points

    Hi, Steve,

    How did you build your kernel? Do you make any changes to the kernel configuration? What version of tool chain do you use? If you did make changes to the kernel, does it work with your kernel build without any changes?

    Rex

  • 0 in reply to Rex Chang
    Expert 1690 points

    Rex:

    I did make changes when building kernel.When I build.the errors below occured.

    No rule to make target 'net/netfilter/xx_CONNMAK.o' , needed by 'net/netfilter/built-in.o'

    so I made menuconfig and I deleted "netfilter" module.

    My toolchain was  Linaro GCC v4.7 (2013.03-20130313).

     

  • 0 in reply to John Westmoreland43
    Guru 13915 points

    Hmm, ever wonder if you are being ignored???  

    EVMK2HX HW and SW Revision Matrix

     EVM  Revision  SN Range  Ship Date  PCB Rev 
     DSPM8305E    		  BMC 
     Rev    		  IBL/POST 
     Rev    		  LINUX-MCSDK 
     (NAND)    		  BIOS-MCSDK 
     (NOR)
    Rev1.0 ESE0075202 - 075236 Feb-13 A102 1.0.1.3a N/A N/A Alpha7
    Rev1.1 EPD0082118 - 0082227 May-22
    May-24    		 A102 1.0.2.5 N/A N/A Alpha7
    Rev2.0 TBD 2013 3Q A103 1.0.2.5 N/A N/A

    Alpha7

    The board that is being discussed in this thread doesn't happen to be the Rev 2.0 called out in the above table, is it?

  • 0 in reply to steve zhang
    TI__Guru 50170 points

    Hi, Steve,

    Could you try running mpm with your kernel build without any changes after downloaded from Arago so to sanity check the build first? If that works, then the problem will be the kernel you build.

    Rex

  • 0 in reply to Rex Chang
    Expert 1690 points

    Rex Chang said:

    Hi, Steve,

    Could you try running mpm with your kernel build without any changes after downloaded from Arago so to sanity check the build first? If that works, then the problem will be the kernel you build.

    Rex

    Rex:

    I can confirm that MPM work successfully with the kernel images named

    "uImage-keystone-evm.bin" supplied by EVM K2.But There‘re have problem

    when MPM worked with new kernel I build.

          I have no way,Now what I just can do was I recompiled MPM source code to

    produce new object files including mpmsrv and mpmcl.

    Thx！

  • 0 in reply to John Westmoreland43
    Guru 13915 points

    And - Advantech has evidently already announced a new rev of the board before anyone answered my question(s):

    Rev2.0 EPD0085682 - EPD0090157 2013 3Q A103 1.0.2.5 N/A Alpha7
    Rev3.0 TBD 2013 4Q A104 1.0.2.5 N/A

    Alpha7

    Regards,
    johnw

  • 0 in reply to steve zhang
    TI__Guru 50170 points

    Hi, Steve,

    Sorry I was out of office on a business trip, so the response was slow.

    I recompiled the 3.0.1.12 kernel with default configuration and mpm works without any issues. I also tried to use 3.0.1.12 kernel with 3.0.0.11 file system, then I see the error as yours. So, my question is that are you using the file system from release 3.0.1.12 which matches your kernel version, or from different release? Attached are the logs I ran. Using kernel  I built and file system from the same release, 3.0.1.12. I was able to run successfully the demo_ipc.sh and demo_imageproc.sh.

    Rex

    Fullscreen 8306.mpmlogs.txt Download 
    =============================== logs ======================================
===  kernel built from 3.0.1.12 release and file system of same release ===

***************************************************************
***************************************************************
Stopping Bootlog daemon: bootlogd.

_____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org keystone-evm ttyS0

Arago 2013.04 keystone-evm ttyS0

keystone-evm login: root
root@keystone-evm:~# cd /usr/share/matrix-gui-2.0/apps/demo_imageproc/
c.sh@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_imageproc# ./demo_imageproc
[   31.288496]  remoteproc0: powering up 2620040.dsp0
[   31.293282]  remoteproc0: Booting unspecified firmware
[   31.302726] virtio_rpmsg_bus virtio0: rpmsg host is online
[   31.308343]  remoteproc0: registered virtio0 (type 7)
[   31.313618]  remoteproc0: remote processor 2620040.dsp0 is now up
[   31.358524]  remoteproc1: powering up 2620044.dsp1
[   31.363290]  remoteproc1: Booting unspecified firmware
[   31.372035] virtio_rpmsg_bus virtio1: rpmsg host is online
[   31.377684]  remoteproc1: registered virtio1 (type 7)
[   31.383044]  remoteproc1: remote processor 2620044.dsp1 is now up
[   31.401545] virtio_rpmsg_bus virtio0: creating channel rpmsg-proto addr 0x3d
[   31.408779] rpmsg_proto rpmsg0: inserting rpmsg src: 1024, dst: 61
[   31.438601]  remoteproc2: powering up 2620048.dsp2
[   31.443373]  remoteproc2: Booting unspecified firmware
[   31.452032] virtio_rpmsg_bus virtio2: rpmsg host is online
[   31.457563]  remoteproc2: registered virtio2 (type 7)
[   31.462640]  remoteproc2: remote processor 2620048.dsp2 is now up
[   31.528494]  remoteproc3: powering up 262004c.dsp3
[   31.533259]  remoteproc3: Booting unspecified firmware
[   31.537446] virtio_rpmsg_bus virtio1: creating channel rpmsg-proto addr 0x3d
[   31.537603] rpmsg_proto rpmsg1: inserting rpmsg src: 1024, dst: 61
[   31.555775] virtio_rpmsg_bus virtio3: rpmsg host is online
[   31.561303]  remoteproc3: registered virtio3 (type 7)
[   31.566342]  remoteproc3: remote processor 262004c.dsp3 is now up
[   31.628515]  remoteproc4: powering up 2620050.dsp4
[   31.633298]  remoteproc4: Booting unspecified firmware
[   31.641889] virtio_rpmsg_bus virtio4: rpmsg host is online
[   31.647380]  remoteproc4: registered virtio4 (type 7)
[   31.652432]  remoteproc4: remote processor 2620050.dsp4 is now up
[   31.666123] virtio_rpmsg_bus virtio2: creating channel rpmsg-proto addr 0x3d
[   31.673293] rpmsg_proto rpmsg2: inserting rpmsg src: 1024, dst: 61
[   31.728516]  remoteproc5: powering up 2620054.dsp5
[   31.733282]  remoteproc5: Booting unspecified firmware
[   31.741356] virtio_rpmsg_bus virtio5: rpmsg host is online
[   31.746877]  remoteproc5: registered virtio5 (type 7)
[   31.751941]  remoteproc5: remote processor 2620054.dsp5 is now up
[   31.786097] virtio_rpmsg_bus virtio3: creating channel rpmsg-proto addr 0x3d
[   31.793272] rpmsg_proto rpmsg3: inserting rpmsg src: 1024, dst: 61
[   31.828496]  remoteproc6: powering up 2620058.dsp6
[   31.833259]  remoteproc6: Booting unspecified firmware
[   31.841484] virtio_rpmsg_bus virtio6: rpmsg host is online
[   31.847072]  remoteproc6: registered virtio6 (type 7)
[   31.852429]  remoteproc6: remote processor 2620058.dsp6 is now up
[   31.908513]  remoteproc7: powering up 262005c.dsp7
[   31.913289]  remoteproc7: Booting unspecified firmware
[   31.918949] virtio_rpmsg_bus virtio4: creating channel rpmsg-proto addr 0x3d
[   31.926263] rpmsg_proto rpmsg4: inserting rpmsg src: 1024, dst: 61
[   31.935649] virtio_rpmsg_bus virtio7: rpmsg host is online
[   31.941412]  remoteproc7: registered virtio7 (type 7)
[   31.946693]  remoteproc7: remote processor 262005c.dsp7 is now up
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"><title>Multicore Image Processing Demonstration</title>

<script type="text/javascript" language="javascript">
function CheckExtentionBMP(){
var FileExt = document.userinput.imagefile.value;
FileExt = FileExt.substring(FileExt.length - 4, FileExt.length);
if(FileExt != '.bmp') { alert("Only BMP file type is allowed.");
return false;
} else {
return true;
}
}
</script></head>
<body style="font-family: helvetica[   32.029119] virtio_rpmsg_bus virtio5: creating channel rpmsg-proto addr 0x3d
;" onload="docum[   32.036964] rpmsg_proto rpmsg5: inserting rpmsg src: 1024, dst: 61
ent.userinput.imagefile.focus()">
<!--<div align="center">-->
<table style="text-align: left; background-color: white" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="width: 147px; text-align: center;"><img src="apps/images/dspchip.png" alt=""></td>
<td><span style="font-size:200%;">Multicore Image Processing Demonstration</span></td>
</tr>
</tbody>
</table>
<!--</div>-->
<!--<div align="center">-->
<form enctype="multipart/form-data" method="post" name="userinput" onsubmit="return CheckExtentionBMP();" action="apps/demo_imageproc/cgi-bin/image_processing_evmtci6638k2k_master.out"><br>
<table cellspacing="10">
<tbody>
<tr>
<td>
<table style="float: left; text-align: left;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td style="width: 200px;"><span style="font-weight: bold;">Number of Cores</span></td>
<td>
<select name="numberofcores">
<option selected value="1">One</option>
<option value="2">Two</option>
<optio[   32.130693] virtio_rpmsg_bus virtio6: creating channel rpmsg-proto addr 0x3d
n value="3">Thre[   32.138647] rpmsg_proto rpmsg6: inserting rpmsg src: 1024, dst: 61
e</option>
<option value="4">Four</option>
<option value="5">Five</option>
<option value="6">Six</option>
<option value="7">Seven</option>
<option value="8">Eight</option>
</select>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td>
<table style="float: left; text-align: left;" border="0"[   32.173128] virtio_rpmsg_bus virtio7: creating channel rpmsg-proto addr 0x3d
cellpadding="2"[   32.180832] rpmsg_proto rpmsg7: inserting rpmsg src: 1024, dst: 61
cellspacing="2">
<tbody>
<tr>
<td style="width: 200px;"><span style="font-weight: bold;">Image processing function</span></td>
<td><input name="processingtype" value="Edge Detection" checked="checked" type="radio">Edge Detection</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<th align="left">Select Image to Process</th>
</tr>
<tr>
<td><input name="imagefile" accept="image/bmp" size="60" type="file"></td>
</tr>
<tr>
<td><input value="Process" type="submit"></td>
</tr>
<tr>
<td><strong>Note:</strong> 8/24 bit <a href="http://en.wikipedia.org/wiki/BMP_file_format" target="_blank">bitmap
(BMP)</a> images are supported
</td>
</tr>
</tbody>
</table>
<br>
<br>
<small><i>BIOS MCSDK Image Processing Demonstration Version 1.00.00.03</i><small>
</form>
<!--</div>-->
<br>
<br>
root@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_imageproc# cd ../demo_ipc/
root@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_ipc# lsoc# cd ../demo_ipc/
demo_ipc.desktop    demo_ipc.sh         desc_demo_ipc.html
root@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_ipc# ./demo_ips.sh
-sh: ./demo_ips.sh: No such file or directory
root@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_ipc# ls
demo_ipc.desktop    demo_ipc.sh         desc_demo_ipc.html
root@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_ipc# ./demo_ipc.sh
Loading DSP Images
Resetting core 0...
[   53.098606] rpmsg_proto rpmsg0: deleting rpmsg src: 1024, dst: 61
[   53.104816]  remoteproc0: stopped remote processor 2620040.dsp0
reset succeeded
dsp0 is in reset state
Resetting core 1...
[   53.178593] rpmsg_proto rpmsg1: deleting rpmsg src: 1024, dst: 61
[   53.184788]  remoteproc1: stopped remote processor 2620044.dsp1
reset succeeded
dsp1 is in reset state
Resetting core 2...
[   53.258705] rpmsg_proto rpmsg2: deleting rpmsg src: 1024, dst: 61
[   53.264915]  remoteproc2: stopped remote processor 2620048.dsp2
reset succeeded
dsp2 is in reset state
Resetting core 3...
[   53.338590] rpmsg_proto rpmsg3: deleting rpmsg src: 1024, dst: 61
[   53.344799]  remoteproc3: stopped remote processor 262004c.dsp3
reset succeeded
dsp3 is in reset state
Resetting core 4...
[   53.418588] rpmsg_proto rpmsg4: deleting rpmsg src: 1024, dst: 61
[   53.424796]  remoteproc4: stopped remote processor 2620050.dsp4
reset succeeded
dsp4 is in reset state
Resetting core 5...
[   53.498700] rpmsg_proto rpmsg5: deleting rpmsg src: 1024, dst: 61
[   53.504908]  remoteproc5: stopped remote processor 2620054.dsp5
reset succeeded
dsp5 is in reset state
Resetting core 6...
[   53.578590] rpmsg_proto rpmsg6: deleting rpmsg src: 1024, dst: 61
[   53.584797]  remoteproc6: stopped remote processor 2620058.dsp6
reset succeeded
dsp6 is in reset state
Resetting core 7...
[   53.658699] rpmsg_proto rpmsg7: deleting rpmsg src: 1024, dst: 61
[   53.664906]  remoteproc7: stopped remote processor 262005c.dsp7
reset succeeded
dsp7 is in reset state
Done
Loading and Running  ...
load succeeded
[   53.748495]  remoteproc0: powering up 2620040.dsp0
[   53.753259]  remoteproc0: Booting unspecified firmware
[   53.759593] virtio_rpmsg_bus virtio0: rpmsg host is online
[   53.765177]  remoteproc0: registered virtio0 (type 7)
[   53.770308]  remoteproc0: remote processor 2620040.dsp0 is now up
[   53.776468] virtio_rpmsg_bus virtio0: creating channel rpmsg-proto addr 0x3d
[   53.783658] rpmsg_proto rpmsg8: inserting rpmsg src: 1024, dst: 61
run succeeded
load succeeded
[   53.838492]  remoteproc1: powering up 2620044.dsp1
[   53.843257]  remoteproc1: Booting unspecified firmware
[   53.849642] virtio_rpmsg_bus virtio1: rpmsg host is online
[   53.855116]  remoteproc1: registered virtio1 (type 7)
[   53.860329]  remoteproc1: remote processor 2620044.dsp1 is now up
[   53.866588] virtio_rpmsg_bus virtio1: creating channel rpmsg-proto addr 0x3d
[   53.873852] rpmsg_proto rpmsg9: inserting rpmsg src: 1024, dst: 61
run succeeded
load succeeded
[   53.918495]  remoteproc2: powering up 2620048.dsp2
[   53.923260]  remoteproc2: Booting unspecified firmware
[   53.929740] virtio_rpmsg_bus virtio2: rpmsg host is online
[   53.935212]  remoteproc2: registered virtio2 (type 7)
[   53.940352]  remoteproc2: remote processor 2620048.dsp2 is now up
[   53.946513] virtio_rpmsg_bus virtio2: creating channel rpmsg-proto addr 0x3d
[   53.953706] rpmsg_proto rpmsg10: inserting rpmsg src: 1024, dst: 61
run succeeded
load succeeded
[   53.998494]  remoteproc3: powering up 262004c.dsp3
[   54.003259]  remoteproc3: Booting unspecified firmware
[   54.009605] virtio_rpmsg_bus virtio3: rpmsg host is online
[   54.015078]  remoteproc3: registered virtio3 (type 7)
[   54.020215]  remoteproc3: remote processor 262004c.dsp3 is now up
[   54.026376] virtio_rpmsg_bus virtio3: creating channel rpmsg-proto addr 0x3d
[   54.033653] rpmsg_proto rpmsg11: inserting rpmsg src: 1024, dst: 61
run succeeded
load succeeded
[   54.078489]  remoteproc4: powering up 2620050.dsp4
[   54.083254]  remoteproc4: Booting unspecified firmware
[   54.089932] virtio_rpmsg_bus virtio4: rpmsg host is online
[   54.095405]  remoteproc4: registered virtio4 (type 7)
[   54.100544]  remoteproc4: remote processor 2620050.dsp4 is now up
[   54.106706] virtio_rpmsg_bus virtio4: creating channel rpmsg-proto addr 0x3d
[   54.113899] rpmsg_proto rpmsg12: inserting rpmsg src: 1024, dst: 61
run succeeded
load succeeded
[   54.158496]  remoteproc5: powering up 2620054.dsp5
[   54.163259]  remoteproc5: Booting unspecified firmware
[   54.169671] virtio_rpmsg_bus virtio5: rpmsg host is online
[   54.175144]  remoteproc5: registered virtio5 (type 7)
[   54.180283]  remoteproc5: remote processor 2620054.dsp5 is now up
[   54.186445] virtio_rpmsg_bus virtio5: creating channel rpmsg-proto addr 0x3d
[   54.193712] rpmsg_proto rpmsg13: inserting rpmsg src: 1024, dst: 61
run succeeded
load succeeded
[   54.238499]  remoteproc6: powering up 2620058.dsp6
[   54.243262]  remoteproc6: Booting unspecified firmware
[   54.249648] virtio_rpmsg_bus virtio6: rpmsg host is online
[   54.255122]  remoteproc6: registered virtio6 (type 7)
[   54.260335]  remoteproc6: remote processor 2620058.dsp6 is now up
[   54.266577] virtio_rpmsg_bus virtio6: creating channel rpmsg-proto addr 0x3d
[   54.273791] rpmsg_proto rpmsg14: inserting rpmsg src: 1024, dst: 61
run succeeded
load succeeded
[   54.318507]  remoteproc7: powering up 262005c.dsp7
[   54.323271]  remoteproc7: Booting unspecified firmware
[   54.329677] virtio_rpmsg_bus virtio7: rpmsg host is online
[   54.335150]  remoteproc7: registered virtio7 (type 7)
[   54.340291]  remoteproc7: remote processor 262005c.dsp7 is now up
[   54.346454] virtio_rpmsg_bus virtio7: creating channel rpmsg-proto addr 0x3d
[   54.353722] rpmsg_proto rpmsg15: inserting rpmsg src: 1024, dst: 61
run succeeded
Running MessageQBench:
Using numLoops: 1000; payloadSize: 8, procId : 1
Entered MessageQApp_execute
Local MessageQId: 0x1
Remote queueId  [0x10000]
Exchanging 1000 messages with remote processor CORE0...
CORE0: Avg round trip time: 48 usecs
Leaving MessageQApp_execute

root@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_ipc#
root@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_ipc#




=============================== Logs ==============================================
========== kernel built from 3.0.1.12 release , but 3.0.0.11 file system ==========



root@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_ipc# ls
demo_ipc.desktop    demo_ipc.sh         desc_demo_ipc.html
root@keystone-evm:/usr/share/matrix-gui-2.0/apps/demo_ipc# ./demo_ipc.sh
Loading DSP Images
Resetting core 0...
reset failed (error: -105)
dsp0 is in reset state
Resetting core 1...
reset failed (error: -105)
dsp1 is in reset state
Resetting core 2...
reset failed (error: -105)
dsp2 is in reset state
Resetting core 3...

     

     

  • 0 in reply to Rex Chang
    Expert 1690 points

    Rex: 

    I was able to run demo_ipc.sh and demo_imageproc.sh successfully only

    when I got kernel images and file system images from mcsdk_linux_3_00_01_12.

          But I failed when I got kernel source code from website

    git clone git://arago-project.org/git/projects/linux-keystone.git

    along with the command

    git reset --hard DEV.MCSDK-03.08.04.11

     BTW,file system images was also got from mcsdk_linux_3_00_01_12.

         I agreed with you that issues could come from mismatch between kernel version

    and file system version.But I don't know how to get the right kernel version 

    which matched with file system images in the mcsdk_linux_3_00_01_12.

    I guessed the Release  Tag -hard DEV.MCSDK-03.08.04.11 was not right because

    I had tried and failed.

         Rex,Could you tell me the right Release Tag which matched with the file system

    in the mcsdk_linux_3_00_01_12.

    Any help will be appreciated.  thx!

  • 0 in reply to steve zhang
    TI__Guru 50170 points

    Hi, Steve,

    Please follow the User's Guide for the linux tag,

       http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring

    The release date for 3.0.1.12 is July 2013 (13.07).

    Rex

  • 0 in reply to Rex Chang
    TI__Intellectual 1840 points

    You can follow Yocto procedure from http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Yocto and for 3.0.1.12 use ./oe-layertool-setup.sh -f configs/mcsdk/mcsdk-03.00.01.12-config.txt.

    It will build you kernel and filesystem images for the release.

  • 0 in reply to Sajesh Kumar Saran
    Expert 1690 points

    Sajesh Kumar Saran said:

    You can follow Yocto procedure from http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Yocto and for 3.0.1.12 use ./oe-layertool-setup.sh -f configs/mcsdk/mcsdk-03.00.01.12-config.txt.

    It will build you kernel and filesystem images for the release.

    Hi Sajesh Kumar Saran:

    I followed the page http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Yocto.

    When I  executed the comman below

    MACHINE=keystone-evm TOOLCHAIN_BRAND=linaro bitbake tisdk-server-rootfs-image

    I failed and found these errors:

    Pseudo is not present but is required, building this first before the main build

    ERROR:  OE-core's config sanity checker detected a potential misconfiguration.

        Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).

        Following is the list of potential problems / advisories:

     

        Failed to create a file in TMPDIR: No such file or directory.

    Failed to create a file in SSTATE_DIR: No such file or directory.

     

    ERROR: Execution of event handler 'check_sanity_eventhandler' failed

    ERROR:  OE-core's config sanity checker detected a potential misconfiguration.

        Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).

        Following is the list of potential problems / advisories:

     

        Failed to create a file in TMPDIR: No such file or directory.

    Failed to create a file in SSTATE_DIR: No such file or directory.

     

    ERROR: Execution of event handler 'check_sanity_eventhandler' failed

  • 0 in reply to steve zhang
    TI__Intellectual 1840 points

    Hi Steve,

    It looks like you don't have permissions to create TMPDIR. Can you please check if the paths in the file 'setenv' and 'local.conf' in build\conf of your Yocto setup are correct and you have permissions to write to it.

    There are more information provided in http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Build_Prerequisites for setting up build environment.

    Regards

    Sajesh

  • 0 in reply to Sajesh Kumar Saran
    Expert 1690 points

    Hi:

       I looked at the conf and local.conf in the mcsdk/build.

    In the conf:

    export OEBASE=/mnt/hgfs/ubuntu_shares/cywee_steve/project/FOLLOW_DAVID_EMAIL/mcsdk

    In the local.conf:

    SSTATE_DIR = "${OEBASE}/build/sstate-cache"

    TMPDIR = "${OEBASE}/build/arago-tmp"

    I found sstate-cache and arago-tmp-external-linaro-toolchain in the mcsdk/build . But no arago-tmp.So I created a new folder called arago-tmp.Then I rebuild and failed again.

        Failed to create a file in TMPDIR: No such file or directory.

    Failed to create a file in SSTATE_DIR: No such file or directory.

     

    Errors infos said that no arago-tmp and sstate-cache in the mcsdk/build.But in fact.these two folders existed.Why?

  • 0 in reply to steve zhang
    TI__Intellectual 1840 points

    Hi Steve,

    I have not seen this issue. But, I know that you don't need to create these folders. The Yocto build should create the folders as a part of the build.

    You are seeing some kind of permission issue I would guess. You can dump all the internal environment variables set/used by bitbake using following command

    MACHINE=keystone-evm TOOLCHAIN_BRAND=linaro bitbake -v -p -e tisdk-server-rootfs-image > yocto-env.txt

    This should dump value of SSTATE_DIR and TMPDIR it is using.

    Regards

    Sajesh

  • 0 in reply to Sajesh Kumar Saran
    Expert 1690 points

    Sajesh:

    I tried and followed your advice .yocto-env.txt was also created .

    Unluckily, yocto-env.txt produced errors like below:

    ERROR: Please set the 'PERSISTENT_DIR' or 'CACHE' variable.

    yocto-env.txt  was attatched .

    Why I meet so many errors step by step ? Why didn't you give a instruction?

     

  • 0 in reply to steve zhang
    TI__Intellectual 1840 points

    Hi Steve,

    There are not many steps to build the filesystem. All the steps are in http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Exploring#Yocto.

    I ran following commands to build a the images in an Ubuntu machine to build the filesystem.

    mkdir mcsdk_3.00_test
    cd mcsdk_3.00_test
    git clone http://arago-project.org/git/people/hzhang/oe-layersetup-mcsdk.git mcsdk
    cd mcsdk/
    ./oe-layertool-setup.sh -f configs/mcsdk/mcsdk-03.00.01.12-config.txt
    cd build
    . conf/setenv
    MACHINE=keystone-evm TOOLCHAIN_BRAND=linaro bitbake tisdk-server-rootfs-image

    Have you followed these steps exactly?

    Regards

    Sajesh

  • 0 in reply to Sajesh Kumar Saran
    Expert 1690 points

    Of course,I followed the steps the same as you mentioned.

  • 0 in reply to steve zhang
    TI__Intellectual 1840 points

    Hi Steve,

    You should be able to build with those steps. I would guess there is something in your environment which is conflicting with the build process.

    I suggest, you please post this issue in Yocto mailing list. The link to the mailing list is http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago. This mailing list is monitored by experts in Yocto/OpenMebedded, they should be able to help you further.

    Regards

    Sajesh

  • 0 in reply to Sajesh Kumar Saran
    Expert 1690 points

    Sajesh:

      Thx,I found mpmcl run normally along with the filesystem in the mcsdk_3_00_01_11/images

    but unsuccessfully with filesystem in the mcsdk_3_00_01_12/images.

          So I doubt that mpmcl inside the filesystem in the mcsdk_3_00_01_12/images may be

    have some bugs.

  • 0 in reply to steve zhang
    TI__Intellectual 1840 points

    Hi Steve,

    The mpmcl binary is in filesystem. If you extract the filesystem image present in mcsdk_3_00_01_12/images directory. I looked at "tisdk-rootfs.tar.gz", the mpmcl is in /usr/bin directory.

    Regards

    Sajesh