Bootargs for EVMK2H using IPC

Anders Klint

Other Parts Discussed in Thread: OMAPL138

Hi,

In the IPC install guide for Linux it is stated that the Linux kernel needs an extra argument specifying the location
of remote processors for IPC to work correctly:

Kernel Boot-up Parameters

IPC requires an argument to be passed to the Linux kernel during boot up to properly run the tests. The remote processor(s) (rproc) memory location needs to be set.

For example,

bootargs console=ttyS2,115200n8 root=/dev/nfs nfsroot=HOST:nfs_root,nolock rw ip=dhcp rproc_mem=16M@0xC3000000

This is just an example, bootargs may vary depending on available setup
Depending on the memory map used in the final system configuration, the memory to be reserved for rproc usage may differ.

As seen above this is "just an example".

Specifically for trying to get IPC 3.36.1.11 working on a EVMK2H board rev 3.0, do I need to set rproc_mem, and if so what would it be set to?

Regards
/Anders

over 10 years ago

0 Titusrathinaraj Stalin over 10 years ago

TI__Guru** 116100 points

Hi,
Which MCSDK version are you using ?
I've used IPC without using any rproc_mem defining.
Where did you see that rproc_mem defining is mandatory for IPC ?

I have tested the IPC in mcsdk_linux_3_00_03_15.

0 Anders Klint over 10 years ago in reply to Titusrathinaraj Stalin

Intellectual 620 points

Hi Titus,

I use MCSDK 3_01_03_06

It's stated in the IPC install Guide for Linux: processors.wiki.ti.com/.../IPC_Install_Guide_Linux
(search for rproc_mem)

Regards
/Anders

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

TI__Mastermind 43955 points

Hi Anders,

For EVMK2H, rproc_mem is not required.
In this, "rproc_mem=16M@0xC3000000" the address of DDR, 0xC30000000 seems to be used for OMAPL138 and not for K2HEVM.
you can use without it too.

Please use this version mcsdk_linux_3_00_03_15 and try once.

----

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

Intellectual 620 points

Hi Shankari,

Thanks for the clarification on the question of rproc_mem, I will not add it.

But I would like to know why you keep referring me to mcsdk 3.0.3.15, which if I read it correctly
was released in late 2013 - close to two years ago. IIRC the release notes in quite a few releases
since that one suggests that a lot of problems have been corrected since then.

Why am I not asked to use the current release, but instead one 21 months old?

Regards
/Anders

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

TI__Mastermind 43955 points

Hi Anders,

This version, MCSDK 3_01_03_06 should also work.

Since we have tested the version, mcsdk_linux_3_00_03_15 without "rproc", I just asked you to try for proof of concept and not recommending for using it.

-----

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

Intellectual 620 points

Hi,

OK, proof of concept thought noted.

Also noted that MCSDK 3_01_03_06 _SHOULD_ work - but have you tried it?
I still find it a little weird that I keep getting the impression that support staff is not using current versions of
the products that are supported.

Regards,
/Anders

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

TI__Mastermind 43955 points

Anders,

Usually the support team will shuttle between different versions with different examples.

Personally, I have run other examples on the later version, 3.1.3.6 but not the IPC. Will try the IPC on 3.1.3.6 and get back.

--

Processors

Processors forum

Bootargs for EVMK2H using IPC

Kernel Boot-up Parameters