Compiler/TDA2SX: Linux Boot Time Optimizations on DRA7xx Devices

Thanks RamPrasad, I am waiting for the engineer Venkateswara Rao Mandela'help.Now I used the file system based on PSDKLA3.0x you provided by http://software-dl.ti.com/processor-sdk-vision/esd/TDAx/vision-sdk/03_07_00_00/index_FDS.html

Hi RamPrasad,

       You mean I need to build the uboot, kernel based on PSDKLA3.02, not the vsdk3.06?

Hi RamPrasad,

       But I need to run the usecase base on vsdk3.06, could the usecase be compatible with PSDKLA3.02?You mean I can use the file system,MLO,uboot.img,uImage and dtb which builded by the PSDKLA3.02?

so the usecase eg. the 4lvds cameras to the display can't run base on the PSDKLA3.02?

so we can only use the early boot to run the usecase eg. the 4lvds cameras to the display as quickly as possible base on vsdk3.06?We need to display the panoramic image.

>>so we can only use the early boot to run the usecase eg. the 4lvds cameras to the display as quickly as possible base on vsdk3.06?

Yes, currently there is only one usecase to demonstrate early usecase with visionSDK.

>>We need to display the panoramic image.

What type of images are these? Are these jpeg?

RamPrasad

Hi Jason,

Can you give more details on panaromic mosaic videos? Are these going to be same everytime?

If yes, there is a possibility of using "NullSrc + Decode + Display" type of application during early boot. 

Some customer have implemetned this as early decode usecase where they show their company logo. This video is a motion jpeg.

RamPrasad

no, they weren't going to be same everytime,they are four cameras which are responsible for four directions(car front car back car left car right) separately, and then we use the DSP core to stitch these live images into a 2D video, which finaly displayed on the screen.(eg.https://www.iqiyi.com/w_19rsuw5km1.html#curid=6197848309_1e5c07c6f2c9dc9b4b44fd8cf5851915,the right video)

>>do you have this usecase running fine in normal boot case?

no, we only have this usecase running on the DSP core now, and the 3D video stitching on the GPU, all of them are done after the app started.How can we run this usecase in normal boot case(early boot)?Do you have detail steps to do it?

>>there is a possibility of using "NullSrc + Decode + Display" type of application during early boot. 

>>Some customer have implemetned this as early decode usecase where they show their company logo. This video is a motion jpeg.

Could you give me the tutorial about using "NullSrc + Decode + Display" type of application during early boot?I try to do this.

>>do you have this usecase running fine in normal boot case?

I misunderstood what you meant yesterday, yes we've already this usecase running fine in normal boot case, now we need to do it in early boot mode.What can we do exactly now?Or you can give me some cases I can imitate.

Hi RamPrasad,

       I'd like to introduce our usecase to you.As follow shown,Q1 is the part of usecase which can realize the 2D real-time panoramic mosaic video, under normal boot, the video is processed by the sgx3Dsrv link and then transfer to Q0, finally displayed by  Display_M4 link.

      Now, we want to Q1 directly transfer to Q0, when it works in the early boot mode at the beginning, so the 2D real-time panoramic mosaic video can be displayed as quickly as possible.Under this situation, we need to depart  the 2D real-time panoramic mosaic video(be realized by some links) from the usecase, when normal usecase startup later, we need to let the Q1 link to the sgx3Dsrv, and then the sgx3Dsrv link to the IPCOUT_A15_0_IPU1_0_0.

      Could it be possible?

Hi RamPrasad,

       Now I know to do the earlyboot for the 2D real-time panoramic mosaic video ,we need to follow processors.wiki.ti.com/.../Early_Boot_and_Late_Attach_in_Linux, and the chapter 3.4Build Linux Vision SDK for fast boot (Early boot and late attach of remotecores), am I right? Could you show me more cases for early boot ?

Regards

Jason

I use 4ch LVDS capture for 2D mosaic video display right now.But how could I do the early boot, the 2D mosaic video need the i2c2 to init the Max96706(input) and the MAX9275(output), and some PLL configure, what exactly I need to do.Could you show me more details?

Best Regards

Jason

I want to use the dts file to drive the Max96706(4 inputs for cameras) and MAX9275(one output on display),but how to do?

i2c_p3_exp: &i2c2 {
status = "okay";
clock-frequency = <400000>;

pcf_hdmi: gpio@26 {
status = "disabled";
compatible = "nxp,pcf8575";
reg = <0x26>;
gpio-controller;
#gpio-cells = <2>;
vin6_brdmux: p1 {
/* vin6_sel_s0: high: VIN6, low: audio */
gpio-hog;
gpios = <1 GPIO_ACTIVE_HIGH>;
output-low;
line-name = "vin6_sel_s0";
};
};

ov10633@37 {
compatible = "ovti,ov10633";
reg = <0x37>;

mux-gpios = <&pcf_hdmi 3 GPIO_ACTIVE_LOW>; /* CAM_FPD_MUX_S0 */
port {
onboardLI: endpoint {
remote-endpoint = <&vin1a>;
hsync-active = <1>;
vsync-active = <1>;
pclk-sample = <0>;
};
};
};

disp_ser: serializer@1b {
compatible = "ti,ds90uh925q";
reg = <0x1b>;

#address-cells = <1>;
#size-cells = <0>;
status = "disabled";
};
};

>>There is only one usecase which is 4ch LVDS capture TI has implemented to demonstrate Early boot Late attach functionality in visionSDK.

Could you show me the details about the 4ch LVDS capture usecase  be  implemented to demonstrate Early boot Late attach functionality in visionSDK?I would like to imitate it to do for my usecase.

you mean this chapter?

About early boot, I thought it's running before app started. For example, we want to display the  4ch LVDS capture quickly, we need to load the dsp1 dsp2 ipu2 firmware during the uboot. we need to init the four inputs and one output peripherals during the uboot, so when the kernel started, it had displayed the 4ch LVDS capture on the screen.

But I see the usecase you mentioned, is running after the app starts.

Hi Jason,

This usecase is completely run on RTOS as soon as firmwares are loaded to IPU and DSP by MLO.

Thanks

RamPrasad

Hi RamPrasad,

       Since the firmwares are loaded to IPU and DSP by MLO, before kernel start, the RTOS has begin to running, even we do not start kernel?am I right?

Hi RamPrasad,

       I would like share you with the log about the early boot I do.The MLO first loaded the dra7-dsp1-fw.lzop, dra7-dsp2-fw.lzop, and dra7-ipu2-fw.lzop successfully, the these firmwares started to running before kernel start.Then I see the peripheral Max96706 has been init by the IPU2, it has the output data, it seems work normal, but when the kernel started, it has no output data. was it reset by the kernel?Could you help me to analysis the log/cfs-file/__key/communityserver-discussions-components-files/791/test_2D00_earlyboot.txt?

      It seems the kernel wanted the load the dra7-dsp1-fw.xe66,dra7-dsp2-fw.xe66,and dra7-ipu2-fw.xem4, but it failed.

 Best Regards

Jason