Quantcast
Channel: Processors
Viewing all 125265 articles
Browse latest View live

Forum Post: RE: Linux/AM3352: GPIO resets on kernel boot

$
0
0
Please read e2e.ti.com/.../684056

Forum Post: RE: PROCESSOR-SDK-TDA2PX: An exception occurs when MCAN calls mcan cls module provided by Ti.

$
0
0
Hi Bikash, Peripheral memories need not be mapped in a different manner. MMU mapping is present for MCAN MMRs in A15 cfg file. I will check with MCAN expert next week once he is back from vacation. Regards, Rishabh

Forum Post: RE: Linux/LINUXSDK-OMAPL138: GPIO wakeup

$
0
0
Hi Shyam Thanks. I will still go ahead and mark this thread closed, and will follow up further on the other thread that you going with Sekhar Nori Regards Mukul

Forum Post: TMS320C6748: Multiple Interrupt Handling

$
0
0
Part Number: TMS320C6748 Good Afternoon, I have a question regarding the handling of maskable interrupts with the TMS320C6748 LCDK. I have reviewed the TMS320C674x DSP CPU and Instruction Set document on interrupts but haven't received a clear picture of what is happening. If I utilize three different interrupts what happens in the event I receive one interrupt and then during that interrupt, a second interrupt is triggered? I understand that there is no nested interrupts based on priority unless written into the software. Will the interrupt routine for the second interrupt follow once the interrupt for interrupt 1 has been completed or is that second interrupt not even flagged and therefor it is ignored? My understanding from the documentation that the interrupts are disabled during interrupts routines and will never be received. Is this true? Therefore you cannot run multiple interrupts at the same time as you can miss that moment when you need to answer an interrupt from an interrupt. In utilizing the UART interrupt to receive information from a serial terminal, sometimes the interrupt does not appear to be flagged when sending data from the serial terminal which results in missed information. I have other interrupts running while I await this UART interrupt. So maybe I need to switch to a polling routine. Thanks, Tyler

Forum Post: RTOS/TDA2PXEVM: High display latency in iss_capture_isp_simcop_display usecase

$
0
0
Part Number: TDA2PXEVM Tool/software: TI-RTOS Hello, We are using PROCESSOR-SDK-VISION V3.06.00 for TDA2PX-EVM on TI-RTOS. Fusion Application Board is used for connection with FPD-Link III camera over coax cable. We had run iss_capture_isp_simcop_display usecase (via selecting "1CH ISS capture + ISS ISP + ISS LDC+VTNF + Display" in menu) and found out that the final latency from source to display is about 90ms (9049106 us). This high latency is quite strange, since there are no visible reasons for that in according to printed performance statistics: [IPU1-0] Chains Run-time Menu [IPU1-0] ==================== [IPU1-0] [IPU1-0] 0: Stop Chain [IPU1-0] [IPU1-0] 1: Toggle VTNF ON/OFF [IPU1-0] 2: Toggle LDC ON/OFF [IPU1-0] 3: Save Captured Frame [IPU1-0] 4: Save SIMCOP Output Frame [IPU1-0] 5: Save ISP Output Frame [IPU1-0] [IPU1-0] p: Print Performance Statistics [IPU1-0] [IPU1-0] Enter Choice: [IPU1-0] [IPU1-0] 248.242939 s: [IPU1-0] 248.243244 s: i2cMdSubmitChan: i2c4 transfer to slave address 0x40 failed [IPU1-0] 248.243366 s: src/bsp_deviceI2c.c @ Line 671: [IPU1-0] 248.243457 s: I2C4: DEV 0x40: ERROR !!! [IPU1-0] 248.243549 s: src/bsp_deviceI2c.c @ Line 693: [IPU1-0] 248.243640 s: I2C4: Error timeout 255 ms!!! [IPU1-0] 747.194198 s: [IPU1-0] 747.194290 s: CPU [IPU1-0 ] Statistics, [IPU1-0] 747.194351 s: ************************* [IPU1-0] 747.194412 s: [IPU1-0] 747.194442 s: LOAD: CPU: 18.6% HWI: 3.0%, SWI:0.8%, Low Power: 77.5% [IPU1-0] 747.194595 s: [IPU1-0] 747.194717 s: LOAD: TSK: DISPLAY0 : 0.5% [IPU1-0] 747.194808 s: LOAD: TSK: DISPLAY1 : 0.4% [IPU1-0] 747.194900 s: LOAD: TSK: ISSCAPTURE : 0.2% [IPU1-0] 747.194991 s: LOAD: TSK: ISSM2MISP : 2.1% [IPU1-0] 747.195083 s: LOAD: TSK: ISS-Resizer0 : 1.4% [IPU1-0] 747.195205 s: LOAD: TSK: ISSM2MSIMCOP : 0.8% [IPU1-0] 747.195327 s: LOAD: TSK: ALGORITHM1 : 4.5% [IPU1-0] 747.195418 s: LOAD: TSK: GrpxSrc0 : 0.2% [IPU1-0] 747.195510 s: LOAD: TSK: STAT_COLL : 3.1% [IPU1-0] 747.195601 s: LOAD: TSK: MISC : 1.6% [IPU1-0] 747.195693 s: [IPU1-0] 747.195723 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1023 [IPU1-0] 747.195815 s: [IPU1-0] 747.195845 s: SYSTEM: Sempahores Objects, 35 of 1050 free [IPU1-0] 747.195937 s: SYSTEM: Task Objects , 5 of 100 free [IPU1-0] 747.196028 s: SYSTEM: Clock Objects , 97 of 100 free [IPU1-0] 747.196120 s: SYSTEM: Hwi Objects , 87 of 100 free [IPU1-0] 747.196211 s: [IPU1-0] 747.196272 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 243896 B (238 KB) [IPU1-0] 747.196425 s: SYSTEM: Heap = SR_OCMC @ 0x00000000, Total size = 0 B (0 KB), Free size = 0 B (0 KB) [IPU1-0] 747.196577 s: SYSTEM: Heap = SR_DDR_CACHED @ 0x88503000, Total size = 368037888 B (350 MB), Free size = 314142208 B (299 MB) [IPU1-0] 747.196730 s: SYSTEM: Heap = SR_DDR_NON_CACHED @ 0xbfc00000, Total size = 127872 B (0 MB), Free size = 106368 B (0 MB) [IPU1-0] 747.196913 s: [IPU1-0] 747.196943 s: [IPU1-0] 747.196974 s: CPU [IPU1-1 ] Statistics, [IPU1-0] 747.197035 s: ************************* [IPU1-0] 747.197096 s: [IPU1-0] 747.197157 s: LOAD: CPU: 1.4% HWI: 0.9%, SWI:0.4%, Low Power: 77.6% [IPU1-0] 747.197309 s: [IPU1-0] 747.197401 s: LOAD: TSK: MISC : 0.1% [IPU1-0] 747.197492 s: [IPU1-0] 747.197523 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1023 [IPU1-0] 747.197614 s: [IPU1-0] 747.197675 s: SYSTEM: Sempahores Objects, 433 of 1050 free [IPU1-0] 747.197736 s: SYSTEM: Task Objects , 37 of 100 free [IPU1-0] 747.197828 s: SYSTEM: Clock Objects , 99 of 100 free [IPU1-0] 747.197919 s: SYSTEM: Hwi Objects , 99 of 100 free [IPU1-0] 747.198011 s: [IPU1-0] 747.198041 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 655360 B (640 KB), Free size = 645240 B (630 KB) [IPU1-0] 747.198377 s: [IPU1-0] 747.198438 s: [IPU1-0] 747.198468 s: CPU [HOST ] Statistics, [IPU1-0] 747.198529 s: ************************* [IPU1-0] 747.198590 s: [IPU1-0] 747.198621 s: LOAD: CPU: 1.3% HWI: 0.0%, SWI:0.0%, Low Power: 97.9% [IPU1-0] 747.198773 s: [IPU1-0] 747.198865 s: LOAD: TSK: MISC : 1.3% [IPU1-0] 747.198956 s: [IPU1-0] 747.198987 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1023 [IPU1-0] 747.199078 s: [IPU1-0] 747.199139 s: SYSTEM: Sempahores Objects, 434 of 1050 free [IPU1-0] 747.199261 s: SYSTEM: Task Objects , 37 of 100 free [IPU1-0] 747.199353 s: SYSTEM: Clock Objects , 99 of 100 free [IPU1-0] 747.199444 s: SYSTEM: Hwi Objects , 99 of 100 free [IPU1-0] 747.199627 s: [IPU1-0] 747.199658 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 6291456 B (6144 KB), Free size = 6246760 B (6100 KB) [IPU1-0] 747.199810 s: [IPU1-0] 747.199871 s: [IPU1-0] 747.199902 s: CPU [DSP1 ] Statistics, [IPU1-0] 747.199963 s: ************************* [IPU1-0] 747.200024 s: [IPU1-0] 747.200054 s: LOAD: CPU: 0.2% HWI: 0.1%, SWI:0.0%, Low Power: 99.3% [IPU1-0] 747.200237 s: [IPU1-0] 747.200298 s: LOAD: TSK: MISC : 0.1% [IPU1-0] 747.200390 s: [IPU1-0] 747.200420 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1023 [IPU1-0] 747.200512 s: [IPU1-0] 747.200542 s: SYSTEM: Sempahores Objects, 447 of 1050 free [IPU1-0] 747.200634 s: SYSTEM: Task Objects , 90 of 100 free [IPU1-0] 747.200725 s: SYSTEM: Clock Objects , 99 of 100 free [IPU1-0] 747.200817 s: SYSTEM: Hwi Objects , 100 of 100 free [IPU1-0] 747.200878 s: [IPU1-0] 747.200939 s: SYSTEM: Heap = LOCAL_L2 @ 0x00800000, Total size = 227264 B (221 KB), Free size = 227264 B (221 KB) [IPU1-0] 747.201091 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 524288 B (512 KB), Free size = 516376 B (504 KB) [IPU1-0] 747.201274 s: [IPU1-0] 747.201305 s: [IPU1-0] 747.201366 s: CPU [DSP2 ] Statistics, [IPU1-0] 747.201427 s: ************************* [IPU1-0] 747.201457 s: [IPU1-0] 747.201518 s: LOAD: CPU: 0.2% HWI: 0.1%, SWI:0.0%, Low Power: 99.3% [IPU1-0] 747.201671 s: [IPU1-0] 747.201701 s: LOAD: TSK: MISC : 0.1% [IPU1-0] 747.201793 s: [IPU1-0] 747.201823 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1023 [IPU1-0] 747.201915 s: [IPU1-0] 747.201945 s: SYSTEM: Sempahores Objects, 447 of 1050 free [IPU1-0] 747.202037 s: SYSTEM: Task Objects , 90 of 100 free [IPU1-0] 747.202128 s: SYSTEM: Clock Objects , 99 of 100 free [IPU1-0] 747.202250 s: SYSTEM: Hwi Objects , 100 of 100 free [IPU1-0] 747.202342 s: [IPU1-0] 747.202372 s: SYSTEM: Heap = LOCAL_L2 @ 0x00800000, Total size = 227264 B (221 KB), Free size = 227264 B (221 KB) [IPU1-0] 747.202525 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 524288 B (512 KB), Free size = 516376 B (504 KB) [IPU1-0] 747.202677 s: [IPU1-0] 747.202738 s: [IPU1-0] 747.202769 s: CPU [EVE1 ] Statistics, [IPU1-0] 747.202830 s: ************************* [IPU1-0] 747.202891 s: [IPU1-0] 747.202921 s: LOAD: CPU: 0.5% HWI: 0.2%, SWI:0.1%, Low Power: 94.1% [IPU1-0] 747.203074 s: [IPU1-0] 747.203135 s: LOAD: TSK: MISC : 0.2% [IPU1-0] 747.203379 s: [IPU1-0] 747.203440 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1023 [IPU1-0] 747.203531 s: [IPU1-0] 747.203562 s: SYSTEM: Sempahores Objects, 448 of 1050 free [IPU1-0] 747.203653 s: SYSTEM: Task Objects , 91 of 100 free [IPU1-0] 747.203745 s: SYSTEM: Clock Objects , 99 of 100 free [IPU1-0] 747.203837 s: SYSTEM: Hwi Objects , 99 of 100 free [IPU1-0] 747.203898 s: [IPU1-0] 747.203959 s: SYSTEM: Heap = LOCAL_L2 @ 0x40020000, Total size = 22528 B (22 KB), Free size = 22528 B (22 KB) [IPU1-0] 747.204111 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 254208 B (248 KB) [IPU1-0] 747.204294 s: [IPU1-0] 747.204355 s: [IPU1-0] 747.204386 s: CPU [EVE2 ] Statistics, [IPU1-0] 747.204447 s: ************************* [IPU1-0] 747.204508 s: [IPU1-0] 747.204569 s: LOAD: CPU: 0.5% HWI: 0.2%, SWI:0.1%, Low Power: 94.1% [IPU1-0] 747.204691 s: [IPU1-0] 747.204752 s: LOAD: TSK: MISC : 0.2% [IPU1-0] 747.204843 s: [IPU1-0] 747.204874 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1023 [IPU1-0] 747.204965 s: [IPU1-0] 747.204996 s: SYSTEM: Sempahores Objects, 448 of 1050 free [IPU1-0] 747.205087 s: SYSTEM: Task Objects , 91 of 100 free [IPU1-0] 747.205179 s: SYSTEM: Clock Objects , 99 of 100 free [IPU1-0] 747.205270 s: SYSTEM: Hwi Objects , 99 of 100 free [IPU1-0] 747.205362 s: [IPU1-0] 747.205423 s: SYSTEM: Heap = LOCAL_L2 @ 0x40020000, Total size = 22528 B (22 KB), Free size = 22528 B (22 KB) [IPU1-0] 747.205575 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 254208 B (248 KB) [IPU1-0] 747.205728 s: [IPU1-0] 747.205758 s: [IPU1-0] 747.205819 s: CPU [IPU2 ] Statistics, [IPU1-0] 747.205880 s: ************************* [IPU1-0] 747.205911 s: [IPU1-0] 747.205972 s: LOAD: CPU: 1.1% HWI: 0.6%, SWI:0.4%, Low Power: 96.2% [IPU1-0] 747.206124 s: [IPU1-0] 747.206246 s: LOAD: TSK: MISC : 0.1% [IPU1-0] 747.206307 s: [IPU1-0] 747.206368 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1023 [IPU1-0] 747.206460 s: [IPU1-0] 747.206490 s: SYSTEM: Sempahores Objects, 440 of 1050 free [IPU1-0] 747.206582 s: SYSTEM: Task Objects , 38 of 100 free [IPU1-0] 747.206673 s: SYSTEM: Clock Objects , 99 of 100 free [IPU1-0] 747.206734 s: SYSTEM: Hwi Objects , 99 of 100 free [IPU1-0] 747.206826 s: [IPU1-0] 747.206887 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 252016 B (246 KB) [IPU1-0] 747.207039 s: [IPU1-0] 747.207375 s: [IPU1-0] 747.207436 s: UTILS_PRCM_STATS: Current Temperature, [IPU1-0] 747.207497 s: [IPU1-0] 747.207558 s: Voltage Rail || Curr Temp Min - Max [IPU1-0] 747.207619 s: --------------------------------------------------------- [IPU1-0] 747.207710 s: PMHAL_PRCM_VD_MPU || [48.400 , 48.800] [IPU1-0] 747.207832 s: PMHAL_PRCM_VD_CORE || [48.400 , 48.800] [IPU1-0] 747.207924 s: PMHAL_PRCM_VD_IVAHD || [48.800 , 49.200] [IPU1-0] 747.208046 s: PMHAL_PRCM_VD_DSPEVE || [46.400 , 46.800] [IPU1-0] 747.208320 s: PMHAL_PRCM_VD_GPU || [47.600 , 48. 0] [IPU1-0] 747.208442 s: [IPU1-0] 747.208473 s: ============================================================================ [IPU1-0] 747.208595 s: Name | Bus (mV) | Res (mOhm) | Shunt (uV) | Current (mA) | Power (mW) [IPU1-0] 747.208686 s: ---------------------------------------------------------------------------- [IPU1-0] 747.210120 s: UTILS_PRCM_STATS: Reading the regulator data failed [IPU1-0] 747.210242 s: UTILS_PRCM_STATS: PM INA226 Power Read Failed !! [IPU1-0] 747.210455 s: [IPU1-0] 747.210516 s: Statistics Collector, [IPU1-0] 747.210577 s: [IPU1-0] 747.210608 s: STATISTIC Avg Data Peak Data [IPU1-0] 747.210669 s: COLLECTOR MB/s MB/s [IPU1-0] 747.210760 s: -------------------------------------------------- [IPU1-0] 747.210852 s: SCI_EMIF1 RD+WR | 1140.143261 2234.290283 [IPU1-0] 747.210943 s: SCI_EMIF2 RD+WR | 0.000000 0.000000 [IPU1-0] 747.211065 s: SCI_EMIF1 RD ONLY | 799.345668 1367.208366 [IPU1-0] 747.211187 s: SCI_EMIF1 WR ONLY | 341.204070 873.704918 [IPU1-0] 747.211309 s: SCI_EMIF2 RD ONLY | 0.000000 0.000000 [IPU1-0] 747.211401 s: SCI_EMIF2 WR ONLY | 0.000000 0.000000 [IPU1-0] 747.211523 s: SCI_MA_MPU_P1 | 0.002863 0.068002 [IPU1-0] 747.211614 s: SCI_MA_MPU_P2 | 0.000000 0.000000 [IPU1-0] 747.211736 s: SCI_DSS | 455.602052 517.870850 [IPU1-0] 747.211828 s: SCI_IPU1 | 14.905725 47.159536 [IPU1-0] 747.211919 s: SCI_VIP1_P1 | 0.000000 0.000000 [IPU1-0] 747.212743 s: SCI_VIP1_P2 | 0.000000 0.000000 [IPU1-0] 747.212895 s: SCI_VPE_P1 | 0.000000 0.000000 [IPU1-0] 747.212987 s: SCI_VPE_P2 | 0.000000 0.000000 [IPU1-0] 747.213109 s: SCI_DSP1_MDMA | 0.833394 1.747736 [IPU1-0] 747.213475 s: SCI_DSP1_EDMA | 0.000000 0.000000 [IPU1-0] 747.213597 s: SCI_DSP2_MDMA | 0.833426 1.709112 [IPU1-0] 747.213688 s: SCI_DSP2_EDMA | 0.000000 0.000000 [IPU1-0] 747.213871 s: SCI_EVE1_TC0 | 2.344468 6.061349 [IPU1-0] 747.213993 s: SCI_EVE1_TC1 | 0.000000 0.000000 [IPU1-0] 747.214115 s: SCI_EVE2_TC0 | 2.345283 6.756497 [IPU1-0] 747.214268 s: SCI_EVE2_TC1 | 0.000000 0.000000 [IPU1-0] 747.214359 s: SCI_EDMA_TC0_RD | 0.000000 0.000000 [IPU1-0] 747.214481 s: SCI_EDMA_TC0_WR | 0.000000 0.000000 [IPU1-0] 747.214603 s: SCI_EDMA_TC1_RD | 0.000000 0.000000 [IPU1-0] 747.214695 s: SCI_EDMA_TC1_WR | 0.000000 0.000000 [IPU1-0] 747.214817 s: SCI_VIP2_P1 | 0.000000 0.000000 [IPU1-0] 747.214908 s: SCI_VIP2_P2 | 0.000000 0.000000 [IPU1-0] 747.215030 s: SCI_IVA | 0.000000 0.000000 [IPU1-0] 747.215122 s: SCI_GPU_P1 | 0.000000 0.000000 [IPU1-0] 747.215244 s: SCI_GPU_P2 | 0.000000 0.000000 [IPU1-0] 747.215366 s: SCI_GMAC_SW | 0.000000 0.000000 [IPU1-0] 747.215457 s: SCI_OCMC_RAM1 | 0.000000 0.000000 [IPU1-0] 747.215579 s: SCI_OCMC_RAM2 | 0.000000 0.000000 [IPU1-0] 747.215671 s: SCI_OCMC_RAM3 | 0.000000 0.000000 [IPU1-0] 747.215793 s: SCI_ISS_RT | 0.000000 0.000000 [IPU1-0] 747.215884 s: SCI_ISS_NRT1 | 248.724672 1517.357856 [IPU1-0] 747.216006 s: SCI_ISS_NRT2 | 280.301268 1042.011667 [IPU1-0] 747.216433 s: SCI_CAL | 124.501832 130.780370 [IPU1-0] 747.316415 s: [IPU1-0] 747.316507 s: [IPU1-0] 747.316598 s: [IPU1-0] 747.316659 s: ### CPU [IPU1-0], LinkID [ 83], [IPU1-0] 747.316751 s: [IPU1-0] 747.318001 s: [ ISSCAPTURE ] Link Statistics, [IPU1-0] 747.318123 s: ****************************** [IPU1-0] 747.318855 s: [IPU1-0] 747.318916 s: Elapsed time = 568074 msec [IPU1-0] 747.318977 s: [IPU1-0] 747.319038 s: Get Full Buf Cb = 30.3 fps [IPU1-0] 747.319099 s: Put Empty Buf Cb = 30.2 fps [IPU1-0] 747.319221 s: Driver/Notify Cb = 30.2 fps [IPU1-0] 747.319313 s: [IPU1-0] 747.319343 s: Input Statistics, [IPU1-0] 747.319404 s: [IPU1-0] 747.319435 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.319526 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.319618 s: -------------------------------------------------- [IPU1-0] 747.319709 s: 0 | 30. 2 0. 0 0. 0 30. 2 [IPU1-0] 747.319831 s: [IPU1-0] 747.319862 s: Output Statistics, [IPU1-0] 747.319923 s: [IPU1-0] 747.319953 s: CH | Out | Out | Out Drop | Out User Drop [IPU1-0] 747.320045 s: | ID | FPS | FPS | FPS [IPU1-0] 747.320106 s: --------------------------------------------- [IPU1-0] 747.320228 s: 0 | 0 30. 3 0. 0 0. 0 [IPU1-0] 747.320350 s: [IPU1-0] 747.320380 s: [ ISSCAPTURE ] LATENCY, [IPU1-0] 747.320441 s: ******************** [IPU1-0] 747.320502 s: [IPU1-0] 747.320624 s: [IPU1-0] 747.320655 s: ### CPU [IPU1-0], LinkID [ 84], [IPU1-0] 747.320746 s: [IPU1-0] 747.320777 s: [ ISSM2MISP ] Link Statistics, [IPU1-0] 747.320868 s: ****************************** [IPU1-0] 747.320929 s: [IPU1-0] 747.320960 s: Elapsed time = 568077 msec [IPU1-0] 747.321021 s: [IPU1-0] 747.321082 s: New data Recv = 30.3 fps [IPU1-0] 747.321173 s: Get Full Buf Cb = 90.8 fps [IPU1-0] 747.321234 s: Driver/Notify Cb = 30.3 fps [IPU1-0] 747.321326 s: [IPU1-0] 747.321356 s: Input Statistics, [IPU1-0] 747.321417 s: [IPU1-0] 747.321448 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.321539 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.321631 s: -------------------------------------------------- [IPU1-0] 747.321692 s: 0 | 30. 3 0. 0 0. 0 30. 3 [IPU1-0] 747.321844 s: [IPU1-0] 747.321875 s: Output Statistics, [IPU1-0] 747.321936 s: [IPU1-0] 747.321966 s: CH | Out | Out | Out Drop | Out User Drop [IPU1-0] 747.322027 s: | ID | FPS | FPS | FPS [IPU1-0] 747.322119 s: --------------------------------------------- [IPU1-0] 747.322210 s: 0 | 0 30. 3 0. 0 0. 0 [IPU1-0] 747.322332 s: 0 | 1 30. 2 0. 1 0. 0 [IPU1-0] 747.322454 s: 0 | 2 30. 3 0. 0 0. 0 [IPU1-0] 747.322576 s: 0 | 3 0. 0 30. 3 0. 0 [IPU1-0] 747.322698 s: [IPU1-0] 747.322729 s: [ ISSM2MISP ] LATENCY, [IPU1-0] 747.322790 s: ******************** [IPU1-0] 747.322851 s: Local Link Latency : Avg = 4752 us, Min = 4697 us, Max = 5490 us, [IPU1-0] 747.322973 s: Source to Link Latency : Avg = 4844 us, Min = 4758 us, Max = 5581 us, [IPU1-0] 747.323095 s: [IPU1-0] 747.323400 s: [IPU1-0] 747.323461 s: ### CPU [IPU1-0], LinkID [ 49], [IPU1-0] 747.323522 s: [IPU1-0] 747.323583 s: [ ALG_SCENE_OBSTRUCTION_DETECT ] Link Statistics, [IPU1-0] 747.323674 s: ****************************** [IPU1-0] 747.323735 s: [IPU1-0] 747.323766 s: Elapsed time = 578715 msec [IPU1-0] 747.323857 s: [IPU1-0] 747.323888 s: [IPU1-0] 747.323918 s: Input Statistics, [IPU1-0] 747.323979 s: [IPU1-0] 747.324010 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.324101 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.324223 s: -------------------------------------------------- [IPU1-0] 747.324315 s: [IPU1-0] 747.324345 s: Output Statistics, [IPU1-0] 747.324406 s: [IPU1-0] 747.324437 s: CH | Out | Out | Out Drop | Out User Drop [IPU1-0] 747.324528 s: | ID | FPS | FPS | FPS [IPU1-0] 747.324589 s: --------------------------------------------- [IPU1-0] 747.324681 s: [IPU1-0] 747.324711 s: [ ALG_SCENE_OBSTRUCTION_DETECT ] LATENCY, [IPU1-0] 747.324803 s: ******************** [IPU1-0] 747.324864 s: [IPU1-0] 747.324986 s: [IPU1-0] 747.325016 s: ### CPU [IPU1-0], LinkID [ 20], [IPU1-0] 747.325108 s: [IPU1-0] 747.325138 s: [ NULL ] Link Statistics, [IPU1-0] 747.325230 s: ****************************** [IPU1-0] 747.325291 s: [IPU1-0] 747.325321 s: Elapsed time = 578717 msec [IPU1-0] 747.325413 s: [IPU1-0] 747.325443 s: [IPU1-0] 747.325474 s: Input Statistics, [IPU1-0] 747.325535 s: [IPU1-0] 747.325565 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.325657 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.325748 s: -------------------------------------------------- [IPU1-0] 747.325809 s: [IPU1-0] 747.325870 s: Output Statistics, [IPU1-0] 747.325931 s: [IPU1-0] 747.325962 s: CH | Out | Out | Out Drop | Out User Drop [IPU1-0] 747.326023 s: | ID | FPS | FPS | FPS [IPU1-0] 747.326114 s: --------------------------------------------- [IPU1-0] 747.326206 s: [IPU1-0] 747.326267 s: [ NULL ] LATENCY, [IPU1-0] 747.326328 s: ******************** [IPU1-0] 747.326358 s: [IPU1-0] 747.326816 s: [IPU1-0] 747.326877 s: ### CPU [IPU1-0], LinkID [ 98], [IPU1-0] 747.326938 s: [IPU1-0] 747.326999 s: [ ISS Resizer ] Link Statistics, [IPU1-0] 747.327060 s: ****************************** [IPU1-0] 747.327121 s: [IPU1-0] 747.327182 s: Elapsed time = 568078 msec [IPU1-0] 747.327273 s: [IPU1-0] 747.327304 s: New data Recv = 30.3 fps [IPU1-0] 747.327395 s: Get Full Buf Cb = 30.3 fps [IPU1-0] 747.327456 s: Put Empty Buf Cb = 30.2 fps [IPU1-0] 747.327548 s: Driver/Notify Cb = 30.3 fps [IPU1-0] 747.327609 s: [IPU1-0] 747.327639 s: Input Statistics, [IPU1-0] 747.327700 s: [IPU1-0] 747.327731 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.327822 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.327883 s: -------------------------------------------------- [IPU1-0] 747.327975 s: 0 | 30. 3 0. 0 0. 0 30. 3 [IPU1-0] 747.328097 s: [IPU1-0] 747.328341 s: Output Statistics, [IPU1-0] 747.328402 s: [IPU1-0] 747.328432 s: CH | Out | Out | Out Drop | Out User Drop [IPU1-0] 747.328524 s: | ID | FPS | FPS | FPS [IPU1-0] 747.328585 s: --------------------------------------------- [IPU1-0] 747.328676 s: 0 | 0 30. 3 0. 0 0. 0 [IPU1-0] 747.328798 s: [IPU1-0] 747.328829 s: [ ISS Resizer ] LATENCY, [IPU1-0] 747.328890 s: ******************** [IPU1-0] 747.328951 s: Local Link Latency : Avg = 1285 us, Min = 1220 us, Max = 1708 us, [IPU1-0] 747.329073 s: Source to Link Latency : Avg = 6560 us, Min = 6435 us, Max = 7381 us, [IPU1-0] 747.329225 s: [IPU1-0] 747.329347 s: [IPU1-0] 747.329378 s: ### CPU [IPU1-0], LinkID [ 73], [IPU1-0] 747.329439 s: [IPU1-0] 747.329500 s: [ DISPLAY ] Link Statistics, [IPU1-0] 747.329561 s: ****************************** [IPU1-0] 747.329622 s: [IPU1-0] 747.329652 s: Elapsed time = 568079 msec [IPU1-0] 747.329713 s: [IPU1-0] 747.329774 s: New data Recv = 30.2 fps [IPU1-0] 747.329835 s: Driver/Notify Cb = 60.3 fps [IPU1-0] 747.329927 s: [IPU1-0] 747.329957 s: Input Statistics, [IPU1-0] 747.330018 s: [IPU1-0] 747.330049 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.330110 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.330232 s: -------------------------------------------------- [IPU1-0] 747.330293 s: 0 | 30. 3 0. 0 0. 0 30. 3 [IPU1-0] 747.330445 s: [IPU1-0] 747.330476 s: [ DISPLAY ] LATENCY, [IPU1-0] 747.330537 s: ******************** [IPU1-0] 747.330598 s: Local Link Latency : Avg = 46 us, Min = 30 us, Max = 275 us, [IPU1-0] 747.330720 s: Source to Link Latency : Avg = 6701 us, Min = 6557 us, Max = 7533 us, [IPU1-0] 747.330811 s: [IPU1-0] 747.330872 s: Display UnderFlow Count = 0 [IPU1-0] 747.330933 s: [IPU1-0] 747.331025 s: [IPU1-0] 747.331086 s: ### CPU [IPU1-0], LinkID [ 50], [IPU1-0] 747.331177 s: [IPU1-0] 747.331208 s: [ ALG_ISS_AEWB ] Link Statistics, [IPU1-0] 747.331269 s: ****************************** [IPU1-0] 747.331330 s: [IPU1-0] 747.331391 s: Elapsed time = 568082 msec [IPU1-0] 747.331452 s: [IPU1-0] 747.331482 s: New data Recv = 30.1 fps [IPU1-0] 747.331574 s: [IPU1-0] 747.331604 s: Input Statistics, [IPU1-0] 747.331665 s: [IPU1-0] 747.331696 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.331787 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.331848 s: -------------------------------------------------- [IPU1-0] 747.331940 s: 0 | 30. 2 0. 0 0. 0 30. 2 [IPU1-0] 747.332062 s: [IPU1-0] 747.332092 s: Output Statistics, [IPU1-0] 747.332184 s: [IPU1-0] 747.332214 s: CH | Out | Out | Out Drop | Out User Drop [IPU1-0] 747.332306 s: | ID | FPS | FPS | FPS [IPU1-0] 747.332367 s: --------------------------------------------- [IPU1-0] 747.332428 s: 0 | 0 30. 2 0. 0 0. 0 [IPU1-0] 747.332550 s: [IPU1-0] 747.332580 s: [ ALG_ISS_AEWB ] LATENCY, [IPU1-0] 747.332672 s: ******************** [IPU1-0] 747.332824 s: Local Link Latency : Avg = 1896 us, Min = 152 us, Max = 264138 us, [IPU1-0] 747.332946 s: Source to Link Latency : Avg = 7639 us, Min = 5825 us, Max = 269871 us, [IPU1-0] 747.333068 s: [IPU1-0] 747.333343 s: [IPU1-0] 747.333404 s: ### CPU [IPU1-0], LinkID [ 85], [IPU1-0] 747.333496 s: [IPU1-0] 747.333526 s: [ ISSM2MSIMCOP ] Link Statistics, [IPU1-0] 747.333587 s: ****************************** [IPU1-0] 747.333648 s: [IPU1-0] 747.333709 s: Elapsed time = 568085 msec [IPU1-0] 747.333770 s: [IPU1-0] 747.333801 s: New data Recv = 30.3 fps [IPU1-0] 747.333892 s: Get Full Buf Cb = 30.3 fps [IPU1-0] 747.333953 s: [IPU1-0] 747.333984 s: Input Statistics, [IPU1-0] 747.334045 s: [IPU1-0] 747.334075 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.334197 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.334289 s: -------------------------------------------------- [IPU1-0] 747.334350 s: 0 | 30. 3 0. 0 0. 0 30. 3 [IPU1-0] 747.334502 s: [IPU1-0] 747.334533 s: Output Statistics, [IPU1-0] 747.334594 s: [IPU1-0] 747.334624 s: CH | Out | Out | Out Drop | Out User Drop [IPU1-0] 747.334685 s: | ID | FPS | FPS | FPS [IPU1-0] 747.334777 s: --------------------------------------------- [IPU1-0] 747.334838 s: 0 | 0 30. 3 0. 0 0. 0 [IPU1-0] 747.334960 s: [IPU1-0] 747.334990 s: [ ISSM2MSIMCOP ] LATENCY, [IPU1-0] 747.335082 s: ******************** [IPU1-0] 747.335112 s: Local Link Latency : Avg = 9492 us, Min = 9394 us, Max = 9791 us, [IPU1-0] 747.335265 s: Source to Link Latency : Avg = 14506 us, Min = 14366 us, Max = 15128 us, [IPU1-0] 747.335387 s: [IPU1-0] 747.335509 s: [IPU1-0] 747.335539 s: ### CPU [IPU1-0], LinkID [ 74], [IPU1-0] 747.335631 s: [IPU1-0] 747.335661 s: [ DISPLAY ] Link Statistics, [IPU1-0] 747.335722 s: ****************************** [IPU1-0] 747.335783 s: [IPU1-0] 747.335814 s: Elapsed time = 568077 msec [IPU1-0] 747.335875 s: [IPU1-0] 747.335936 s: New data Recv = 30.2 fps [IPU1-0] 747.335997 s: Driver/Notify Cb = 60.3 fps [IPU1-0] 747.336088 s: [IPU1-0] 747.336119 s: Input Statistics, [IPU1-0] 747.336180 s: [IPU1-0] 747.336241 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.336302 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.336393 s: -------------------------------------------------- [IPU1-0] 747.336454 s: 0 | 30. 3 0. 0 0. 0 30. 3 [IPU1-0] 747.336607 s: [IPU1-0] 747.336637 s: [ DISPLAY ] LATENCY, [IPU1-0] 747.336698 s: ******************** [IPU1-0] 747.336759 s: Local Link Latency : Avg = 38 us, Min = 30 us, Max = 244 us, [IPU1-0] 747.336881 s: Source to Link Latency : Avg = 14647 us, Min = 14488 us, Max = 15280 us, [IPU1-0] 747.336973 s: [IPU1-0] 747.337034 s: Display UnderFlow Count = 0 [IPU1-0] 747.337095 s: [IPU1-0] 747.337125 s: CPU [ IPU1-0], LinkID [ 23], Link Statistics not available ! [IPU1-0] 747.337308 s: [IPU1-0] 747.337369 s: ### CPU [IPU1-0], LinkID [ 75], [IPU1-0] 747.337430 s: [IPU1-0] 747.337491 s: [ DISPLAY ] Link Statistics, [IPU1-0] 747.337552 s: ****************************** [IPU1-0] 747.337613 s: [IPU1-0] 747.337644 s: Elapsed time = 568139 msec [IPU1-0] 747.337705 s: [IPU1-0] 747.337766 s: Driver/Notify Cb = 60.3 fps [IPU1-0] 747.337827 s: [IPU1-0] 747.337857 s: Input Statistics, [IPU1-0] 747.337918 s: [IPU1-0] 747.337949 s: CH | In Recv | In Drop | In User Drop | In Process [IPU1-0] 747.338040 s: | FPS | FPS | FPS | FPS [IPU1-0] 747.338101 s: -------------------------------------------------- [IPU1-0] 747.338345 s: 0 | 0. 0 0. 0 0. 0 0. 0 [IPU1-0] 747.338498 s: [IPU1-0] 747.338528 s: [ DISPLAY ] LATENCY, [IPU1-0] 747.338589 s: ******************** [IPU1-0] 747.338650 s: Local Link Latency : Avg = 30 us, Min = 30 us, Max = 30 us, [IPU1-0] 747.338772 s: Source to Link Latency : Avg = 9049106 us, Min = 9049106 us, Max = 9049106 us, [IPU1-0] 747.338894 s: [IPU1-0] 747.338925 s: Display UnderFlow Count = 0 [IPU1-0] 747.338986 s: [IPU1-0] 747.838193 s: [IPU1-0] [IPU1-0] ==================== [IPU1-0] Chains Run-time Menu [IPU1-0] ==================== [IPU1-0] [IPU1-0] 0: Stop Chain [IPU1-0] [IPU1-0] 1: Toggle VTNF ON/OFF [IPU1-0] 2: Toggle LDC ON/OFF [IPU1-0] 3: Save Captured Frame [IPU1-0] 4: Save SIMCOP Output Frame [IPU1-0] 5: Save ISP Output Frame [IPU1-0] [IPU1-0] p: Print Performance Statistics [IPU1-0] [IPU1-0] Enter Choice: [IPU1-0] I don't understand how Source-to-Link Latency in last [ DISPLAY ] become in average 90ms (9049106 us). The Source-to-Link latency of previous [ DISPLAY ] is only 15ms (14647 us). What can be the reason of extra 75ms? Are any ways to reduce overall latency of camera-to-display pipeline on TDA2P-EVM to reasonable values? The complete log is attached below. Kind regards, Andrey (Please visit the site to view this file)

Forum Post: RE: TDA2SX: What IDE is recommended to customize the Vision SDK?

$
0
0
Thank you Rishabh, Here is a follow up question from a colleague: Referring to the response received, clearly using an editor would not be ideal for us but we could make some progress if someone pointed us to the file/function containing the scheduler which calls the FFT functions and Angle_Find function, etc…. If we can at least look at this source it might allow us to make some progress of using the Demo as a template for our own purposes. Thanks again, -Zach

Forum Post: RE: Linux/AM5718: Arago distribution

$
0
0
August, I'm sorry, I'm not familiar with that layer or how to use it as we don't use it in the SDK. You may have more luck working directly with the Yocto/OE community. Thanks, Ron

Forum Post: RE: TMS320C6747:Please tell me about a parallel flash.

$
0
0
Hello, Do you wish to bootload the program from the Flash when the power is applied to the board? Or do you wish to read/write data from the Flash during the execution of a program? Can you connect to the C6747 device with a JTAG emulator using CCS? The steps for creating a boot image with AISgen, , building the Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L137 , and running the Utility from CCS to program the boot image into flash were mentioned in the previous post: https://e2e.ti.com/support/processors/f/791/t/815196 Regards, Mark

Forum Post: RE: RTOS/TMDX654IDKEVM: Core/affinity assignment

$
0
0
Paul, I am not sure what is your intended use case. Core and task affinity assignment is only supported on Cortex A and Cortex M platforms that support SMP (symmetric processing) mode. Cortex R5 (MCU) only supports lockstep (core1 is diagnostic core for core0) and split mode (both cores are independent) operations. If your objective is to use core 1 for processing then you need create a independent SYSBIOS application for that core and ensure there is no overlap of resources in the two applications unless there is shared memory setup. Check the E2E discussion here: https://e2e.ti.com/support/processors/f/791/t/814666 Regards, Rahul

Forum Post: RE: Linux/AM5728: GPMC doesn't work

$
0
0
Hello, 1. I am wondering if you could please share more information on how you are connecting the GPMC. Please keep in mind that GPMC has to be configured as a host/master device and GPMC cannot be driven by other devices. 2. Are there any other devices driving the CS or any other pins in your configurations? 3. In your setup, please share how you are asserting the CS0? Regards, Krunal

Forum Post: RE: Linux/TMDSIDK574: PRP question

$
0
0
[quote user="VLeshka VV"]So, I'll try to make things right (if I'm right in my guess). The pruss1_eth associates to the PRU1ETH0 and PRU1ETH1. The pruss2_eth associates to the PRU2ETH0 and PRU2ETH1[/quote] Yes, and they will likely enumerate in Linux to ethx to ethy depending on the number of interfaces you have. [quote user="VLeshka VV"] 3.On AM572x IDK, only PRU-ICSS2 is supported. Hence only prueth.pruss2_type takes effect. Does this mean that pruss1_eth is impossible? [/quote] No. The SoC (AM574x) supports using 4 PRU Eth ports, but the board has a limitation to support only two PRU Eth ports. The AM571x IDK actually enables 4 PRU eth ports and should serve as a good Linux model for how to do this on AM572x/4x. I hope this helps you.

Forum Post: RE: RTOS/AM5728: FatFS console project crashes

$
0
0
Hi, We plan to fix this issue in PRSDK 6.1 (end of 2019 Q3), I am closing this issue for now. Regards, Eric

Forum Post: RE: RTOS/TMDX654IDKEVM: CAN-FD test

$
0
0
Paul, I will loop our automotive team to help with the the issue of CAN-FD setup since they have more experience with the setup and try to help you with the boot setup in the interim. Have you tested the application using the on board emulator before trying to boot. There is not enough information in your thread to answer your boot question. For SD boot, you need to have three files (tiboot3.bin, sysfw.bin and app). Do you have all these three files on the SD card. The app file is your test application, after converting to rprc format using out2rprc also needs to be combined to MulticoreImage formation using MulticoreImageGen tool. Did you perform this operation? The EVM has boot switches for WKUP_BOOTMODE and MAIN_BOOTMODE pin configuration to setup SD boot. Did you set the EVM boot switch correctly? It might help to first get a known good boot test case working so you know that the setup is correct. Have you run EVM diagnostics or boot examples to ensure that SD boot is working correctly on your HW setup. Regards, Rahul

Forum Post: RE: Linux/AM4378: USB3.0 disk doesn't work

$
0
0
Hi David, When I initially looked at this issue a few years ago, I didn't have enough time to understand the root cause, and only understood the problem is due to both the USB host and device do not agree on some LPM parameters/protocol, but not sure whose fault. As the patch does, disabling LPM on the host works around the issue.

Forum Post: RE: Linux/AM3358: NAND access on GP EVM

$
0
0
Tony, I'm afraid your EVM may just be too old. I booted my rev 2.1 board and was able to see the NAND with no problems. Here is the U-Boot output: U-Boot 2018.01-g9d984f4548 (Apr 06 2019 - 07:42:30 +0000) CPU : AM335X-GP rev 2.1 Model: TI AM335x EVM DRAM: 1 GiB NAND: 256 MiB MMC: OMAP SD/MMC: 0 *** Warning - bad CRC, using default environment And here is Linux: root@am335x-evm:~# dmesg | grep nand [ 0.184952] omap-gpmc 50000000.gpmc: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/nandflash_pins_s0, deferring probe [ 1.529280] omap2-nand 8000000.nand: GPIO lookup for consumer rb [ 1.529289] omap2-nand 8000000.nand: using device tree for GPIO lookup [ 1.529334] of_get_named_gpiod_flags: parsed 'rb-gpios' property of node '/ocp/gpmc@50000000/nand@0,0[0]' - status (0) [ 1.529523] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda [ 1.535947] nand: Micron MT29F2G08ABAEAWP [ 1.540103] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 1.547827] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme [ 1.553315] 10 ofpart partitions found on MTD device omap2-nand.0 [ 1.559461] Creating 10 MTD partitions on "omap2-nand.0": root@am335x-evm:~# cat /proc/mtd dev: size erasesize name mtd0: 00020000 00020000 "NAND.SPL" mtd1: 00020000 00020000 "NAND.SPL.backup1" mtd2: 00020000 00020000 "NAND.SPL.backup2" mtd3: 00020000 00020000 "NAND.SPL.backup3" mtd4: 00040000 00020000 "NAND.u-boot-spl-os" mtd5: 00100000 00020000 "NAND.u-boot" mtd6: 00020000 00020000 "NAND.u-boot-env" mtd7: 00020000 00020000 "NAND.u-boot-env.backup1" mtd8: 00800000 00020000 "NAND.kernel" mtd9: 0f600000 00020000 "NAND.file-system" I believe I had the board configured in it's default state, but to be most clear here is what I have: Profile Selection: Sysboot Pins: I hope this helps you.

Forum Post: RE: Linux/AM4378: ADC data out of order

$
0
0
Hello Joshua, I apologize for the delay. I will have a response for you next week. Regards, Nick

Forum Post: RE: Linux/AM3358: 4G USB Simcom module IC detect issue

$
0
0
On Beaglebone Black, not on your board? No matter how you change the software, I don't understand how its USB0 port would work in host mode. Where is the 5V VBUS power come from? There is no VBUS power source for USB0 on the Beaglebone Black board.

Forum Post: RE: RTOS/TMS320C6678: Flash booting Issues

$
0
0
Jack, The instructions to program images into NAND are in the ReadME.txt attached (Please visit the site to view this file) The C6678 EVM comes with default images programmed in NAND, NOR and I2C. IF you want to restore the images in the EVM, then you can use the script provided here: http://processors.wiki.ti.com/index.php/BIOS_MCSDK_2.0_User_Guide#Using_Program_EVM The script has been moved to the following location in Processor SDK RTOS: EVM programming script: processor_sdk_rtos_c667x_x_xx_xx_xx\bin\program_evm.js Prebuilt binaries : processor_sdk_rtos_c667x_x_xx_xx_xx\prebuilt-images Hope this helps. Regards, Rahul

Forum Post: RE: RTOS/AM4376: VLAN tag issue in HSR packet

$
0
0
Alexey, thank you for the explanation and the files. I will send the information to our HSR-PRP experts. Please be patience as some of the key people to check this are out of office. Paula

Forum Post: Linux: eMMC cannot boot on MMC0 am335x

$
0
0
Tool/software: Linux Hi Ti, I'm using SD card (4GB) on MMC1 and eMMC 16GB on MMC0, am335x. I had read in technical document that eMMC cannot boot MMC0 with capacity higher than 4GB. I created SD 2 partitions (boot and rootfs), and eMMC 2 partitions(boot and rootfs). I put MLO and u-boot.img to SD card (MMC1, boot partition (uuid 1:1) and rootfs (zImage, dtb, roootfile ) to eMMC (MMC0), rootfs partititon (uuid 0:2) I want to boot MLO,u-boot.img from SD card (uuid 1:1) and boot zImage from eMMC (MMC0, UUID 0:2) but fail. I think to modify uboot source code to change partititon but i cannot see that. My BSP version: ti-processor-sdk-linux-am335x-evm-02.00.02.11, uboot version: 2015.07-00067 Please help me!
Viewing all 125265 articles
Browse latest View live