• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 100 subscribers
  • Views 1188 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

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

Memory mapping for DM385 512M

German Baranov
Intellectual 660 points
Other Parts Discussed in Thread: DM385

Hi!

In spite of a number of links devoted to memory configuration for ti81xx systems and nice "EZSDK memory map" guide,

I can't configure memory to load vpss.ko driver and asking fo help/

My case is DM385 (ti813x) processor with 512MB of memory.

I'm using M3 firmware from 1GB system (ipnc_rdk_fw_m3video.xem3, ipnc_rdk_fw_m3vpss.xem3) and here is the first question:

I've seen different .xem3 files for 512M and 1GB in case of ti814x, but just one for ti813x. Is it OK to use the same M3 firmware for ti813x systems with 512MB

and 1 GB of memory?

notifyk.vpssm3_sva for this firmware is set to 0xBFD00000 and attempts to change it cause problems with firmware load.

So I have to provide configuration of DMM_LISA_MAP_ registers, which maps 0xB0000000-0xC0000000 segment to physical device

(and not forget about mapping of 0x80000000-0x90000000 which is used for kernel and cmemk)

I've tried couple of variants but in all cases, after successful m3 firmware load I'm getting problem after "insmod vpss.ko", which looks like:

VPSS_FVID2: create handle is NULL
VPSS_SYSTEM: failed to create handle
VPSS_CORE : failed to init system
vpss: probe of vpss failed with error -22
VPSS_CORE : failed to register ti81xx-vpss driver

Can you please give me an advice?

Tnanks, German Baranov

  • 0
    TI__Guru* 80190 points
    Hello,

    If you are using EZSDK please check these threads regarding memory map:
    processors.wiki.ti.com/.../EZSDK_Memory_Map
    e2e.ti.com/.../305051

    Regarding the error check here:
    e2e.ti.com/.../1321165

    You could recheck your bootargs also.

    BR
    Margarita
  • 0 in reply to Margarita Gashova
    Intellectual 660 points
    Hi,
    Thanks for answering,

    No, I'm not using EZSDK, I work with custom DM385 board.
    Nevertheless, I believe, the main idea should be very similar.
    (The evident difference is just one EMIF0 and no interleaving)

    After your post I'm in doubt - if I'm asking correctly...
    Actually what I have is a problem with loading vpss.ko
    (thanks for e2e.ti.com/.../1321165 but I still have an error)
    Decision that this is because of incorrect memory mapping is purely mine and can be wrong
    Should I continue digging into memory map?

    Regards,
    German Baranov
  • 0 in reply to German Baranov
    Intellectual 660 points

    Actually, 

    e2e.ti.com/.../1321165

    nicely answers to the question "where to look for vpss.ko?",

    but in my case, vpss.ko location is known.

  • 0 in reply to German Baranov
    TI__Guru* 80190 points
    Hello,

    Could you check what are yours bootargs?

    BR
    Margarita
  • 0 in reply to Margarita Gashova
    Intellectual 660 points
    Hello?

    boot script is:
    setenv bootargs 'console=ttyO0,115200n8 root=/dev/mmcblk0p2 mem=80M rootwait vram=8M notifyk.vpssm3_sva=0xBFD00000 ip=off eth=$(ethaddr) cmemk.phys_start=0x85000000 cmemk.phys_end=0x89000000 cmemk.allowOverlap=1 earlyprintk'
    setenv bootcmd 'mmc init; fatload mmc 0 0x81000000 uImage; bootm 0x81000000'
    boot


    Content of LISA registers is:
    #define DDR3_DMM_LISA_MAP__0 0x0
    #define DDR3_DMM_LISA_MAP__1 0x0
    #define DDR3_DMM_LISA_MAP__2 0x80500100
    #define DDR3_DMM_LISA_MAP__3 0xA0500100

    Yours truly,
    German Baranov
  • 0 in reply to German Baranov
    Intellectual 660 points
    Hi,
    Just to describe the situation shortly:
    Firmware has been loaded to VPSS-M3 and loader returns status 0, so I think loading was OK.
    In attempt to load vpss.ko, error "FVID2 NULL handle is returned"
    Since NULL is not default handle value, I presume vpss-m3 device sends this message because it dislikes something.
    Is there a way to find out what's wrong, without going into m3 firmware source and inserting debug marks?
    How hard is to get an access to the source of xem3 files? ( From authorized distributor I got message:
    "Ti doesn't provide any support for dm385", (and just for info : we have NDA signed ))

    Regards
  • 0 in reply to German Baranov
    TI__Guru* 80190 points
    Hello,

    I would recommend you to search in the e2e for similar issue.

    BR
    Margarita
  • 0 in reply to Margarita Gashova
    Intellectual 660 points
    Hello!
    Let me do a little bit more talking on the subject.
    Now I'm capable to load vpss.ko module and capable of seeing some problems.
    1. Do not forget to turn on power and clocks for ISS in PRCModule. Some naive people (like me)
    think that "power on" can be done after loading driver - no, power first.
    2. Thing, which is still unclear to me. VPSS M3 controller requires command
    (namely " capital T") to be sent, for vpss driver loading. (TI provides utility
    remote_debug_client.out to send the command)
    Where can I read about those commands and m3vpss interaction?
    since "VPSS video driver user guide" doesn't pay a lot of attention to
    the issue (if pays at all).

    Best regards,
    German