Configuration / build of messageq_single

Anders Klint

Other Parts Discussed in Thread: CCSTUDIO

Hi,

Like quite a few others on the forum, I'm trying to get MessageQ between Linux on the ARM cores and Sys/BIOS on DSP cores working, in my case on an EVMK2H eval board, rev 3.0
Currently I am able to build an application pair (Linux + DSP) by rebuilding ipc using "make -f ipc-bios.mak" and "make -f ipc-linux.mak" in the ipc installation directory which gives me MessageQBench and messageq_single.xe66
Loading and starting messageq_single.xe66 on all 8 dsp cores and running MessageQBench from Linux command line works and reports round trip times of just over 60 microseconds. So far so good.

What I now try is to rebuild (and as a next step modify) the DSP application in CCStudio. I have created a new Sys/BIOS application using the SYS?BIOS -> Ti target examples -> Typical template, replaced the default app.cfg with rpmsg_transport.cfg and messageq_common.cfg.xs and the default main.c with (by linking) messageq_single.c - all files from packages/ti/ipc/tests under the ipc installation directory. This project builds cleanly, but when i try to run the application pair with the built binary the dsp application hangs (timeout) waiting for the first message from the host ("Awaiting sync message from host...")

The choice of rpmsg_transport.cfg as config file for messageq_single,c was based on this answer: https://e2e.ti.com/support/embedded/tirtos/f/355/p/343362/1204552#1204552

The LAD daemon is running and even when the dsp application hangs the host have been able to find the right queue on core0 (part of log file included below)

Since I am able to build the dsp application using make, it seems to be the configuration in the CCS project that is the problem. I have tried - in vain - to figure out the actual configuration used when building with make -f ipc-bios.mak

Key points of our installation:

CCS Version: 6.0.1.00040
MCSDK 3_01_03_06
IPC 3_35_01_07

Any help on getting this resolved would be most appreciated. I have spent far more time than I am prepared to admit trying to get what I regard as basic infrastructure on a SoC working and am quite surprised and disappointed that there isn't a well documented and stable example to use as a staring point for application development in this setup. A Linux application on SMP-configured ARM using a "farm" of DSPs for heavy numeric processing seems like a very natural architecture on a potentially very competent hardware and I believe it is worthy of better support to get developers started.

Regards,
/Anders Klint

Last part of LAD log file:

[8732.922874] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[8732.923855] LAD_NAMESERVER_GETUINT32: calling NameServer_getUInt32(0x1b4e8, 'SLAVE_CORE0')...

[8732.923885] NameServer_getLocal: entry key: 'SLAVE_CORE0' not found!

[8732.923932] NameServer_getRemote: Sending request via sock: 5

[8732.923952] NameServer_getRemote: Requesting from procId 1, MessageQ:[8732.923971] SLAVE_CORE0...

[8732.924004] NameServer_getRemote: pending on waitFd: 4

[8732.924133] NameServer: back from select()

[8732.924159] NameServer: Listener got NameServer message from sock: 6!

[8732.924186] listener_cb: recvfrom socket: fd: 6

[8732.924206] Received ns msg: byteCount: 484, from addr: 61, [8732.924224] from vproc: 0

[8732.924242] NameServer Reply: instanceName: MessageQ, name: SLAVE_CORE0[8732.924261] , value: 0x10080

[8732.924286] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[8732.924297] NameServer_getRemote: Reply from: 1, MessageQ:[8732.924378] SLAVE_CORE0, value: 0x10080...

[8732.924397] value = 0x10080

[8732.924412] status = 0

[8732.924429] DONE

[8732.924445] Sending response...

[8732.924469] Retrieving command...

Last part of output from MessageQBench:

dsp6 is in running state

load succeeded

run succeeded

dsp7 is in running state

Running MessageQBench:

Using numLoops: 1000; payloadSize: 8, procId : 1

Entered MessageQApp_execute

Local MessageQId: 0x88

Remote queueId [0x10080]

over 8 years ago

0 Shankari G over 8 years ago

TI__Mastermind 43955 points

Hi Anders,

Anders said:

What I now try is to rebuild (and as a next step modify) the DSP application in CCStudio. I have created a new Sys/BIOS application using the SYS?BIOS -> Ti target examples -> Typical template, replaced the default app.cfg with rpmsg_transport.cfg and messageq_common.cfg.xs and the default main.c with (by linking) messageq_single.c - all files from packages/ti/ipc/tests under the ipc installation directory. This project builds cleanly, but when i try to run the application pair with the built binary the dsp application hangs (timeout) waiting for the first message from the host ("Awaiting sync message from host...")

Have you tried to replace the default app.cfg with IPC's .cfg ?

Regards,
Shankari

0 Anders Klint over 8 years ago in reply to Shankari G

Intellectual 620 points

Hi Shankari,

I'm not sure which .cfg you refer to with "IPC's .cfg" - I have replaced the default app.cfg with rpmsg_transport.cfg and message_common.cfg.xs as suggested in the other post I referred to.
In the tests directory there are two files called IpcCommon_omap5.cfg.xs and IpcCommon_vayu.cfg.xs - are these the ones you mean? I have not tried them.

0 Anders Klint over 8 years ago in reply to Anders Klint

Intellectual 620 points

Hi again Shankari (or anyone else who may help)

Could you please clarify which .cfg file you refer to?

Regards /Anders

0 Shankari G over 8 years ago in reply to Anders Klint

TI__Mastermind 43955 points

Hi Anders,

What is your MCSDK version ?

C:\ti\mcsdk_bios_3_01_01_04\demos\image_processing\ipc\evmtci6638k2k\slave
Try this "image_processing_evmtci6638k2k_slave.cfg" from the above location.

Also, provide your steps to reproduce the problem at my end.

Regards,
Shankari

0 Anders Klint over 8 years ago in reply to Shankari G

Intellectual 620 points

Hi,

Key points of our installation:

CCS Version: 6.0.1.00040
MCSDK 3_01_03_06
IPC 3_35_01_07

Steps to reproduce:

Create a new SYS/BIOS project using "Typical" template.
Remove default "main.c" file from project.
Choose "add file" from pop-up menu at project in project explorer pane,
then select "<ti install dir>/ipc_<version>/packages/ti/ipc/tests/messageq_single.c (I selected add by link)
Disable default "app.cfg" by choosing "exclude from build" in popup menu.
Again choose "add file" from pop-up menu at project in project explorer pane,
then select "<ti install dir>/demos/image_processing/ipc/evmtci6638k2k/slave/image_processing_evmtci6638k2k_slave.cfg (add by link)

So far the steps - except the selected .cfg file - are identical to my attempt described above.
To be able to build with the .cfg file from the image processing demo, I also had to do:

Edit the .cfg file and comment out the last lines (from line 186) which creates tasks specific to the image processing demo (?).
The message_single.c file does task creation in its main() function.

Build the project (it produces a clean build in my environment)
Load and start the built executable file on all 8 DSP cores.
Run the pre-built MessageQBench

For me this produces identical results as my previous attempt, last part of output in console is:
run succeeded
dsp7 is in running state
Running MessageQBench:
Using numLoops: 1000; payloadSize: 8, procId : 1
Entered MessageQApp_execute
Local MessageQId: 0x88
Remote queueId [0x10080]

At this point the Linux application just waits forever.

Modifying the dsp application by setting a timeout at the call to MessageQ_get around line 90 and checking the return
code gives that the call fails with a timeout. Repeatedly calling MessageQ_get gives repeated timeouts.

Modified code snippet:
while (1) {
/* handshake with host to get starting parameters */
int numTries = 0;
do {
System_printf("Awaiting sync message from host...\n");
// MessageQ_get(messageQ, &msg, MessageQ_FOREVER);
status = MessageQ_get(messageQ, &msg, 1e6); // Timeout in microseconds
if (status < 0) {
System_printf(" MessageQ_get() failed (%d) after %d attempts\n", status, ++numTries);
}
} while (status < 0);

Thanks for looking into this!

Regards /Anders

0 Anders Klint over 8 years ago in reply to Anders Klint

Intellectual 620 points

Hi Shankari,

Did you manage to reproduce the described behaviour?

Regards /Anders

0 Anders Klint over 8 years ago in reply to Anders Klint

Intellectual 620 points

Hi,

After more analysis it turns out that the previous answer referred to was right - the config files used to build messageq_single
under the tests directory under IPC are rpmsg_transport.cfg and messageq_common.cfg.xs

Looking at the output from the two builds (make -f ipc-bios.mak vs CCS) shows quite large differences (log files below)

Should we regard CCS as a possible way to develop in our project, or should we resort to using a modified version of the build system
used to create the test executables for IPC? We would prefer to use CCS, but obviously it needs to be able to produce working executables.

If anyone on the forum has managed to build IPC/MessageQ based executables in CCS I am very interested in your experiences and advice.

Regards /Anders

Output from build of new target message_single2, identical to messageq_single (copy of source and config):

rm -f package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2/messageq_single2.oe66
#
# cle66 messageq_single2.c ...
/home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/bin/cl6x -c -qq -pdsw225 -mv6600 --abi=eabi -eo.oe66 -ea.se66 -mi10 -mo -pdr -pden -pds=238 -pds=880 -pds1110 -g -D_DEBUG_=1 -D BENCHMARK -Dxdc_cfg__xheader__='"ti/ipc/tests/package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2_pe66.h"' -Dxdc_target_name__=C66 -Dxdc_target_types__=ti/targets/elf/std.h -Dxdc_bld__profile_debug -Dxdc_bld__vers_1_0_7_4_14 --symdebug:dwarf -I. -I/home/klint/ti/bios_6_41_00_26/packages -I/home/klint/ti/xdctools_3_30_05_60/packages -I../../.. -I/home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/include -fs=./package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2 -fr=./package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2 -fc messageq_single2.c
/home/klint/ti/xdctools_3_30_05_60/bin/mkdep -a package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2/messageq_single2.oe66.dep -p package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2 -s oe66 messageq_single2.c -C -qq -pdsw225 -mv6600 --abi=eabi -eo.oe66 -ea.se66 -mi10 -mo -pdr -pden -pds=238 -pds=880 -pds1110 -g -D_DEBUG_=1 -D BENCHMARK -Dxdc_cfg__xheader__='"ti/ipc/tests/package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2_pe66.h"' -Dxdc_target_name__=C66 -Dxdc_target_types__=ti/targets/elf/std.h -Dxdc_bld__profile_debug -Dxdc_bld__vers_1_0_7_4_14 --symdebug:dwarf -I. -I/home/klint/ti/bios_6_41_00_26/packages -I/home/klint/ti/xdctools_3_30_05_60/packages -I../../.. -I/home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/include -fs=./package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2 -fr=./package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2
rm -f bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2.xe66
#
# lnke66 bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2.xe66 ...
rm -f package/cfg//bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2.xe66.map
/home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/bin/lnk6x -w -q -u _c_int00 -fs package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/ -q -o bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2.xe66 package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2_pe66.oe66 package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2/messageq_single2.oe66 package/cfg/bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2_pe66.xdl --abi=eabi -c -m package/cfg//bin/ti_platforms_evmTCI6636K2H_core0/messageq_single2.xe66.map -l /home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/lib/libc.a --cinit_compression=off
.executables files complete: Wed May 27 11:02:17 CEST 2015.

Output from building a SYS/BIOS project based on "typical" template with main.c replaced by message_single.c and app.cfg replaced by rpmsg_transport.cfg (and by include, message_common.cfg.xs):

Building file: /home/klint/ti/ipc_3_35_01_07/packages/ti/ipc/tests/messageq_single.c
Invoking: C6000 Compiler
"/home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/bin/cl6x" --abi=eabi -g --include_path="/home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/include" --display_error_number --diag_warning=225 --diag_wrap=off --preproc_with_compile --preproc_dependency="messageq_single.pp" --cmd_file="./configPkg/compiler.opt" "/home/klint/ti/ipc_3_35_01_07/packages/ti/ipc/tests/messageq_single.c"
Finished building: /home/klint/ti/ipc_3_35_01_07/packages/ti/ipc/tests/messageq_single.c

Building target: mq.out
Invoking: C6000 Linker
"/home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/bin/cl6x" --abi=eabi -g --display_error_number --diag_warning=225 --diag_wrap=off -z -m"mq.map" -i"/home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/lib" -i"/home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/include" --reread_libs --warn_sections --display_error_number --diag_wrap=off --xml_link_info="mq_linkInfo.xml" --rom_model -o "mq.out" -l"./configPkg/linker.cmd" "./messageq_single.obj" -l"libc.a"
<Linking>
Finished building target: mq.out

Copy binary to target
cp mq.out /opt/nfshost/home/root/klint/

**** Build Finished ****

Both executables load and run, but the one built with CCS hangs on the first MessageQ_get while the one built built with the tests perform as expected.

0 Ronny Jimenez over 8 years ago in reply to Anders Klint

Intellectual 550 points

Anders

Using CCS is kind of tricky when generating code aimed to the KeyStone II devices, I found it was much more easier to use a command line approach than a CCS, and as consequence you have more control of the compilation process . Nevertheless I think it is possible and probably you should change some packages on the CFGs. As you, I think TI documentation about it is really really poor. I would suggest you to modify your CFGs and makefiles by hand and "match" them with the output you are looking for. Probably it's not the best solution long-term, but should work in a short-term solution.

A long-term solution should be to start looking for dependencies that might be needed during runtime and start adding them into the CCS project while compiling and linking the proper libraries.

A good idea would be to post here your CFGs, makefiles, and even the whole project in order to see possible solutions for your issue.

Regards,
Ronny

0 Shankari G over 8 years ago in reply to Ronny Jimenez

TI__Mastermind 43955 points

Hi Ronny,

Sorry for my delayed response.

As a first step,( Attempt with pre-built )

Able to run the K2H Image processing demo with pre-built images ( Both ARM + DSP ) side.

As a second step, ( Attempt with own-build )

Able to rebuild the slave side IPC program ( Project used : opt/ti/mcsdk_bios_3_00_03_15/demos/image_processing/ipc/evmtci6638k2k/slave) using CCS version 5.5
Replaced the rebuilt binary, "image_processing_evmtci6638k2k_slave.out" at /usr/share/matrix-gui-2.0/apps/demo_imageproc/bin/
Able to run the demo as expected.

As a third step ( Tried reproduce your problem)

Followed your steps but not able to reproduce your problem...

Questions to you:

1. Did you get any problem in re-building the DSP ( slave side) image processing project??

2. By any chance, you tried replacing the newly built DSP side binary at "/usr/share/matrix-gui-2.0/apps/demo_imageproc/bin/" ??

3. Would you please make me understand the necessity of creating your own example instead of modifying the image processing slave side project or reusing this project for your requirements?

Regards,

Shankari

0 Anders Klint over 8 years ago in reply to Shankari G

Intellectual 620 points

Hi Shankari,

Answer to your specific questions at the bottom of the post.

I attempted the same steps as you report above with the following results:

First: Running the image processing demo with pre-build images FAIL
Webpage comes up, number of cores and image is selected. After pressing "Process"
the only thing happening in the browser (Firefox) is a note "waiting for 10.44.0.2",
where the 10.44.0.2 corresponds to the IP address of our EVM board.

Looking at the LAD log during the attemped run shows this:

root@k2hk-evm:~# tail -f /tmp/LAD/lad.txt

[0.569089]

Initializing LAD... [0.569500]

opening FIFO: /tmp/LAD/LADCMDS

[74.571767] Retrieving command...

[74.572181]

LAD_CONNECT:

[74.572199] client FIFO name = /tmp/LAD/1979

[74.572211] client PID = 1979

[74.572228] assigned client handle = 0

[74.572345] FIFO /tmp/LAD/1979 created

[74.572478] FIFO /tmp/LAD/1979 opened for writing

[74.572527] sent response

[74.572542] DONE

[74.572554] Retrieving command...

[74.572583] LAD_MULTIPROC_GETCONFIG: calling MultiProc_getConfig()...

[74.572605] MultiProc_getConfig() - 65535 procs

[74.572620] # processors in cluster: 9

[74.572631] cluster baseId: 0

[74.572642] ProcId 0 - "HOST"

[74.572653] ProcId 1 - "CORE0"

[74.572664] ProcId 2 - "CORE1"

[74.572675] ProcId 3 - "CORE2"

[74.572685] ProcId 4 - "CORE3"

[74.572696] ProcId 5 - "CORE4"

[74.572706] ProcId 6 - "CORE5"

[74.572717] ProcId 7 - "CORE6"

[74.572727] ProcId 8 - "CORE7"

[74.572738] status = 0

[74.572749] DONE

[74.572760] Sending response...

[74.572779] Retrieving command...

[74.573162] LAD_NAMESERVER_SETUP: calling NameServer_setup()...

[74.573190] NameServer_setup: entered, refCount=0

[74.573263] NameServer_setup: created send socket: 5, procId 1

[74.573308] NameServer_setup: created recv socket: 6, procId 1

[74.573476] NameServer_setup: created send socket: 7, procId 2

[74.573506] NameServer_setup: created recv socket: 8, procId 2

[74.573629] NameServer_setup: created send socket: 9, procId 3

[74.573655] NameServer_setup: created recv socket: 10, procId 3

[74.573778] NameServer_setup: created send socket: 11, procId 4

[74.573806] NameServer_setup: created recv socket: 12, procId 4

[74.573921] NameServer_setup: created send socket: 13, procId 5

[74.573950] NameServer_setup: created recv socket: 14, procId 5

[74.574065] NameServer_setup: created send socket: 15, procId 6

[74.574094] NameServer_setup: created recv socket: 16, procId 6

[74.574206] NameServer_setup: created send socket: 17, procId 7

[74.574233] NameServer_setup: created recv socket: 18, procId 7

[74.574348] NameServer_setup: created send socket: 19, procId 8

[74.574374] NameServer_setup: created recv socket: 20, procId 8

[74.574480] NameServer_setup: creating listener thread

[74.574602] NameServer_setup: exiting, refCount=1

[74.574636] listener_cb: Entered Listener thread.

[74.574679] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[74.574641] status = 0

[74.575018] DONE

[74.575030] Sending response...

[74.575049] Retrieving command...

[74.575167] LAD_MESSAGEQ_GETCONFIG: calling MessageQ_getConfig()...

[74.575183] status = 0

[74.575196] DONE

[74.575208] Sending response...

[74.575225] Retrieving command...

[74.575366] LAD_MESSAGEQ_SETUP: calling MessageQ_setup()...

[74.575382] MessageQ_setup: entered, refCount=0

[74.575402] NameServer_create(): 'MessageQ'

[74.575432] MessageQ_setup: exiting, refCount=1

[74.575446] status = 0

[74.575460] DONE

[74.575475] Sending response...

[74.575492] Retrieving command...

[74.575963] LAD_MESSAGEQ_CREATE: calling MessageQ_create(0x1aae0, 0x1ab00)...

[74.575983] MessageQ_create: creating 'HOST_DDR'

[74.576004] NameServer_add: Entered key: 'HOST_DDR', data: 0x88

[74.576018] MessageQ_create: returning obj=0x1b5d0, qid=0x88

[74.576032] status = 0

[74.576044] DONE

[74.576057] Sending response...

[74.576075] Retrieving command...

[74.579513] LAD_NAMESERVER_GETUINT32: calling NameServer_getUInt32(0x1b4e8, 'SLAVE_DDR_CORE0')...

[74.579548] NameServer_getLocal: entry key: 'SLAVE_DDR_CORE0' not found!

[74.579570] NameServer_getRemote: Sending request via sock: 5

[74.579589] NameServer_getRemote: Requesting from procId 1, MessageQ:[74.579608] SLAVE_DDR_CORE0...

[74.579641] NameServer_getRemote: pending on waitFd: 4

[74.579733] NameServer: back from select()

[74.579760] NameServer: Listener got NameServer message from sock: 6!

[74.579786] listener_cb: recvfrom socket: fd: 6

[74.579802] Received ns msg: byteCount: 484, from addr: 61, [74.579817] from vproc: 0

[74.579830] NameServer Reply: instanceName: MessageQ, name: SLAVE_DDR_CORE0[74.579846] , value: 0x10080

[74.579870] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[74.579996] NameServer_getRemote: Reply from: 1, MessageQ:[74.580019] SLAVE_DDR_CORE0, value: 0x10080...

[74.580038] value = 0x10080

[74.580053] status = 0

[74.580068] DONE

[74.580084] Sending response...

[74.580110] Retrieving command...

...which seems to indicate that there is a mismatch in the queue names..?

Second: Rebuilding the project
~/ti/mcsdk_bios_3_01_03_06/demos/image_processing/ipc/slave

FAILS with the message below:

undefined first referenced
symbol in file
--------- ----------------
main /home/klint/ti/ccsv6/tools/compiler/c6000_7.4.14/lib/rts6600_elf.lib<args_main.obj>

error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking;
"image_processing_evmtci6638k2k_slave.out" not built

And your specific questions:

1. Did you get any problem in re-building the DSP ( slave side) image processing project??
Yes, failed as described above.

2. By any chance, you tried replacing the newly built DSP side binary at "/usr/share/matrix-gui-2.0/apps/demo_imageproc/bin/" ??
No, since the build failed.

3. STARTING with the image processing demo is perfectly acceptable - if it works.
The product should still be stable and enough documented to allow a more fine-tuned workflow once work is progressing.

Regards,
/Anders

0 Shankari G over 8 years ago in reply to Anders Klint

TI__Mastermind 43955 points

Hi Anders,

I can help you out in re-building the DSP slave side image processing project.

The following are the steps:

1. Install mcsdk_bios_3_00_03_15 and CCS

2. Import the project located at "..\ti\mcsdk_bios_3_00_03_15\demos\image_processing\ipc\evmtci6638k2k\slave" into CCS using the option, "import"

CCS-->project-->import existing CCS eclipse project-->select search directory--> path to "<\ti\mcsdk_bios_3_00_03_15\demos\image_processing\ipc\evmtci6638k2k\slave>"-->Finish.

3. Build the project.

4. Under binary folder, you will find the out file as "image_processing_evmtci6638k2k_slave.out".

5. Take this binary file, image_processing_evmtci6638k2k_slave.out and replace it in the path, /usr/share/matrix-gui-2.0/apps/demo_imageproc/bin/"

Get back to me if you failed in any of the steps given above.

Regards,

Shankari

-------------------------------------------------------------------------------------------------------

Please click the Verify Answer button on this post if it answers your question.
--------------------------------------------------------------------------------------------------------

--------------------------------------------------------------------------------------------------------

0 Anders Klint over 8 years ago in reply to Shankari G

Intellectual 620 points

Hi Shankari,

I have installed CCS5.5 and MCSDK 3.0.3.15, imported the demo project into CCS and built as described.

This produced a clean build and I replaced the old binary with the newly built one as per your instructions.

However, running this one also fails, but with continuous new data being written to the LAD log (excerpt included below)

The behaviour of the browser is as before - nothing happens.

I am a bit concerned about the perceived need to go back to olde releases of both CCS and MCSDK - are there known
problems with the newer versions? While my first priority is getting this to work, I am also interested in keeping an up-to-date
development environment.

Further I am interested in your view about why the pre-built image processing demo binaries fail to work, while the IPC demo
works as expected on the same hardware.

Looking forward to hearing from you!

Regards
/Anders

-------
Following is a part of LAD log file from failed run of image processing demo.
The sequence below is repeated about once per second, one cycle included here.
--------

773.537098] Sending response...

[773.537119] Retrieving command...

[774.537226] LAD_NAMESERVER_GETUINT32: calling NameServer_getUInt32(0x1b4e8, 'SLAVE_DDR_CORE0')...

[774.537246] NameServer_getLocal: entry key: 'SLAVE_DDR_CORE0' not found!

[774.537259] NameServer_getRemote: Sending request via sock: 5

[774.537272] NameServer_getRemote: Requesting from procId 1, MessageQ:[774.537285] SLAVE_DDR_CORE0...

[774.537305] NameServer_getRemote: pending on waitFd: 4

[774.537350] NameServer: back from select()

[774.537364] NameServer: Listener got NameServer message from sock: 6!

[774.537381] listener_cb: recvfrom socket: fd: 6

[774.537393] Received ns msg: byteCount: 176, from addr: 61, [774.537406] from vproc: 0

[774.537417] NameServer Reply: instanceName: MessageQ, name: SLAVE_DDR_CORE0[774.537430] , value: 0xb6ec60d8

[774.537447] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[774.537479] NameServer_getRemote: value for MessageQ:SLAVE_DDR_CORE0 not found.

[774.537494] NameServer_getRemote: Sending request via sock: 7

[774.537506] NameServer_getRemote: Requesting from procId 2, MessageQ:[774.537519] SLAVE_DDR_CORE0...

[774.537539] NameServer_getRemote: pending on waitFd: 4

[774.537583] NameServer: back from select()

[774.537596] NameServer: Listener got NameServer message from sock: 8!

[774.537613] listener_cb: recvfrom socket: fd: 8

[774.537625] Received ns msg: byteCount: 176, from addr: 61, [774.537638] from vproc: 1

[774.537649] NameServer Reply: instanceName: MessageQ, name: SLAVE_DDR_CORE0[774.537662] , value: 0xb6ec60d8

[774.537679] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[774.537710] NameServer_getRemote: value for MessageQ:SLAVE_DDR_CORE0 not found.

[774.537725] NameServer_getRemote: Sending request via sock: 9

[774.537747] NameServer_getRemote: Requesting from procId 3, MessageQ:[774.537760] SLAVE_DDR_CORE0...

[774.537780] NameServer_getRemote: pending on waitFd: 4

[774.537823] NameServer: back from select()

[774.537837] NameServer: Listener got NameServer message from sock: 10!

[774.537853] listener_cb: recvfrom socket: fd: 10

[774.537866] Received ns msg: byteCount: 176, from addr: 61, [774.537878] from vproc: 2

[774.537889] NameServer Reply: instanceName: MessageQ, name: SLAVE_DDR_CORE0[774.537902] , value: 0xb6ec60d8

[774.537919] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[774.537950] NameServer_getRemote: value for MessageQ:SLAVE_DDR_CORE0 not found.

[774.537964] NameServer_getRemote: Sending request via sock: 11

[774.537976] NameServer_getRemote: Requesting from procId 4, MessageQ:[774.537988] SLAVE_DDR_CORE0...

[774.538008] NameServer_getRemote: pending on waitFd: 4

[774.538052] NameServer: back from select()

[774.538065] NameServer: Listener got NameServer message from sock: 12!

[774.538082] listener_cb: recvfrom socket: fd: 12

[774.538094] Received ns msg: byteCount: 176, from addr: 61, [774.538106] from vproc: 3

[774.538117] NameServer Reply: instanceName: MessageQ, name: SLAVE_DDR_CORE0[774.538129] , value: 0xb6ec60d8

[774.538146] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[774.538177] NameServer_getRemote: value for MessageQ:SLAVE_DDR_CORE0 not found.

[774.538192] NameServer_getRemote: Sending request via sock: 13

[774.538204] NameServer_getRemote: Requesting from procId 5, MessageQ:[774.538216] SLAVE_DDR_CORE0...

[774.538236] NameServer_getRemote: pending on waitFd: 4

[774.538279] NameServer: back from select()

[774.538293] NameServer: Listener got NameServer message from sock: 14!

[774.538309] listener_cb: recvfrom socket: fd: 14

[774.538322] Received ns msg: byteCount: 176, from addr: 61, [774.538334] from vproc: 4

[774.538346] NameServer Reply: instanceName: MessageQ, name: SLAVE_DDR_CORE0[774.538357] , value: 0xb6ec60d8

[774.538374] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[774.538405] NameServer_getRemote: value for MessageQ:SLAVE_DDR_CORE0 not found.

[774.538419] NameServer_getRemote: Sending request via sock: 15

[774.538432] NameServer_getRemote: Requesting from procId 6, MessageQ:[774.538444] SLAVE_DDR_CORE0...

[774.538464] NameServer_getRemote: pending on waitFd: 4

[774.538505] NameServer: back from select()

[774.538519] NameServer: Listener got NameServer message from sock: 16!

[774.538536] listener_cb: recvfrom socket: fd: 16

[774.538548] Received ns msg: byteCount: 176, from addr: 61, [774.538560] from vproc: 5

[774.538571] NameServer Reply: instanceName: MessageQ, name: SLAVE_DDR_CORE0[774.538583] , value: 0xb6ec60d8

[774.538608] NameServer_getRemote: value for MessageQ:SLAVE_DDR_CORE0 not found.

[774.538622] NameServer_getRemote: Sending request via sock: 17

[774.538635] NameServer_getRemote: Requesting from procId 7, MessageQ:[774.538646] SLAVE_DDR_CORE0...

[774.538666] NameServer_getRemote: pending on waitFd: 4

[774.538688] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[774.538717] NameServer: back from select()

[774.538729] NameServer: Listener got NameServer message from sock: 18!

[774.538746] listener_cb: recvfrom socket: fd: 18

[774.538758] Received ns msg: byteCount: 176, from addr: 61, [774.538770] from vproc: 6

[774.538781] NameServer Reply: instanceName: MessageQ, name: SLAVE_DDR_CORE0[774.538794] , value: 0xb6ec60d8

[774.538818] NameServer_getRemote: value for MessageQ:SLAVE_DDR_CORE0 not found.

[774.538833] NameServer_getRemote: Sending request via sock: 19

[774.538845] NameServer_getRemote: Requesting from procId 8, MessageQ:[774.538857] SLAVE_DDR_CORE0...

[774.538877] NameServer_getRemote: pending on waitFd: 4

[774.538900] NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

[774.538930] NameServer: back from select()

[774.538943] NameServer: Listener got NameServer message from sock: 20!

[774.538959] listener_cb: recvfrom socket: fd: 20

[774.538972] Received ns msg: byteCount: 176, from addr: 61, [774.538984] from vproc: 7

[774.539004] NameServer Reply: instanceName: MessageQ, name: SLAVE_DDR_CORE0[774.539017] , value: 0xb6ec60d8

[774.539041] NameServer_getRemote: value for MessageQ:SLAVE_DDR_CORE0 not found.

[774.539055] value = 0x88

[774.539067] status = -5

[774.539079] DONE

[774.539090] Sending response...

[774.539111] Retrieving command...

0 Shankari G over 8 years ago in reply to Anders Klint

TI__Mastermind 43955 points

Hi Anders,

The version of CCS and MCSDK which I use is 5.5 version and the MCSDK 3_00_03_15

I will give my complete bootlogs of booting u-boot, linux and the image processing demo, you can compare it with your bootlogs.

Questions to you:-

1. Are you using the correct filessytem and able to get the ipaddress using which you are launching the image processing demo?

2. Which browser you use? I use Mozilla...

3. Send me the screenshot of the image processing demo which you got in the browser!!.

Regards,

Shankari.

-------------------------------------------------------------------------------------------------------

Please click the Verify Answer button on this post if it answers your question.

--------------------------------------------------------------------------------------------------------

0 Anders Klint over 8 years ago in reply to Shankari G

Intellectual 620 points

Hi Shankari,

1. Not quite sure about your first question - I am able to reach the target using its IP address from the development machine (attaching

screenshot of ping session). How do you define "correct filesystem"?

2,3: Using Mozilla Firefox, screenshot attached.

Regards,

/Anders

0 Anders Klint over 8 years ago in reply to Anders Klint

Intellectual 620 points

Hi Shankari,

We have now tried the provided kernels and filesystems for both mcsdk_3_00_3_15 both rt and "normal" versions.
Using the non-rt version and pre-built binaries I can run the image processing demo ONCE. Trying to run the demo
a second time fails (nothing happens efter pressing "Process" in the browser. Trying to run the rt versions does not
work at all (same behaviour as a second run using the non-rt version).
Based on those observations I am assuming that we should focus on the non-rt versions? What are the differences
in the rt-patched version compared to the "normal" version and which one would you recommend that we use?

Regards
/Anders

0 Anders Klint over 8 years ago in reply to Anders Klint

Intellectual 620 points

Hi Shankari,

It seems that trying to continue using the image processing demo after first time quite repeatedly causes
a more severe crash. I have not been able to precisely reproduce the steps, but a rather detailed list is below
together with a crash dump from the console window running tail -f to look at the lad logfile during the demo run.

Kernel and root fs come unmodified from the mcsdk_3_00_03_15 installation.

Please get in touch if there is anything more you need from me in order to solve this.

Regards
/Anders

Steps to reproduce crash of image processing demo on EVMK2H

Power-cycle board.

In a console window:
Log in to Linux on the EVM as root, then

tail -f /tmp/LAD/lad.txt

Start a Mozilla Firefox browser

Connect to http server of evm board (10.44.0.2 in our case)

Select "cancel" since no display is attached to board

Select "Demonstrations"

Select "Image Processing Demo"

Select "Run"

Select Number of Cores to "Eight"

Select "Browse" an then select "evmc6678l_1587x2182_9_91MB.bmp" from the sample images
provided with the demo.

Select "Process"

Image and result of operation is displayed

Select "Back" in browser (I use the left arrow near top of window).

Select "Process" to run again

<nothing happens, wait a couple of seconds>

Press the big blue up arrow, goes back to Image Processing Demo App startscreen

Press "Run"

<Sometimes changing the number of cores or re-selecting the file>

Crash dump in console window.

---- Crash dump from console window ----

NameServer: Listener got NameServer message from sock: 20!

listener_cb: recvfrom socket: fd: 20

Received ns msg: byteCount: 176, from addr: 61, from vproc: 7

NameServer Reply: instanceName: MessageQ, name: core1_queue, value: 0x19008

NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

NameServer_getRemote: value for MessageQ:core1_queue not found.

value = 0x2

status = -5

DONE

Sending response...

Retrieving command...

LAD_NAMESERVER_GETUINT32: calling NameServer_getUInt32(0x194e8, 'core1_queue')...

NameServer_getLocal: entry key: 'core1_queue' not found!

NameServer_getRemote: Sending request via sock: 5

NameServer_getRemote: Requesting from procId 1, MessageQ:core1_queue...

NameServer_getRemote: pending on waitFd: 4

NameServer: back from select()

NameServer: Listener got NameServer message from sock: 6!

listener_cb: recvfrom socket: fd: 6

Received ns msg: byteCount: 176, from addr: 61, from vproc: 0

NameServer Reply: instanceName: MessageQ, name: core1_queue, value: 0x19008

NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

NameServer_getRemote: value for MessageQ:core1_queue not found.

NameServer_getRemote: Sending request via sock: 7

NameServer_getRemote: Requesting from procId 2, MessageQ:core1_queue...

NameServer_getRemote: pending on waitFd: 4

NameServer: back from select()

NameServer: Listener got NameServer message from sock: 8!

listener_cb: recvfrom socket: fd: 8

Received ns msg: byteCount: 176, from addr: 61, from vproc: 1

NameServer Reply: instanceName: MessageQ, name: core1_queue, value: 0x19008

NameServer: waiting for unblockFd: 2, and socks: maxfd: 21

NameServer_getRemote: value for MessageQ:core1_queue not found.

NameServer_getRemote: Sending request via sock: 9

NameServer_getRemote: Requesting from procId 3, MessageQ:core1_queue...

NameServer_getRemote: pending on waitFd: 4

NameServer: back from select(2013 Nov 25 17:28:07 keystone-evm [ 213.226319] Unable to handle kernel paging request at virtual address acfc9ce6

2013 Nov 25 17:28:07 keystone-evm [ 213.232224] pgd = eca79780

2013 Nov 25 17:28:07 keystone-evm [ 213.234441] [acfc9ce6] *pgd=82cb3e003, *pmd=00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237296] Internal error: Oops: 206 [#1] SMP ARM

2013 Nov 25 17:28:07 keystone-evm [ 213.237337] Process lad_tci6638 (pid: 1687, stack limit = 0xec89e238)

2013 Nov 25 17:28:07 keystone-evm [ 213.237339] Stack: (0xec89fb48 to 0xec8a0000)

2013 Nov 25 17:28:07 keystone-evm [ 213.237343] fb40: 00000000 00000000 00000000 ec89fe5c ecd5c81c ecd5c81c

2013 Nov 25 17:28:07 keystone-evm [ 213.237346] fb60: 00000001 000000b0 ed2c6d80 ec89e000 ecd5d408 c050382c ecd5c800 c038f350

2013 Nov 25 17:28:07 keystone-evm [ 213.237350] fb80: ec89e000 ec89ff78 00000001 ecd5c800 00000000 c039011c 000000d0 00000001

2013 Nov 25 17:28:07 keystone-evm [ 213.237353] fba0: 00000400 0000003d ecd5d400 ec89fbf8 000000db 000000b0 00000000 ec89fbf8

2013 Nov 25 17:28:07 keystone-evm [ 213.237356] fbc0: ec89e000 ec89fbf8 000000b0 ecfd3200 00000000 00000001 000000b0 ed2c6d80

2013 Nov 25 17:28:07 keystone-evm [ 213.237360] fbe0: ec89e000 00000000 000186ac c04fb0f4 000000b0 00000001 5678abcd 00019008

2013 Nov 25 17:28:07 keystone-evm [ 213.237363] fc00: 00000000 00000000 7373654d 51656761 00000000 00000000 00019008 b6e99274

2013 Nov 25 17:28:07 keystone-evm [ 213.237366] fc20: 00000003 31019008 00019008 b6e99274 00000003 00019008 00000039 b6e99290

2013 Nov 25 17:28:07 keystone-evm [ 213.237369] fc40: b6e62b77 00000039 b6e62b51 00019008 b6f42000 00000039 65726f63 75715f31

2013 Nov 25 17:28:07 keystone-evm [ 213.237373] fc60: 00657565 bee39c00 00000003 00000039 b6f3f000 bee39c64 00019514 b6e637e3

2013 Nov 25 17:28:07 keystone-evm [ 213.237376] fc80: 00019008 b6e62f15 61e97889 00000004 000186a8 00019008 b6f3f000 b6e5b4cd

2013 Nov 25 17:28:07 keystone-evm [ 213.237379] fca0: b6f17be5 00017500 00000001 00000000 00000000 00000000 00000000 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237382] fcc0: 00000000 00000000 00000000 00000000 ffffd96f c13f6828 ffffed63 00000002

2013 Nov 25 17:28:07 keystone-evm [ 213.237385] fce0: 00000001 c13f8880 ec89fd8c c07560c0 00000002 c0052090 80000093 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237388] fd00: ec89e000 c0752880 c0752880 ee0d6380 c0752880 00000002 00000002 c13f6828

2013 Nov 25 17:28:07 keystone-evm [ 213.237391] fd20: ee0d6380 00000000 00000000 00000002 c13f8880 00000000 00000000 00000001

2013 Nov 25 17:28:07 keystone-evm [ 213.237394] fd40: 00000060 00001000 00000000 00000fa0 00000000 ec97b1c8 ffffffff 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237397] fd60: ed0e4da8 ffffffe4 00000000 00000003 00000fdc c00a8318 00000020 c05073a4

2013 Nov 25 17:28:07 keystone-evm [ 213.237400] fd80: 00fdc000 00000000 ec89e000 ed0e4d80 00000001 00000000 000000d0 ed0e4d80

2013 Nov 25 17:28:07 keystone-evm [ 213.237404] fda0: ec89e000 ec89fdf0 ec89e000 ec89e000 0000000f ed0e4e7c 00000000 00fdc000

2013 Nov 25 17:28:07 keystone-evm [ 213.237407] fdc0: 00000000 c0518b00 0000000f c0096114 000200da 00000000 ec89fdf0 ec89fdf4

2013 Nov 25 17:28:07 keystone-evm [ 213.237410] fde0: ece94a80 00001000 00000000 00000000 529388a7 15752a00 ec89fed0 ec89fe10

2013 Nov 25 17:28:07 keystone-evm [ 213.237413] fe00: 000000b0 ec89fedc 00000001 c0394600 00000000 00000000 ece94a80 000000b0

2013 Nov 25 17:28:07 keystone-evm [ 213.237416] fe20: edf4f800 ec89fed0 00000000 ec89fedc 00fdc000 00000000 ec89fef8 0000000f

2013 Nov 25 17:28:07 keystone-evm [ 213.237419] fe40: 00000000 ec89fe58 00000000 c00e4e30 00000001 00000000 00000000 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237422] fe60: 00000000 ed2c6d80 00000000 00000000 00000000 00000000 ec89fe10 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237425] fe80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237427] fea0: 00000000 00000000 00000000 00000000 edf4f800 000000b0 00000000 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237431] fec0: bee39b50 c0396070 00fdc000 fffffff7 00000001 bee39c00 00000000 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237434] fee0: 00000000 ec89fed4 00000001 00000000 00000000 00000000 00fdc000 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237436] ff00: 00000000 00000000 0000000f 00000000 0000000f 00000000 00000000 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237439] ff20: 00000000 00000000 ffffffff ec41e800 ffffffe4 b6f42000 ec89ff80 00000001

2013 Nov 25 17:28:07 keystone-evm [ 213.237442] ff40: 0000000f c00cfd9c 00000020 00000001 ece94a80 c00ce750 000186a8 c00ce880

2013 Nov 25 17:28:07 keystone-evm [ 213.237446] ff60: 00000000 00fdc000 00000000 ece94a80 ffffffe4 00000000 ece94a80 000174fc

2013 Nov 25 17:28:07 keystone-evm [ 213.237449] ff80: 00018618 0001724c 00000121 c000dc28 00000000 c03960ac 00000000 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237452] ffa0: 00000000 c000da80 000174fc 00018618 00000005 bee39b50 000000b0 00000000

2013 Nov 25 17:28:07 keystone-evm [ 213.237455] ffc0: 000174fc 00018618 0001724c 00000121 00000001 00017500 00000005 000186ac

2013 Nov 25 17:28:07 keystone-evm [ 213.237458] ffe0: 00000000 bee39aa8 b6f18964 b6f18974 80000010 00000005 ffffffff ffffffff

2013 Nov 25 17:28:07 keystone-evm [ 213.237516] Code: e3caa03f e59a800c e5903010 e3530000 (15933018)

2013 Nov 25 17:32:22 keystone-evm [ 422.145648] Unable to handle kernel NULL pointer dereference at virtual address 00000034

2013 Nov 25 17:32:22 keystone-evm [ 422.152278] pgd = c0003000

2013 Nov 25 17:32:22 keystone-evm [ 422.154566] [00000034] *pgd=80000800004003, *pmd=00000000

2013 Nov 25 17:32:22 keystone-evm [ 422.159068] Internal error: Oops: 207 [#2] SMP ARM

2013 Nov 25 17:32:22 keystone-evm [ 422.163022] Process image_processin (pid: 1944, stack limit = 0xec836238)

2013 Nov 25 17:32:22 keystone-evm [ 422.163023] Stack: (0xec837d5c to 0xec838000)

2013 Nov 25 17:32:22 keystone-evm [ 422.163026] 7d40: 00000000

2013 Nov 25 17:32:22 keystone-evm [ 422.163030] 7d60: c053ce1c 00000000 edbad208 c0126b48 c077bebc edbad208 ecd5de18 c0128084

2013 Nov 25 17:32:22 keystone-evm [ 422.163033] 7d80: ecb6ad80 c077be98 edbad208 c02c6684 c077be98 edbad208 ecd5de18 edf3eda0

2013 Nov 25 17:32:22 keystone-evm [ 422.163036] 7da0: edf3eda0 c02c5b0c ffffffff edbad208 edbad208 c02bf550 edbad208 00000000

2013 Nov 25 17:32:22 keystone-evm [ 422.163039] 7dc0: ee0d7610 c02bf694 edf3ed80 c04fb230 edf3ed80 c03952d8 c0395614 ed3826c0

2013 Nov 25 17:32:22 keystone-evm [ 422.163043] 7de0: edfa6d48 c0395620 c0395614 c00cf43c 00000000 00000000 ecf3ff08 ecb6b050

2013 Nov 25 17:32:22 keystone-evm [ 422.163046] 7e00: ed3823c0 c079ee8c ecb6ad80 ecf1eee0 ecf1ee40 ec836000 ec836000 c003d934

2013 Nov 25 17:32:22 keystone-evm [ 422.163049] 7e20: ed31ac40 003b003b ecb6ad80 ed31ac40 00000000 ecb6ad80 ed31ac80 c0025968

2013 Nov 25 17:32:22 keystone-evm [ 422.163052] 7e40: ed1d0080 ed1d0098 ec836000 00000001 00000000 ecb6b014 003b003b c0030574

2013 Nov 25 17:32:22 keystone-evm [ 422.163056] 7e60: ecb6b014 edbade00 0000000f ec836000 00418004 ecf1eee0 ecf1ee40 ec836000

2013 Nov 25 17:32:22 keystone-evm [ 422.163059] 7e80: 00000009 c0026104 418004fc 00000000 ec837ef4 ecf1eee4 00418004 c0032b44

2013 Nov 25 17:32:22 keystone-evm [ 422.163062] 7ea0: 00000020 ec836000 ecf1f344 418004fc edbade00 ec837ee0 ec837f80 ec837fb0

2013 Nov 25 17:32:22 keystone-evm [ 422.163065] 7ec0: ec836000 fffffe00 ec837ee0 b6f471c8 ec836000 b6f471cc bea8d7bc c0010c00

2013 Nov 25 17:32:22 keystone-evm [ 422.163068] 7ee0: 00000001 ecafe3c0 00000000 00000000 00000000 00000009 00000000 00000000

2013 Nov 25 17:32:22 keystone-evm [ 422.163071] 7f00: 00000000 00000000 00000000 00000000 00001000 00000000 00001000 00000000

2013 Nov 25 17:32:22 keystone-evm [ 422.163074] 7f20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

2013 Nov 25 17:32:22 keystone-evm [ 422.163077] 7f40: 00000002 ecafe3c0 00001000 b6ec1000 ec837f80 00000000 00001000 c00ce810

2013 Nov 25 17:32:22 keystone-evm [ 422.163081] 7f60: 00000000 00000000 00000000 00000000 ecafe3c0 b6ec1000 ec836000 ec836000

2013 Nov 25 17:32:22 keystone-evm [ 422.163084] 7f80: ec836000 c000dc28 ec837fb0 ec836000 00000000 c00112b8 00024178 b6f9fc68

2013 Nov 25 17:32:22 keystone-evm [ 422.163087] 7fa0: bea8d434 00000003 c000dc28 c000dac0 00000004 b6ec1000 00001000 00000000

2013 Nov 25 17:32:22 keystone-evm [ 422.163090] 7fc0: 00024178 b6f9fc68 bea8d434 00000003 00000000 b6fed000 00016e34 bea8d7bc

2013 Nov 25 17:32:22 keystone-evm [ 422.163093] 7fe0: 00000000 bea8d3cc b6f118d9 b6f471c8 40000010 00000004 00000000 00000000

2013 Nov 25 17:32:22 keystone-evm [ 422.163106] Code: e3e0500b eaffffee e92d40f0 e1a06001 (e1d0c3b4)

2013 Nov 25 17:32:22 keystone-evm [ 422.163178] Fixing recursive fault but reboot is needed!

0 Shankari G over 8 years ago in reply to Anders Klint

TI__Mastermind 43955 points

Hi Anders,

Filesystem:

Please use this filesystem: tisdk-rootfs.tar.gz given in the MCSDK package. With this filesystem, it never failed. Please give it a try and not to use the rt-filesystem

Bootargs:

bootargs=earlyprintk debug console=ttyS0,115200n8 ip=dhcp rootwait=1 root=/dev/nfs nfsroot=10.100.1.62:/usr/local/k2hk_fs_3000315,v3,t
cp rw

Bootcmd:

bootcmd=tftpboot 0x87000000 ${tftp_root}/uImage-k2hk-evm.dtb;tftpboot 0x88000000 ${tftp_root}/uImage-keystone-evm.bin;tftpboot 0x0c5f0
000 ${tftp_root}/skern-keystone-evm.bin;mon_install 0x0c5f0000;bootm 0x88000000 - 0x87000000

I have attached the complete bootlogs which includes the u-boot, kernel and Image processing demo.

Please have a look at it. Bootlogs_IMPDemo.odt

When the image processing demo is running, the following is the output logs which I got. Please compare it with yours.

2185.Output_logs_Image_processing

Image processing output screen with processing details:

PS: Please have a look at the attachment.

My suggestion is, if you follow the TI WIKI, step by step, you can get successful in running this demo.

Regards,

Shankari

0 Anders Klint over 8 years ago in reply to Shankari G

Intellectual 620 points

Hi,

I am still able to run the image processing demo ONCE using the non-rt kernels and filesystems.
It seems that our card is using a little different way of setting up the environment but that the end result is the same.
Our environment and bootlog is copied in below and attached, respectively.

Our first-run results match your provided application log (the order of some lined differed) and screenshot.
Your screenshot indicates that the image is processed about 10 ms faster on your system, but I am not sure about
precisely what that time includes - network traffic could be one possibility, I would expect times to be more similar
if it is only computing time once the images are loaded.

Questions:
1. Is is possible for you to run the image processing demo MORE THAN ONCE without reboot?

I have tried the pre-built versions on a EVMK2K board we have in the office, but that one also fails to run more than once (and fails with faultyfile descriptors/failed malloc for the example images of eval boards included in the installation). Got it running once using a smaller .bmp image though. I am not sure which versions of mcsdk that is used on the EVMK2K board.

If the demo application does not survive being run more than once it is of course a waste of time trying to get that working here.

About the bootlog file:

I have copied the skern-keystone-evm.bin file as skern-k2hk-evm.bin in order to make it follow the new naming
scheme and make it easier to switch between kernel versions, so that diff in names in the bootlog is expected.

After boot I ran the image processing demo from a browser (times about 50 to 51) successfully.
The i tried to run it again, first by just going back from result page and pressing "Process" - nothing happened.
Went back to start page of image processing demo (by pressing the blue up arrow, then pressing "Run" and
selecting number of cores and image again, followed by pressing "Process").
This resulted in entires at times 171 to 184.
After this I left the board alone doing some work on my development machine.
At time 367 the board crashed without any user input.

Regards /Anders

Environment:

TCI6638 EVM # printenv

addr_fdt=0x87000000

addr_fs=0x82000000

addr_kern=0x88000000

addr_mon=0x0c5f0000

addr_ubi=0x82000000

addr_uboot=0x87000000

addr_uinitrd=-

args_all=setenv bootargs console=ttyS0,115200n8 rootwait=1 ip=10.1.34.15:::::eth0:off

args_net=setenv bootargs ${bootargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=10.44.0.2:::::eth0:off

args_ramfs=setenv bootargs ${bootargs} earlyprintk rdinit=/sbin/init rw root=/dev/ram0 initrd=0x802000000,9M

args_ubi=setenv bootargs ${bootargs} rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048

args_uinitrd=setenv bootargs ${bootargs} earlyprintk rdinit=/sbin/init rw root=/dev/ram0

baudrate=115200

boot=net

bootargs=console=ttyS0,115200n8 rootwait=1 ip=10.1.34.15:::::eth0:off rootfstype=nfs root=/dev/nfs rw nfsroot=10.44.0.56:/opt/nfshost,v3,tcp,rsize=4096,wsize=4096 ip=10.44.0.2:::::eth0:off

bootcmd=run init_net get_fdt_net get_mon_net get_kern_net run_mon cpu3_on run_kern

bootdelay=3

bootfile=10.112.0.45:rootfs.cpio.gz

burn_ubi=nand erase.part ubifs; nand write ${addr_ubi} ubifs ${filesize}

burn_uboot=sf probe; sf erase 0 0x100000; sf write ${addr_uboot} 0 ${filesize}

cpu3_on=

debug_options=1

dnsip=10.112.0.10

ethact=TCI6638_EMAC

ethaddr=c4:ed:ba:a0:bb:a9

fdt_high=0xffffffff

fileaddr=C5F0000

filesize=B000

get_fdt_net=tftp ${addr_fdt} ${tftp_root}/${name_fdt}

get_fdt_ramfs=tftp ${addr_fdt} ${tftp_root}/${name_fdt}

get_fdt_ubi=ubifsload ${addr_fdt} ${name_fdt}

get_fdt_uinitrd=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}

get_fs_ramfs=tftp ${addr_fs} ${tftp_root}/${name_fs}

get_fs_uinitrd=dhcp ${addr_fs} ${tftp_root}/${name_uinitrd}

get_kern_net=tftp ${addr_kern} ${tftp_root}/${name_kern}

get_kern_ramfs=tftp ${addr_kern} ${tftp_root}/${name_kern}

get_kern_ubi=ubifsload ${addr_kern} ${name_kern}

get_kern_uinitrd=dhcp ${addr_kern} ${tftp_root}/${name_kern}

get_mon_net=tftp ${addr_mon} ${tftp_root}/${name_mon}

get_mon_ramfs=tftp ${addr_mon} ${tftp_root}/${name_mon}

get_mon_ubi=ubifsload ${addr_mon} ${name_mon}

get_mon_uinitrd=dhcp ${addr_mon} ${tftp_root}/${name_mon}

get_ubi_net=dhcp ${addr_ubi} ${tftp_root}/${name_ubi}

get_uboot_net=tftp ${addr_uboot} ${tftp_root}/${name_uboot}

get_uboot_ramfs=tftp ${addr_uboot} ${tftp_root}/${name_uboot}

has_mdio=0

init_net=run set_fs_none args_all args_net

init_ramfs=run set_fs_none args_all args_ramfs get_fs_ramfs

init_ubi=run set_fs_none args_all args_ubi; ubi part ubifs; ubifsmount boot

init_uinitrd=run set_fs_uinitrd args_all args_uinitrd get_fs_uinitrd

initrd_high=0xffffffff

ipaddr=10.44.0.2

mem_lpae=1

mem_reserve=512M

mtdparts=mtdparts=davinci_nand.0:1024k(bootloader)ro,512k(params)ro,129536k(ubifs)

name_fdt=uImage-k2hk-evm.dtb

name_fs=arago-console-image.cpio.gz

name_kern=uImage-keystone-evm.bin

name_mon=skern-k2hk-evm.bin

name_ubi=keystone-evm-ubifs.ubi

name_uboot=u-boot-spi-keystone-evm.gph

name_uinitrd=uinitrd.bin

nfs_options=v3,tcp,rsize=4096,wsize=4096

nfs_root=/opt/nfshost

no_post=1

run_kern=bootm ${addr_kern} ${addr_uinitrd} ${addr_fdt}

run_mon=mon_install ${addr_mon}

serverip=10.44.0.56

set_fs_none=setenv addr_uinitrd -

set_fs_uinitrd=setenv addr_uinitrd ${addr_fs}

stderr=serial

stdin=serial

stdout=serial

tftp_root=.

ver=U-Boot 2013.01 (Nov 24 2013 - 16:43:18)

Environment size: 3392/262140 bytes

TCI6638 EVM #

bootlog_qrt.txt

U-Boot SPL 2013.01 (Nov 24 2013 - 16:43:18)
SF: Detected N25Q128A with page size 64 KiB, total 16 MiB


U-Boot 2013.01 (Nov 24 2013 - 16:43:18)

I2C:   ready
Detected SO-DIMM []
DRAM:  2 GiB
NAND:  512 MiB
Net:   TCI6638_EMAC, TCI6638_EMAC1
Hit any key to stop autoboot:  0 
Using TCI6638_EMAC device
TFTP from server 10.44.0.56; our IP address is 10.44.0.2
Filename './uImage-k2hk-evm.dtb'.
Load address: 0x87000000
Loading: ####
         2.8 MiB/s
done
Bytes transferred = 57857 (e201 hex)
Using TCI6638_EMAC device
TFTP from server 10.44.0.56; our IP address is 10.44.0.2
Filename './skern-k2hk-evm.bin'.
Load address: 0xc5f0000
Loading: ####
         3.1 MiB/s
done
Bytes transferred = 45056 (b000 hex)
Using TCI6638_EMAC device
TFTP from server 10.44.0.56; our IP address is 10.44.0.2
Filename './uImage-keystone-evm.bin'.
Load address: 0x88000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############
         3 MiB/s
done
Bytes transferred = 3990416 (3ce390 hex)
## installed monitor, freq [204800000], status 0
## Booting kernel from Legacy Image at 88000000 ...
   Image Name:   Linux-3.10.10
   Created:      2013-11-24  21:26:00 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3990352 Bytes = 3.8 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 87000000
   Booting using the fdt blob at 0x87000000
   Loading Kernel Image ... OK
OK
   Using Device Tree in place at 87000000, end 87011200

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.10.10 (gtbldadm@ubuntu-12) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #1 SMP Sun Nov 24 16:25:07 EST 2013
[    0.000000] CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), cr=30c7387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine: KeyStone2, model: Texas Instruments Keystone 2 SoC
[    0.000000] switching to high address space at 0x800000000
[    0.000000] cma: CMA: reserved 16 MiB at 2e800000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map
[    0.000000] PERCPU: Embedded 8 pages/cpu @c13e6000 s12032 r8192 d12544 u32768
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 391696
[    0.000000] Kernel command line: console=ttyS0,115200n8 rootwait=1 ip=10.1.34.15:::::eth0:off rootfstype=nfs root=/dev/nfs rw nfsroot=10.44.0.56:/opt/nfshost,v3,tcp,rsize=4096,wsize=4096 ip=10.44.0.2:::::eth0:off
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1536MB = 1536MB total
[    0.000000] Memory: 1535072k/1535072k available, 37792k reserved, 794624K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06ff570   (7134 kB)
[    0.000000]       .init : 0xc0700000 - 0xc0752f00   ( 332 kB)
[    0.000000]       .data : 0xc0754000 - 0xc0798e68   ( 276 kB)
[    0.000000]        .bss : 0xc0798e68 - 0xc07c78bc   ( 187 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ipc irq: irqchip registered, range 512-539
[    0.000000] main_pll_clk rate is 1228800000, postdiv = 2, mult = 19,prediv = 0
[    0.000000] pll_clk parent_rate(122880000 Hz), rate(327680000 Hz),postdiv = 6, mult = 15, prediv = 0
[    0.000000] Architected local timer running at 204.80MHz (phys).
[    0.000000] Switching to timer-based delay loop
[    0.000000] sched_clock: ARM arch timer >56 bits at 204800kHz, resolution 4ns
[    0.000000] keystone timer clock @204800000 MHz
[    0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
[    0.000000] Console: colour dummy device 80x30
[    7.352028] Calibrating delay loop (skipped), value calculated using timer frequency.. 409.60 BogoMIPS (lpj=2048000)
[    7.352035] pid_max: default: 4096 minimum: 301
[    7.352131] Mount-cache hash table entries: 512
[    7.358380] CPU: Testing write buffer coherency: ok
[    7.358511] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    7.358521] Setting up static identity map for 0xc050a688 - 0xc050a6bc
[    7.397381] CPU1: Booted secondary processor
[    7.397401] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    7.436064] CPU2: Booted secondary processor
[    7.436086] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    7.474739] CPU3: Booted secondary processor
[    7.474761] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    7.474857] Brought up 4 CPUs
[    7.474872] SMP: Total of 4 processors activated (1638.40 BogoMIPS).
[    7.474876] CPU: All CPU(s) started in SVC mode.
[    7.485473] NET: Registered protocol family 16
[    7.486236] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    7.493488] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    7.493493] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    7.500955] bio: create slab <bio-0> at 0
[    7.501199] keystone-pcie: keystone_pcie_rc_init - start
[    7.501269] keystone2_pcie_serdes_setup
[    7.502966] keystone2_pcie_serdes_setup done, en_link_train = 1
[    7.502994] keystone-pcie: MEM 0x0000000050000000..0x000000005fffffff -> 0x0000000050000000 
[    7.503001] keystone-pcie: IO 0x0000000024000000..0x0000000024003fff -> 0x0000000000000000
[    7.503030] keystone-pcie: pcie - number of legacy irqs = 4
[    7.503071] keystone-pcie: pcie - number of MSI host irqs = 8, msi_irqs = 32
[    7.589602] keystone-pcie: Doing PCI Setup...Done
[    7.589606] keystone-pcie: Starting PCI scan...
[    7.589702] PCI host bridge to bus 0000:00
[    7.589711] pci_bus 0000:00: root bus resource [mem 0x50000000-0x5fffffff]
[    7.589717] pci_bus 0000:00: root bus resource [io  0x0000-0x3fff]
[    7.589723] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    7.589757] PCI: bus0: Fast back to back transfers enabled
[    7.589770] keystone-pcie: Ending PCI scan...
[    7.589776] keystone-pcie: keystone_pcie_rc_init - end
[    7.589909] vgaarb: loaded
[    7.590158] SCSI subsystem initialized
[    7.590443] usbcore: registered new interface driver usbfs
[    7.590511] usbcore: registered new interface driver hub
[    7.590587] usbcore: registered new device driver usb
[    7.591575] pca953x 2-0020: failed reading register
[    7.591587] pca953x: probe of 2-0020 failed with error -121
[    7.591721] pps_core: LinuxPPS API ver. 1 registered
[    7.591725] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    7.591774] PTP clock support registered
[    7.591875] keystone-hwqueue hwqueue.4: qmgr start queue 0, number of queues 8192
[    7.591938] keystone-hwqueue hwqueue.4: added qmgr start queue 0, num of queues 8192, reg_peek f0040000, reg_status f0004000, reg_config f0006000, reg_region f0008000, reg_push f0080000, reg_pop f00c0000
[    7.591946] keystone-hwqueue hwqueue.4: qmgr start queue 8192, number of queues 8192
[    7.592004] keystone-hwqueue hwqueue.4: added qmgr start queue 8192, num of queues 8192, reg_peek f0100000, reg_status f000a400, reg_config f000c000, reg_region f000e000, reg_push f0140000, reg_pop f0180000
[    7.592664] keystone-hwqueue hwqueue.4: qos: sched port @8096, drop sched @8000
[    7.593418] keystone-hwqueue hwqueue.4: qos: sched port @6496, drop sched @6400
[    7.594152] keystone-hwqueue hwqueue.4: added pool pool-net: 2048 descriptors of size 128
[    7.594160] keystone-hwqueue hwqueue.4: added pool pool-rio: 128 descriptors of size 256
[    7.594168] keystone-hwqueue hwqueue.4: added pool pool-udma: 1636 descriptors of size 256
[    7.594175] keystone-hwqueue hwqueue.4: added pool pool-xge: 1024 descriptors of size 128
[    7.594182] keystone-hwqueue hwqueue.4: added pool pool-crypto: 1024 descriptors of size 128
[    7.595970] keystone-hwqueue hwqueue.4: registered queues 0-16383
[    7.596234] keystone-hwqueue hwqueue.4: qos version 0x2000106, magic valid
[    7.596641] keystone-hwqueue hwqueue.4: qos version 0x2000106, magic valid
[    7.601130] keystone-pktdma 2004000.pktdma: registered 26 logical channels, flows 32, tx chans: 9, rx chans: 24
[    7.603283] keystone-pktdma 2a08000.pktdma: registered 24 logical channels, flows 32, tx chans: 32, rx chans: 32, loopback
[    7.603714] keystone-pktdma 2fa1000.pktdma: registered 4 logical channels, flows 32, tx chans: 16, rx chans: 16
[    7.603835] Switching to clocksource arch_sys_counter
[    7.616992] NET: Registered protocol family 2
[    7.617284] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    7.617374] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    7.617463] TCP: Hash tables configured (established 8192 bind 8192)
[    7.617500] TCP: reno registered
[    7.617507] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    7.617527] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    7.617674] NET: Registered protocol family 1
[    7.617801] RPC: Registered named UNIX socket transport module.
[    7.617805] RPC: Registered udp transport module.
[    7.617809] RPC: Registered tcp transport module.
[    7.617812] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    7.618092] hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver, 7 counters available
[    7.677912] bounce pool size: 64 pages
[    7.684693] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    7.684841] NTFS driver 2.1.30 [Flags: R/O].
[    7.685046] jffs2: version 2.2. (NAND) ?© 2001-2006 Red Hat, Inc.
[    7.685304] msgmni has been set to 1478
[    7.686875] NET: Registered protocol family 38
[    7.687055] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    7.687060] io scheduler noop registered
[    7.687065] io scheduler deadline registered
[    7.687173] io scheduler cfq registered (default)
[    7.688081] keystone-udma udma0.5: registered udma device udma0
[    7.722677] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    7.723720] 2530c00.serial: ttyS0 at MMIO 0x2530c00 (irq = 309) is a 16550A
[    8.397024] console [ttyS0] enabled
[    8.400299] 2531000.serial: ttyS1 at MMIO 0x2531000 (irq = 312) is a 16550A
[    8.408110] loop: module loaded
[    8.410779] at24 0-0050: 131072 byte 24c1024 EEPROM, writable, 1 bytes/write
[    8.417820] Generic platform RAM MTD, (c) 2004 Simtec Electronics
[    8.423496] ONFI param page 0 valid
[    8.426345] ONFI flash detected
[    8.428911] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xac (Micron MT29F4G08ABBDAHC), 512MiB, page size: 2048, OOB size: 64
[    8.438420] Bad block table found at page 262080, version 0x01
[    8.443510] Bad block table found at page 262016, version 0x01
[    8.448490] 3 ofpart partitions found on MTD device 30000000.nand
[    8.453469] Creating 3 MTD partitions on "30000000.nand":
[    8.457887] 0x000000000000-0x000000100000 : "u-boot"
[    8.462400] 0x000000100000-0x000000180000 : "params"
[    8.466891] 0x000000180000-0x000020000000 : "ubifs"
[    8.471444] davinci_nand 30000000.nand: controller rev. 2.5
[    8.476482] spi_davinci 21000400.spi: master is unqueued, this is deprecated
[    8.482459] m25p80 spi32766.0: found n25q128a11, expected n25q128
[    8.487441] m25p80 spi32766.0: n25q128a11 (16384 Kbytes)
[    8.491795] 2 ofpart partitions found on MTD device spi32766.0
[    8.496561] Creating 2 MTD partitions on "spi32766.0":
[    8.500766] 0x000000000000-0x000000080000 : "u-boot-spl"
[    8.505529] 0x000000080000-0x000001000000 : "test"
[    8.510092] spi_davinci 21000400.spi: Controller at 0xf0078400
[    8.515103] spi_davinci 21000600.spi: master is unqueued, this is deprecated
[    8.520866] spi_davinci 21000600.spi: Controller at 0xf007a600
[    8.525877] spi_davinci 21000800.spi: master is unqueued, this is deprecated
[    8.531646] spi_davinci 21000800.spi: Controller at 0xf007c800
[    8.537165] libphy: GPIO Bitbanged MDIO: probed
[    8.541464] mdio_bus gpio-ffffffed: cannot get PHY at address 0
[    8.546892] mdio_bus gpio-ffffffed: cannot get PHY at address 1
[    8.551788] tun: Universal TUN/TAP device driver, 1.6
[    8.555921] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    8.561313] keystone-netcp 2f00000.netcp: No streaming regs defined
[    8.566514] keystone-netcp 2090000.netcp: cpts rftclk freq not defined
[    8.571894] netif_napi_add() called with weight 128 on device eth%d
[    8.577662] keystone-netcp 2090000.netcp: Created interface "eth0"
[    8.582724] keystone-netcp 2090000.netcp: dma_chan_name nettx0
[    8.588135] keystone-netcp 2090000.netcp: Created interface "eth1"
[    8.593190] keystone-netcp 2090000.netcp: dma_chan_name nettx1
[    8.598857] keystone-netcp 2f00000.netcp: Created interface "eth2"
[    8.603919] keystone-netcp 2f00000.netcp: dma_chan_name xgetx0
[    8.608978] keystone-netcp 2f00000.netcp: Created interface "eth3"
[    8.614040] keystone-netcp 2f00000.netcp: dma_chan_name xgetx1
[    8.619586] keystone-dwc3 2690000.dwc: usbss revision 47914300
[    8.624376] keystone-dwc3 2690000.dwc: mapped irq 425 to virq 608
[    8.794554] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    8.799045] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[    8.805771] xhci-hcd xhci-hcd.0.auto: irq 608, io mem 0x02690000
[    8.810744] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    8.816297] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    8.822200] usb usb1: Product: xHCI Host Controller
[    8.826191] usb usb1: Manufacturer: Linux 3.10.10 xhci-hcd
[    8.830673] usb usb1: SerialNumber: xhci-hcd.0.auto
[    8.834939] hub 1-0:1.0: USB hub found
[    8.838007] hub 1-0:1.0: 1 port detected
[    8.841358] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    8.845846] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[    8.852168] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    8.857722] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    8.863626] usb usb2: Product: xHCI Host Controller
[    8.867616] usb usb2: Manufacturer: Linux 3.10.10 xhci-hcd
[    8.872098] usb usb2: SerialNumber: xhci-hcd.0.auto
[    8.876344] hub 2-0:1.0: USB hub found
[    8.879410] hub 2-0:1.0: 1 port detected
[    8.882881] usbcore: registered new interface driver usb-storage
[    8.887941] mousedev: PS/2 mouse device common for all mice
[    8.892660] i2c /dev entries driver
[    8.895941] watchdog 22f0080.wdt: heartbeat 60 sec
[    8.909001] keystone-crypto 20c0000.crypto: crypto accelerator enabled
[    8.914618] usbcore: registered new interface driver usbhid
[    8.919171] usbhid: USB HID core driver
[    8.922515]  remoteproc0: 2620040.dsp0 is available
[    8.926512]  remoteproc0: Note: remoteproc is still under development and considered experimental.
[    8.933841]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    8.942322]  remoteproc0: no firmware found
[    8.945831] rproc-user 2620040.dsp0: registered misc device dsp0
[    8.950914]  remoteproc1: 2620044.dsp1 is available
[    8.954900]  remoteproc1: Note: remoteproc is still under development and considered experimental.
[    8.962229]  remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    8.970712]  remoteproc1: no firmware found
[    8.974214] rproc-user 2620044.dsp1: registered misc device dsp1
[    8.979286]  remoteproc2: 2620048.dsp2 is available
[    8.983279]  remoteproc2: Note: remoteproc is still under development and considered experimental.
[    8.990608]  remoteproc2: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    8.999087]  remoteproc2: no firmware found
[    9.002582] rproc-user 2620048.dsp2: registered misc device dsp2
[    9.007656]  remoteproc3: 262004c.dsp3 is available
[    9.011642]  remoteproc3: Note: remoteproc is still under development and considered experimental.
[    9.018972]  remoteproc3: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    9.027459]  remoteproc3: no firmware found
[    9.030962] rproc-user 262004c.dsp3: registered misc device dsp3
[    9.036026]  remoteproc4: 2620050.dsp4 is available
[    9.040019]  remoteproc4: Note: remoteproc is still under development and considered experimental.
[    9.047348]  remoteproc4: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    9.055826]  remoteproc4: no firmware found
[    9.059319] rproc-user 2620050.dsp4: registered misc device dsp4
[    9.064397]  remoteproc5: 2620054.dsp5 is available
[    9.068382]  remoteproc5: Note: remoteproc is still under development and considered experimental.
[    9.075713]  remoteproc5: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    9.084191]  remoteproc5: no firmware found
[    9.087689] rproc-user 2620054.dsp5: registered misc device dsp5
[    9.092753]  remoteproc6: 2620058.dsp6 is available
[    9.096747]  remoteproc6: Note: remoteproc is still under development and considered experimental.
[    9.104076]  remoteproc6: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    9.112562]  remoteproc6: no firmware found
[    9.116060] rproc-user 2620058.dsp6: registered misc device dsp6
[    9.121136]  remoteproc7: 262005c.dsp7 is available
[    9.125120]  remoteproc7: Note: remoteproc is still under development and considered experimental.
[    9.132450]  remoteproc7: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    9.140930]  remoteproc7: no firmware found
[    9.144429] rproc-user 262005c.dsp7: registered misc device dsp7
[    9.149352] rproc-user dspmem.3: kick gpio
[    9.152790] rproc-user dspmem.3: registered misc device dspmem
[    9.157799] oprofile: using arm/armv7-ca15
[    9.161179] GACT probability on
[    9.163744] Mirror/redirect action on
[    9.166734] Failed to load ipt action
[    9.169729] Simple TC action Loaded
[    9.172898] netem: version 1.3
[    9.175394] u32 classifier
[    9.177610]     Performance counters on
[    9.180741]     input device check on
[    9.183730]     Actions configured
[    9.186518] Netfilter messages via NETLINK v0.30.
[    9.190367] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    9.195662] ctnetlink v0.93: registering with nfnetlink.
[    9.200189] ipip: IPv4 over IPv4 tunneling driver
[    9.204334] gre: GRE over IPv4 demultiplexor driver
[    9.208320] ip_gre: GRE over IPv4 tunneling driver
[    9.212902] ip_tables: (C) 2000-2006 Netfilter Core Team
[    9.217289] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
[    9.222511] arp_tables: (C) 2002 David S. Miller
[    9.226313] TCP: cubic registered
[    9.229018] Initializing XFRM netlink socket
[    9.232890] NET: Registered protocol family 10
[    9.237419] NET: Registered protocol family 17
[    9.241060] NET: Registered protocol family 15
[    9.244725] Bridge firewalling registered
[    9.248002] Ebtables v2.0 registered
[    9.283244] 8021q: 802.1Q VLAN Support v1.8
[    9.288086] sctp: Hash tables configured (established 65536 bind 65536)
[    9.293612] NET: Registered protocol family 41
[    9.297367] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    9.303645] Registering SWP/SWPB emulation handler
[    9.310838] keystone-netcp 2090000.netcp: initializing cpsw version 1.3 (1) SGMII identification value 0x4ed1
[    9.319055] keystone-netcp 2090000.netcp: Created a cpsw ale engine
[    9.326592] pps pps0: new PPS source ptp0
[    9.329881] cpts rftclk rate(614400000 HZ),mult(1747626667),shift(30)
[    9.363401] keystone-netcp 2090000.netcp: Using Packet Accelerator Firmware version 0x02000104
[    9.370451] keystone-netcp 2090000.netcp: pa_clk_rate(163840000 HZ),mult(25000),shift(12)
[    9.380474] net eth0: netcp device eth0 opened
[    9.385439] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    9.390210] 8021q: adding VLAN 0 to HW filter on device eth0
[    9.394836] net eth0: adding rx vlan id: 0
[    9.414369] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    9.430720] IP-Config: Guessing netmask 255.0.0.0
[    9.434618] IP-Config: Complete:
[    9.437256]      device=eth0, hwaddr=c4:ed:ba:a0:bb:a9, ipaddr=10.44.0.2, mask=255.0.0.0, gw=255.255.255.255
[    9.445307]      host=10.44.0.2, domain=, nis-domain=(none)
[    9.449877]      bootserver=255.255.255.255, rootserver=10.44.0.56, rootpath=
[    9.460537] VFS: Mounted root (nfs filesystem) on device 0:11.
[    9.465481] Freeing unused kernel memory: 328K (c0700000 - c0752000)
INIT: version 2.88 booting
Starting udev
Starting Bootlog daemon: bootlogd.
NOT configuring network interfaces: / is an NFS mount
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
Mon Nov 25 17:24:00 UTC 2013
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Starting Dropbear SSH server: dropbear.
Starting mpmsrv daemon.
Starting telnet daemon.
#>>>>> LCD 12
IP Address:
10.44.0.2
Starting tiipclad daemon.
Starting network benchmark server: netserver.
Starting syslog-ng:.
Starting thttpd.
Starting Lighttpd Web Server: lighttpd.
2013-11-25 17:24:00: (log.c.166) server started 
* starting FTP Server: vsftpd... done.
***************************************************************
***************************************************************
NOTICE: This file system contains the followin GPLv3 packages:
        binutils-symlinks
        binutils
        gdb
        gdbserver

If you do not wish to distribute GPLv3 components please remove
the above packages prior to distribution.  This can be done using
the opkg remove command.  i.e.:
    opkg remove <package>
Where <package> is the name printed in the list above

NOTE: If the package is a dependency of another package you
      will be notified of the dependent packages.  You should
      use the --force-removal-of-dependent-packages option to
      also remove the dependent packages as well
***************************************************************
***************************************************************
Stopping Bootlog daemon: bootlogd.

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

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

Arago 2013.04 keystone-evm ttyS0

keystone-evm login: [   50.336230]  remoteproc0: powering up 2620040.dsp0
[   50.343539] virtio_rpmsg_bus virtio0: rpmsg host is online
[   50.348207]  remoteproc0: registered virtio0 (type 7)
[   50.374043]  remoteproc1: powering up 2620044.dsp1
[   50.381355] virtio_rpmsg_bus virtio1: rpmsg host is online
[   50.385966]  remoteproc1: registered virtio1 (type 7)
[   50.412203]  remoteproc2: powering up 2620048.dsp2
[   50.418410] virtio_rpmsg_bus virtio2: rpmsg host is online
[   50.422939]  remoteproc2: registered virtio2 (type 7)
[   50.449228]  remoteproc3: powering up 262004c.dsp3
[   50.453493] virtio_rpmsg_bus virtio0: creating channel rpmsg-proto addr 0x3d
[   50.459690] rpmsg_proto rpmsg0: inserting rpmsg src: 1024, dst: 61
[   50.466552] virtio_rpmsg_bus virtio3: rpmsg host is online
[   50.471171]  remoteproc3: registered virtio3 (type 7)
[   50.497483]  remoteproc4: powering up 2620050.dsp4
[   50.503455] virtio_rpmsg_bus virtio4: rpmsg host is online
[   50.508133]  remoteproc4: registered virtio4 (type 7)
[   50.533949]  remoteproc5: powering up 2620054.dsp5
[   50.539934] virtio_rpmsg_bus virtio5: rpmsg host is online
[   50.544502]  remoteproc5: registered virtio5 (type 7)
[   50.570071]  remoteproc6: powering up 2620058.dsp6
[   50.576390] virtio_rpmsg_bus virtio6: rpmsg host is online
[   50.581073]  remoteproc6: registered virtio6 (type 7)
[   50.595825] virtio_rpmsg_bus virtio1: creating channel rpmsg-proto addr 0x3d
[   50.601721] rpmsg_proto rpmsg1: inserting rpmsg src: 1024, dst: 61
[   50.617984]  remoteproc7: powering up 262005c.dsp7
[   50.623968] virtio_rpmsg_bus virtio7: rpmsg host is online
[   50.628506]  remoteproc7: registered virtio7 (type 7)
[   50.733674] virtio_rpmsg_bus virtio2: creating channel rpmsg-proto addr 0x3d
[   50.739566] rpmsg_proto rpmsg2: inserting rpmsg src: 1024, dst: 61
[   50.836184] virtio_rpmsg_bus virtio3: creating channel rpmsg-proto addr 0x3d
[   50.842068] rpmsg_proto rpmsg3: inserting rpmsg src: 1024, dst: 61
[   50.923022] virtio_rpmsg_bus virtio4: creating channel rpmsg-proto addr 0x3d
[   50.928888] rpmsg_proto rpmsg4: inserting rpmsg src: 1024, dst: 61
[   50.988046] virtio_rpmsg_bus virtio5: creating channel rpmsg-proto addr 0x3d
[   50.993930] rpmsg_proto rpmsg5: inserting rpmsg src: 1024, dst: 61
[   51.027928] virtio_rpmsg_bus virtio6: creating channel rpmsg-proto addr 0x3d
[   51.033788] rpmsg_proto rpmsg6: inserting rpmsg src: 1024, dst: 61
[   51.052751] virtio_rpmsg_bus virtio7: creating channel rpmsg-proto addr 0x3d
[   51.058580] rpmsg_proto rpmsg7: inserting rpmsg src: 1024, dst: 61
[  171.423958] rpmsg_proto rpmsg0: deleting rpmsg src: 1024, dst: 61
[  171.429375]  remoteproc0: stopped remote processor 2620040.dsp0
[  171.464024] rpmsg_proto rpmsg1: deleting rpmsg src: 1024, dst: 61
[  171.469279]  remoteproc1: stopped remote processor 2620044.dsp1
[  171.503776] rpmsg_proto rpmsg2: deleting rpmsg src: 1024, dst: 61
[  171.508997]  remoteproc2: stopped remote processor 2620048.dsp2
[  171.543661] rpmsg_proto rpmsg3: deleting rpmsg src: 1024, dst: 61
[  171.548875]  remoteproc3: stopped remote processor 262004c.dsp3
[  171.583633] rpmsg_proto rpmsg4: deleting rpmsg src: 1024, dst: 61
[  171.588877]  remoteproc4: stopped remote processor 2620050.dsp4
[  171.623658] rpmsg_proto rpmsg5: deleting rpmsg src: 1024, dst: 61
[  171.629020]  remoteproc5: stopped remote processor 2620054.dsp5
[  171.663835] rpmsg_proto rpmsg6: deleting rpmsg src: 1024, dst: 61
[  171.669103]  remoteproc6: stopped remote processor 2620058.dsp6
[  171.704107] rpmsg_proto rpmsg7: deleting rpmsg src: 1024, dst: 61
[  171.709357]  remoteproc7: stopped remote processor 262005c.dsp7
[  173.558479]  remoteproc0: powering up 2620040.dsp0
[  173.563842] virtio_rpmsg_bus virtio0: rpmsg host is online
[  173.568403]  remoteproc0: registered virtio0 (type 7)
[  173.580640] virtio_rpmsg_bus virtio0: creating channel rpmsg-proto addr 0x3d
[  173.586482] rpmsg_proto rpmsg56: inserting rpmsg src: 1024, dst: 61
[  173.604400]  remoteproc1: powering up 2620044.dsp1
[  173.609485] virtio_rpmsg_bus virtio1: rpmsg host is online
[  173.613979]  remoteproc1: registered virtio1 (type 7)
[  173.626414] virtio_rpmsg_bus virtio1: creating channel rpmsg-proto addr 0x3d
[  173.632251] rpmsg_proto rpmsg57: inserting rpmsg src: 1024, dst: 61
[  173.650553]  remoteproc2: powering up 2620048.dsp2
[  173.655671] virtio_rpmsg_bus virtio2: rpmsg host is online
[  173.660197]  remoteproc2: registered virtio2 (type 7)
[  173.672580] virtio_rpmsg_bus virtio2: creating channel rpmsg-proto addr 0x3d
[  173.678403] rpmsg_proto rpmsg58: inserting rpmsg src: 1024, dst: 61
[  173.696001]  remoteproc3: powering up 262004c.dsp3
[  173.701014] virtio_rpmsg_bus virtio3: rpmsg host is online
[  173.705520]  remoteproc3: registered virtio3 (type 7)
[  173.718508] virtio_rpmsg_bus virtio3: creating channel rpmsg-proto addr 0x3d
[  173.724466] rpmsg_proto rpmsg59: inserting rpmsg src: 1024, dst: 61
[  173.741101]  remoteproc4: powering up 2620050.dsp4
[  173.746173] virtio_rpmsg_bus virtio4: rpmsg host is online
[  173.750665]  remoteproc4: registered virtio4 (type 7)
[  173.763140] virtio_rpmsg_bus virtio4: creating channel rpmsg-proto addr 0x3d
[  173.768966] rpmsg_proto rpmsg60: inserting rpmsg src: 1024, dst: 61
[  173.787212]  remoteproc5: powering up 2620054.dsp5
[  173.792178] virtio_rpmsg_bus virtio5: rpmsg host is online
[  173.796756]  remoteproc5: registered virtio5 (type 7)
[  173.809323] virtio_rpmsg_bus virtio5: creating channel rpmsg-proto addr 0x3d
[  173.815235] rpmsg_proto rpmsg61: inserting rpmsg src: 1024, dst: 61
[  173.832124]  remoteproc6: powering up 2620058.dsp6
[  173.837418] virtio_rpmsg_bus virtio6: rpmsg host is online
[  173.841910]  remoteproc6: registered virtio6 (type 7)
[  173.854181] virtio_rpmsg_bus virtio6: creating channel rpmsg-proto addr 0x3d
[  173.860005] rpmsg_proto rpmsg62: inserting rpmsg src: 1024, dst: 61
[  173.877324]  remoteproc7: powering up 262005c.dsp7
[  173.882304] virtio_rpmsg_bus virtio7: rpmsg host is online
[  173.886807]  remoteproc7: registered virtio7 (type 7)
[  173.899405] virtio_rpmsg_bus virtio7: creating channel rpmsg-proto addr 0x3d
[  173.905250] rpmsg_proto rpmsg63: inserting rpmsg src: 1024, dst: 61
[  176.269083] virtio_rpmsg_bus virtio0: msg received with no recipient
[  184.471503] virtio_rpmsg_bus virtio0: msg received with no recipient
[  367.937516] Unable to handle kernel NULL pointer dereference at virtual address 00000034
[  367.944132] pgd = c0003000
[  367.946351] [00000034] *pgd=80000800004003, *pmd=00000000
[  367.949561] Internal error: Oops: 207 [#1] SMP ARM
[  367.949564] Modules linked in:
[  367.949569] CPU: 2 PID: 1831 Comm: image_processin Not tainted 3.10.10 #1
[  367.949572] task: ee3ebb80 ti: ec87a000 task.ti: ec87a000
[  367.949584] PC is at sysfs_find_dirent+0x8/0xf0
[  367.949587] LR is at sysfs_get_dirent+0x28/0x78
[  367.949591] pc : [<c012697c>]    lr : [<c0126b48>]    psr: 60000013
[  367.949591] sp : ec87bd5c  ip : 00000000  fp : ec95e908
[  367.949593] r10: 00000008  r9 : 00000000  r8 : edf58320
[  367.949595] r7 : ed34d408  r6 : 00000000  r5 : c053ce1c  r4 : 00000000
[  367.949597] r3 : ee3ebb80  r2 : c053ce1c  r1 : 00000000  r0 : 00000000
[  367.949600] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[  367.949602] Control: 30c5387d  Table: 2cf9cc40  DAC: 55555555
[  367.949605] Process image_processin (pid: 1831, stack limit = 0xec87a238)
[  367.949607] Stack: (0xec87bd5c to 0xec87c000)
[  367.949610] bd40:                                                                00000000
[  367.949614] bd60: c053ce1c 00000000 ed34d408 c0126b48 c077bebc ed34d408 ecd1e818 c0128084
[  367.949617] bd80: ee3ebb80 c077be98 ed34d408 c02c6684 c077be98 ed34d408 ecd1e818 edf58320
[  367.949620] bda0: edf58320 c02c5b0c ffffffff ed34d408 ed34d408 c02bf550 ed34d408 00000000
[  367.949623] bdc0: ee0d7610 c02bf694 edf58300 c04fb230 edf58300 c03952d8 c0395614 ec95e900
[  367.949626] bde0: edf7ec38 c0395620 c0395614 c00cf43c 00000000 00000000 ee30b608 ee3ebe50
[  367.949630] be00: edaa2d80 c079ee8c ee3ebb80 ee31df20 ee31de80 ec87a000 ec87a000 c003d934
[  367.949633] be20: ecf47500 00420042 ee3ebb80 ecf47500 00000000 ee3ebb80 ecf47540 c0025968
[  367.949636] be40: ed1ca780 ed1ca798 ec87a000 00000001 00000000 ee3ebe14 00420042 c0030574
[  367.949639] be60: ee3ebe14 ecaffa00 0000000f ec87a000 00418004 ee31df20 ee31de80 ec87a000
[  367.949642] be80: 00000009 c0026104 418004fc 00000000 ec87bef4 ee31df24 00418004 c0032b44
[  367.949646] bea0: 00000020 ec87a000 ee31e384 418004fc ecaffa00 ec87bee0 ec87bf80 ec87bfb0
[  367.949649] bec0: ec87a000 fffffe00 ec87bee0 b6e721c8 ec87a000 b6e721cc be9897bc c0010c00
[  367.949652] bee0: 00000001 ecb590c0 00000000 00000000 00000000 00000009 00000000 00000000
[  367.949655] bf00: 00000000 00000000 00000000 00000000 00001000 00000000 00001000 00000000
[  367.949657] bf20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  367.949660] bf40: 00000002 ecb590c0 00001000 b6dec000 ec87bf80 00000000 00001000 c00ce810
[  367.949663] bf60: 00000000 00000000 00000000 00000000 ecb590c0 b6dec000 ec87a000 ec87a000
[  367.949667] bf80: ec87a000 c000dc28 ec87bfb0 ec87a000 00000000 c00112b8 00024178 b6ecac68
[  367.949670] bfa0: be989434 00000003 c000dc28 c000dac0 00000004 b6dec000 00001000 00000000
[  367.949673] bfc0: 00024178 b6ecac68 be989434 00000003 00000000 b6f18000 00016e34 be9897bc
[  367.949676] bfe0: 00000000 be9893cc b6e3c8d9 b6e721c8 40000010 00000004 00000000 00000000
[  367.949685] [<c012697c>] (sysfs_find_dirent+0x8/0xf0) from [<ecd1e818>] (0xecd1e818)
[  367.949690] Code: e3e0500b eaffffee e92d40f0 e1a06001 (e1d0c3b4) 
[  367.949693] ---[ end trace ba3a9f007ad2994b ]---
[  367.949695] Fixing recursive fault but reboot is needed!

0 Shankari G over 8 years ago in reply to Anders Klint

TI__Mastermind 43955 points

Hi Anders,

Anders said:
1. Is is possible for you to run the image processing demo MORE THAN ONCE without reboot?

yes with the filesystem ( mentioned in my previuos post, i.e., tisdk-rootfs.tar.gz ) able to run it repeatedly many times, without any issue, without reboot.

Regards,

Shankari.

-------------------------------------------------------------------------------------------------------

Please click the Verify Answer button on this post if it answers your question.

--------------------------------------------------------------------------------------------------------

0 Anders Klint over 8 years ago in reply to Shankari G

Intellectual 620 points

Hi,
I think we let this issue get quite far off-topic and I'd like to bring it back on track.

The issue is that I get different results when rebuilding the bios app messageq_single.xe66
depending on whether I build it with the provided makefiles (make -f ipc_bios.mak) which works
OR importing the source into CCS and building with the same config files - which does NOT work.

I do need to get IPC working - if its not doable with CCS then I'd be happy to settle for a command-line
based build system, but I would like something faster than rebuilding the whole test suite.

I have tried again to build the image processing demo from mcsdk_bios_3_01_03_06 using CCS 6.0.1
but that fails to build and I think we should put that into a separate issue.

Regards
/Anders

0 Shankari G over 8 years ago in reply to Anders Klint

TI__Mastermind 43955 points

Hi Anders,

I do need to get IPC working - if its not doable with CCS then I'd be happy to settle for a command-line
based build system, but I would like something faster than rebuilding the whole test suite.

It is also doable with CCS.

I have tried again to build the image processing demo from mcsdk_bios_3_01_03_06 using CCS 6.0.1
but that fails to build and I think we should put that into a separate issue.

Create a new post for this issue.

0 Anders Klint over 8 years ago in reply to Shankari G

Intellectual 620 points

Hi,

Great to hear that it is doable in CCS!

Where did we go wrong? My attempts to build this project with one source file and two config files is described - at length - in the beginning of this thread, can you _please_ read through that and compare with what you get when you build it? Also if I did anything wrong, please let me know.

Regards
/Anders

0 Shankari G over 8 years ago in reply to Anders Klint

TI__Mastermind 43955 points

Hi Anders Klint,

I apologize that the Image processing demo doesnot work on the latest version of MCSDK 3.01.3.6. It works only on mcsdk_linux_3_00_03_15.I confirmed this with the internal team and got a reply telling that it will be fixed in the next release.
Only the IPC demo works on both the versions.

Your observations were right.

After few investigations, it seems to me that the whole IPC package ( version: ipc_3_35_01_07) can only be successfully built using the below command ( you already mentioned about it in your first post. ). I am able to built only as a whole package.

C:\ti\ipc_3_35_01_07_copy_14082015>gmake -f ipc-bios.mak

There is no clear procedure for extracting the messageq_single alone and built it in CCS. Because, as per the user guide ( page no: 68) , attached, it says to use the DOS command shell or the cygwin.

The instructions in this section can be used to build IPC on Windows or Linux. If you are using a Windows
machine, you can use the regular DOS command shell provided with Windows. However, you may want
to install a Unix-like shell, such as Cygwin.

According to me, the approach of building the messageq_single alone to be looked into detail with the same command line set up and not the CCS ( For that matter, atleast I am not sure about its list of dependencies needed for the messageq_single during runtime). Few customers seems to be using CCS environment for building this as a separate component but not sure whether they succeed in there attempts ( Seen posts in forums only)

----

0 Anders Klint over 8 years ago in reply to Shankari G

Intellectual 620 points

Hi Shankari,

Thanks for looking into this and getting back with info.

Perhaps I haven't been clear enough - I intended to use messageq_single as a minimal example
to get IPC (preferrably using MessageQ) working and then continue building on that.

What I am aiming for is to get IPC working (Linux-DSP) on our target hardware which will arrive shortly.
Building messageq_single is a means to an end, not a goal in itself. It was the smallest, specific example
I could come up with.

My view is that TI recommends application development to be done in CCS. If this for some reason
is not possible I can live with a command-line / make based solution, but I believe that I would need
some help to set that up. However I get the impression that it SHALL be possible to do application
development on Keystone2 using CCS, even if it involves IPC...

So what I (and others, apparently) need is a minimal example, which is possible to build - and run! -
in CCS - performing reliable communication between Linux and the DSPs. If you have something other
(simpler) than messageq_single that's fine - as long as it works.

I still hope and believe that this is not impossible.

Regards
/Anders

0 Shankari G over 8 years ago in reply to Anders Klint

TI__Mastermind 43955 points

Hi Anders,

Shankari said:
I apologize that the Image processing demo doesnot work on the latest version of MCSDK 3.01.3.6. It works only on mcsdk_linux_3_00_03_15.I confirmed this with the internal team and got a reply telling that it will be fixed in the next release. Only the IPC demo works on both the versions.

In MCSDK 3.01.3.6, the image processing demo started working after setting the mem_reserve=1536M in the u-boot prompt.

Please refer to

Anders said:
So what I (and others, apparently) need is a minimal example, which is possible to build - and run! -
in CCS - performing reliable communication between Linux and the DSPs. If you have something other
(simpler) than messageq_single that's fine - as long as it works.

I have taken this as a customer feedback and strongly recommended to have a simple IPC example between ARM-DSP core to the factory team.

Meanwhile please give a try on the MCSDK 3.01.3.6 with mem_reserve settings as said earlier. Will help you out for making it work.

-----

Processors

Processors forum

Configuration / build of messageq_single