66AK2H06: 66AK2H06
RTOS/AM5746: About supervisor access
Part Number:AM5746
Tool/software: TI-RTOS
Hi.
My customer was reading the EDMA section of TRM and had question about supervisor access.
Question 1
When both supervisor access and user access are enabled, can they be accessed regardless of memory attribute?
Question 2
Is it possible to access the user access area under the following options?
・Supervisor access enabled
・User access disabled
Regards,
Rei
TMS320VC33: Maximum Junction Temperature Rating for the TMS320VC33PGEA120
Part Number:TMS320VC33
Hi,
I am looking for the Maximum junction temperature for the TMS320VC33PGEA120.
The data sheet lists the temperature rating as -40°C to 100°C. I am wondering what the maximum junction temperature will be.
Please let me know,
Thanks
Sam
AM3358: UVC based camera image capture issue
Part Number:AM3358
Hi,
I am trying to capture MJPEG 3264X2448 frame on BeableBoneBlack AM3358 processor based board. Currently using latest TI SDK.
I have capture usbmon logs for good and bad case. Need help to understand where is the issue.
Good log is for case MJPEG 640x480 frame and bad case for MJPEG 3264x2448 frame.
Camera is connected over USB. When MJPEG frame is captured for 3264X2448, fame/jpeg image capture is incomplete. When such image(capturing MJPEG fame and save to file) is decoded using any image view application, it shows black/grey strip at bottom.
Best Regards,
Vikas(Please visit the site to view this file)(Please visit the site to view this file)
RTOS/AM5728: McASP2 xref_clk0
Part Number:AM5728
Tool/software: TI-RTOS
Is there a way to modify the frequency of xref_clk0 through a phase lock loop before it hits McASP2 as the high frequency clock?
Thank you
RTOS/AM5726: Board initialization hangs on pad IO de-isolation
Part Number:AM5726
Tool/software: TI-RTOS
We are bringing up our custom board with an AM5726, based on the AM5728 IDK board. We are having an issue running the UART_BasicExample_idkAM572x_armExampleProject. Using the debugger, we traced down the issue to the board initialization step (beginning with the Board_init() function in main). More specifically, the process execution hangs in ~/ti/pdk_am57xx_1_0_11/packages/ti/board/src/idkAM572x/iodelay_config.c; in the boardPadIoDeIsolation() function, at this line:
CSL_FINS(ctrlCoreRegs->SMA_SW_0, CONTROL_CORE_SMA_SW_0_SMA_SW_0_ISO,
0x0U);
It never seems to return from this function or finish pad de-isolation. I have been looking through the TRM for the IDK, but have not been able to find much about what this function does or what could be causing this issue. Pad io isolation works fine, it is just during this de-isolation step that it gets hung up. To be clear, this all works fine on the IDK board, it is our custom board that we are experiencing the issue. I would appreciate any troubleshooting tips or things to look at in our hardware design that may be causing this issue.
Linux/AM4378: Custom Device Tree, SPL can't find serial driver
Part Number:AM4378
Tool/software: Linux
When I try to boot my board using my custom device tree, the SPL fails and gets to the line:
panic_str("No serial driver found");
When I use the am437x-gp-evm device tree file, it loads the serial driver just fine and prints the U-boot output to minicom. I'm using uart0 for the serial console, and I'm pretty sure I have things set up the same way the EVM device tree file does it, so I'm not sure why it is failing.
In my .dts file, I have the stdout path set as follows:
chosen {
stdout-path = &uart0;
};
And I configure the uart0 pins in the mux.c file, just like the EVM file does. Any ideas about what I am doing wrong?
Linux/PROCESSOR-SDK-TDAX: getting repo init error(looking for glsdk manifest instead of psdkla)
Part Number:PROCESSOR-SDK-TDAX
Tool/software: Linux
Hi
I am getting similar error w.r.t thread https://e2e.ti.com/support/processors/f/791/t/741536
why it is looking for glsdk instead of psdkla?
fatal: repository 'git.ti.com/.../' not found
fatal: cannot obtain manifest git://git.ti.com/glsdk/release-manifest.git
Failed setup, aborting..
Failed setup, aborting..
I am following http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Automotive_Software_Developers_Guide
Linux: TIDL eve_test_dl_algo invalid output for MobileNet V1
Tool/software: Linux
Hi,
I'm using ti-processor-sdk-linux-am57xx-evm-05.02.00.10 and try to run MobileNet V1 using eve_test_dl_algo.out (or eve_test_dl_algo_ref.out) on the host.
I took the model, config file, and test vector from the tidl-examples-1.2.2 folder.
This is the config file: tidl_config_mobileNet1.txt
numFrames = 1 preProcType = 2 inData = ./preproc_2_224x224.y outData = "./stats_tool_out.bin" traceDumpBaseName = "./out/trace_dump_" netBinFile = "./tidl_net_mobilenet_1_224.bin" paramsBinFile = "./tidl_param_mobilenet_1_224.bin" inWidth = 224 inHeight = 224 inNumChannels = 3
I run inference with this command:
ti-processor-sdk-linux-am57xx-evm-05.02.00.10/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/eve_test_dl_algo.out config_list.txt
This is the printout:
Processing config file ./tidl_config_mobileNet1.txt ! 0, TIDL_DataLayer , 0, -1 , 1 , x , x , x , x , x , x , x , x , 0 , 0 , 0 , 0 , 0 , 1 , 3 , 224 , 224 , 1, TIDL_ConvolutionLayer , 1, 1 , 1 , 0 , x , x , x , x , x , x , x , 1 , 1 , 3 , 224 , 224 , 1 , 32 , 112 , 112 , 2, TIDL_ConvolutionLayer , 1, 1 , 1 , 1 , x , x , x , x , x , x , x , 2 , 1 , 32 , 112 , 112 , 1 , 32 , 112 , 112 , 3, TIDL_ConvolutionLayer , 1, 1 , 1 , 2 , x , x , x , x , x , x , x , 3 , 1 , 32 , 112 , 112 , 1 , 64 , 112 , 112 , 4, TIDL_ConvolutionLayer , 1, 1 , 1 , 3 , x , x , x , x , x , x , x , 4 , 1 , 64 , 112 , 112 , 1 , 64 , 56 , 56 , 5, TIDL_ConvolutionLayer , 1, 1 , 1 , 4 , x , x , x , x , x , x , x , 5 , 1 , 64 , 56 , 56 , 1 , 128 , 56 , 56 , 6, TIDL_ConvolutionLayer , 1, 1 , 1 , 5 , x , x , x , x , x , x , x , 6 , 1 , 128 , 56 , 56 , 1 , 128 , 56 , 56 , 7, TIDL_ConvolutionLayer , 1, 1 , 1 , 6 , x , x , x , x , x , x , x , 7 , 1 , 128 , 56 , 56 , 1 , 128 , 56 , 56 , 8, TIDL_ConvolutionLayer , 1, 1 , 1 , 7 , x , x , x , x , x , x , x , 8 , 1 , 128 , 56 , 56 , 1 , 128 , 28 , 28 , 9, TIDL_ConvolutionLayer , 1, 1 , 1 , 8 , x , x , x , x , x , x , x , 9 , 1 , 128 , 28 , 28 , 1 , 256 , 28 , 28 , 10, TIDL_ConvolutionLayer , 1, 1 , 1 , 9 , x , x , x , x , x , x , x , 10 , 1 , 256 , 28 , 28 , 1 , 256 , 28 , 28 , 11, TIDL_ConvolutionLayer , 1, 1 , 1 , 10 , x , x , x , x , x , x , x , 11 , 1 , 256 , 28 , 28 , 1 , 256 , 28 , 28 , 12, TIDL_ConvolutionLayer , 1, 1 , 1 , 11 , x , x , x , x , x , x , x , 12 , 1 , 256 , 28 , 28 , 1 , 256 , 14 , 14 , 13, TIDL_ConvolutionLayer , 1, 1 , 1 , 12 , x , x , x , x , x , x , x , 13 , 1 , 256 , 14 , 14 , 1 , 512 , 14 , 14 , 14, TIDL_ConvolutionLayer , 1, 1 , 1 , 13 , x , x , x , x , x , x , x , 14 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 15, TIDL_ConvolutionLayer , 1, 1 , 1 , 14 , x , x , x , x , x , x , x , 15 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 16, TIDL_ConvolutionLayer , 1, 1 , 1 , 15 , x , x , x , x , x , x , x , 16 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 17, TIDL_ConvolutionLayer , 1, 1 , 1 , 16 , x , x , x , x , x , x , x , 17 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 18, TIDL_ConvolutionLayer , 1, 1 , 1 , 17 , x , x , x , x , x , x , x , 18 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 19, TIDL_ConvolutionLayer , 1, 1 , 1 , 18 , x , x , x , x , x , x , x , 19 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 20, TIDL_ConvolutionLayer , 1, 1 , 1 , 19 , x , x , x , x , x , x , x , 20 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 21, TIDL_ConvolutionLayer , 1, 1 , 1 , 20 , x , x , x , x , x , x , x , 21 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 22, TIDL_ConvolutionLayer , 1, 1 , 1 , 21 , x , x , x , x , x , x , x , 22 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 23, TIDL_ConvolutionLayer , 1, 1 , 1 , 22 , x , x , x , x , x , x , x , 23 , 1 , 512 , 14 , 14 , 1 , 512 , 14 , 14 , 24, TIDL_ConvolutionLayer , 1, 1 , 1 , 23 , x , x , x , x , x , x , x , 24 , 1 , 512 , 14 , 14 , 1 , 512 , 7 , 7 , 25, TIDL_ConvolutionLayer , 1, 1 , 1 , 24 , x , x , x , x , x , x , x , 25 , 1 , 512 , 7 , 7 , 1 , 1024 , 7 , 7 , 26, TIDL_ConvolutionLayer , 1, 1 , 1 , 25 , x , x , x , x , x , x , x , 26 , 1 , 1024 , 7 , 7 , 1 , 1024 , 7 , 7 , 27, TIDL_ConvolutionLayer , 1, 1 , 1 , 26 , x , x , x , x , x , x , x , 27 , 1 , 1024 , 7 , 7 , 1 , 1024 , 7 , 7 , 28, TIDL_PoolingLayer , 1, 1 , 1 , 27 , x , x , x , x , x , x , x , 28 , 1 , 1024 , 7 , 7 , 1 , 1 , 1 , 1024 , 29, TIDL_InnerProductLayer , 1, 1 , 1 , 28 , x , x , x , x , x , x , x , 29 , 1 , 1 , 1 , 1024 , 1 , 1 , 1 , 1001 , 30, TIDL_SoftMaxLayer , 1, 1 , 1 , 29 , x , x , x , x , x , x , x , 30 , 1 , 1 , 1 , 1001 , 1 , 1 , 1 , 1001 , 31, TIDL_DataLayer , 0, 1 , -1 , 30 , x , x , x , x , x , x , x , 0 , 1 , 1 , 1 , 1001 , 0 , 0 , 0 , 0 , Layer ID ,inBlkWidth ,inBlkHeight ,inBlkPitch ,outBlkWidth ,outBlkHeight,outBlkPitch ,numInChs ,numOutChs ,numProcInChs,numLclInChs ,numLclOutChs,numProcItrs ,numAccItrs ,numHorBlock ,numVerBlock ,inBlkChPitch,outBlkChPitc,alignOrNot 1 72 60 72 32 28 32 3 32 3 1 8 1 3 4 4 4320 896 1 2 40 30 40 32 28 32 1 1 1 1 1 1 1 4 4 1200 896 1 3 32 28 32 32 28 32 32 64 32 8 8 1 4 4 4 896 896 1 4 72 60 72 32 28 32 1 1 1 1 1 1 1 2 2 4320 896 1 5 32 28 32 32 28 32 64 128 64 8 8 1 8 2 2 896 896 1 6 40 30 40 32 28 32 1 1 1 1 1 1 1 2 2 1200 896 1 7 32 28 32 32 28 32 128 128 128 8 8 1 16 2 2 896 896 1 8 72 60 72 32 28 32 1 1 1 1 1 1 1 1 1 4320 896 1 9 32 28 32 32 28 32 128 256 128 8 8 1 16 1 1 896 896 1 10 40 30 40 32 28 32 1 1 1 1 1 1 1 1 1 1200 896 1 11 32 28 32 32 28 32 256 256 256 8 8 1 32 1 1 896 896 1 12 40 32 40 16 14 16 1 1 1 1 1 1 1 1 1 1280 224 1 13 16 14 16 16 14 16 256 512 256 8 8 1 32 1 1 224 224 1 14 24 16 24 16 14 16 1 1 1 1 1 1 1 1 1 384 224 1 15 16 14 16 16 14 16 512 512 512 8 8 1 64 1 1 224 224 1 16 24 16 24 16 14 16 1 1 1 1 1 1 1 1 1 384 224 1 17 16 14 16 16 14 16 512 512 512 8 8 1 64 1 1 224 224 1 18 24 16 24 16 14 16 1 1 1 1 1 1 1 1 1 384 224 1 19 16 14 16 16 14 16 512 512 512 8 8 1 64 1 1 224 224 1 20 24 16 24 16 14 16 1 1 1 1 1 1 1 1 1 384 224 1 21 16 14 16 16 14 16 512 512 512 8 8 1 64 1 1 224 224 1 22 24 16 24 16 14 16 1 1 1 1 1 1 1 1 1 384 224 1 23 16 14 16 16 14 16 512 512 512 8 8 1 64 1 1 224 224 1 24 40 18 40 16 7 16 1 1 1 1 1 1 1 1 1 720 112 1 25 16 7 16 16 7 16 512 1024 512 8 8 1 64 1 1 112 112 1 26 24 9 24 16 7 16 1 1 1 1 1 1 1 1 1 216 112 1 27 16 7 16 16 7 16 1024 1024 1024 8 8 1 128 1 1 112 112 1 Processing Frame Number : 0 Layer 1 : Out Q : 19199 , TIDL_ConvolutionLayer, PASSED #MMACs = 10.84, 9.63, Sparsity : 11.11 Layer 2 : Out Q : 10879 , TIDL_ConvolutionLayer, PASSED #MMACs = 3.61, 3.61, Sparsity : 0.00 Layer 3 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 25.69, 20.47, Sparsity : 20.31 Layer 4 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 1.81, 1.81, Sparsity : 0.00 Layer 5 : Out Q : 11291 , TIDL_ConvolutionLayer, PASSED #MMACs = 25.69, 24.56, Sparsity : 4.39 Layer 6 : Out Q : 10877 , TIDL_ConvolutionLayer, PASSED #MMACs = 3.61, 3.61, Sparsity : 0.00 Layer 7 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 51.38, 50.97, Sparsity : 0.81 Layer 8 : Out Q : 11091 , TIDL_ConvolutionLayer, PASSED #MMACs = 0.90, 0.90, Sparsity : 0.00 Layer 9 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 25.69, 25.68, Sparsity : 0.02 Layer 10 : Out Q : 10879 , TIDL_ConvolutionLayer, PASSED #MMACs = 1.81, 1.81, Sparsity : 0.00 Layer 11 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 51.38, 51.38, Sparsity : 0.00 Layer 12 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 0.45, 0.45, Sparsity : 0.00 Layer 13 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 25.69, 25.68, Sparsity : 0.02 Layer 14 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 0.90, 0.90, Sparsity : 0.00 Layer 15 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 51.38, 51.38, Sparsity : 0.00 Layer 16 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 0.90, 0.90, Sparsity : 0.00 Layer 17 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 51.38, 51.28, Sparsity : 0.20 Layer 18 : Out Q : 10878 , TIDL_ConvolutionLayer, PASSED #MMACs = 0.90, 0.90, Sparsity : 0.00 Layer 19 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 51.38, 51.28, Sparsity : 0.20 Layer 20 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 0.90, 0.90, Sparsity : 0.00 Layer 21 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 51.38, 51.38, Sparsity : 0.01 Layer 22 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 0.90, 0.90, Sparsity : 0.00 Layer 23 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 51.38, 51.38, Sparsity : 0.00 Layer 24 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 0.23, 0.23, Sparsity : 0.00 Layer 25 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 25.69, 25.59, Sparsity : 0.39 Layer 26 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 0.45, 0.45, Sparsity : 0.00 Layer 27 : Out Q : 10880 , TIDL_ConvolutionLayer, PASSED #MMACs = 51.38, 51.38, Sparsity : 0.00 Layer 28 : Out Q : 11019 , TIDL_PoolingLayer, PASSED #MMACs = 0.00, 0.00, Sparsity : 0.00 Layer 29 : Out Q : 2826 , TIDL_InnerProductLayer, PASSED #MMACs = 0.00, 0.00, Sparsity : 0.00 Layer 30 :-------Max Index 909 : 19 ------- #MMACs = 0.00, 0.00, Sparsity : 0.00 End of config list found !
However, most bytes of the output file stats_tool_out.bin are zero:
Output length: 1001 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19 19 8 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 19 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 19 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19 0 0 0 0 0 0 0 0 0 0 0 7 19 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
I also tried to run it with eve_test_algo_ref.out. The outputs are not the same but again most bytes are zero.
Linux/AM5728: Ethernet PHY randomly disappears
Part Number:AM5728
Tool/software: Linux
My custom AM5728 board cannot connect to the network about 2 out 3 boots because the Ethernet PHY (BCM54610) disappears!
This is when it works:
U-Boot 2018.01-g62414e2c81 (Mar 25 2019 - 18:36:04 +0000)
CPU : DRA752-GP ES2.0
Model: TI AM5728 IDK
Board: Solix19 Dev
DRAM: 2 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - bad CRC, using default environment
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net:
Warning: ethernet@48484000 using MAC address from ROM
eth0: ethernet@48484000
Hit any key to stop autoboot: 0
root@solix:~# dmesg | grep -i eth
[ 2.151339] cpsw 48484000.ethernet: No slave[1] phy_id, phy-handle, or fixed-link property
[ 2.159689] cpsw 48484000.ethernet: Detected MACID = 34:03:de:ca:d0:7a
[ 2.166323] cpsw 48484000.ethernet: initialized cpsw ale version 1.4
[ 2.172743] cpsw 48484000.ethernet: ALE Table size 1024
[ 2.178036] cpsw 48484000.ethernet: cpts: overflow check period 500 (jiffies)
[ 3.284323] systemd[1]: /lib/systemd/system/eth0-up.service:13: Unknown lvalue 'After' in section 'Install'
[ 7.103159] net eth0: initializing cpsw version 1.15 (0)
[ 7.156786] net eth0: phy "" not found on slave 1, err -19
[ 7.168656] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 8.240135] cpsw 48484000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 8.252017] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 9.280086] cpsw 48484000.ethernet eth0: Link is Down
[ 11.360152] cpsw 48484000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
root@solix:~# dmesg | grep -i phy
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] arch_timer: cp15 timer(s) running at 6.14MHz (phys).
[ 2.056926] libphy: Fixed MDIO Bus: probed
[ 2.130112] davinci_mdio 48485000.mdio: detected phy mask fffffffe
[ 2.138647] libphy: 48485000.mdio: probed
[ 2.142711] davinci_mdio 48485000.mdio: phy[0]: device 48485000.mdio:00, driver unknown
[ 2.151339] cpsw 48484000.ethernet: No slave[1] phy_id, phy-handle, or fixed-link property
[ 7.156655] Generic PHY 48485000.mdio:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=48485000.mdio:00, irq=POLL)
[ 7.156781] libphy: PHY not found
[ 7.156786] net eth0: phy "" not found on slave 1, err -19
root@solix:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)
Link detected: yes
And this is when it doesn't:
U-Boot 2018.01-g62414e2c81 (Mar 25 2019 - 18:36:04 +0000)
CPU : DRA752-GP ES2.0
Model: TI AM5728 IDK
Board: Solix19 Dev
DRAM: 2 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - bad CRC, using default environment
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net: Could not get PHY for ethernet@48484000: addr 0
root@solix:~# dmesg | grep -i eth
[ 2.163116] cpsw 48484000.ethernet: No slave[1] phy_id, phy-handle, or fixed-link property
[ 2.171465] cpsw 48484000.ethernet: Detected MACID = 34:03:de:ca:d0:7a
[ 2.178078] cpsw 48484000.ethernet: initialized cpsw ale version 1.4
[ 2.184482] cpsw 48484000.ethernet: ALE Table size 1024
[ 2.189775] cpsw 48484000.ethernet: cpts: overflow check period 500 (jiffies)
[ 3.297448] systemd[1]: /lib/systemd/system/eth0-up.service:13: Unknown lvalue 'After' in section 'Install'
[ 8.011871] net eth0: initializing cpsw version 1.15 (0)
[ 8.161286] net eth0: phy "48485000.mdio:00" not found on slave 0, err -19
[ 8.161305] net eth0: phy "" not found on slave 1, err -19
[ 8.176401] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 53.657624] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
root@solix:~# dmesg | grep -i phy
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] arch_timer: cp15 timer(s) running at 6.14MHz (phys).
[ 2.075205] libphy: Fixed MDIO Bus: probed
[ 2.148541] davinci_mdio 48485000.mdio: no live phy, scanning all
[ 2.163116] cpsw 48484000.ethernet: No slave[1] phy_id, phy-handle, or fixed-link property
[ 8.035611] libphy: PHY 48485000.mdio:00 not found
[ 8.161286] net eth0: phy "48485000.mdio:00" not found on slave 0, err -19
[ 8.161301] libphy: PHY not found
[ 8.161305] net eth0: phy "" not found on slave 1, err -19
root@solix:~# ethtool eth0
Settings for eth0:
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)
Link detected: no
My Kernel is 4.14 from SDK 5.02. I have a batch of identical boards, but only 2 from the same batch show this issue. This could indicate PCB component issue, but I checked the boards and nothing really stands out.
Linux/AM4378: Linux Kernel boot hangs
Part Number:AM4378
Tool/software: Linux
Hey Kemal,
Based on the previous thread, I am getting to the point in the boot process where the kernel tries to start, but it just hangs. I can see in U-boot code it just to the line:
kernel_entry(0, machid, r2);
and then it fails. I was trying to follow the training series at https://training.ti.com/linux-board-porting-series-module-10-debugging-linux-kernel-jtag-ccs?cu=399066 to debug the kernel code, but it is out of date and doesn't line up the current SDK. If you could give me any pointers on how to debug this I would appreciate it!
Thanks,
Tanner
Linux/AM5718: Arago/Yocto wpa-supplicant version question
Part Number:AM5718
Tool/software: Linux
Hello,
I'm trying to build a custom image based on the arago distribution corresponding to SDK 05.02.00.10.
My project will use an USB wifi dongle and I need to include the wpa-supplicant package.
However, if I put IMAGE_INSTALL_append = " wpa-supplicant" in my image recipe the build process pulls in wpa-supplicant-wl18xx from the meta-arago layer, which seems to be a custom version for the TI WL18XX modules.
How can override this behavior and use the recipe from oe-core/meta layer? I tried setting PREFERRED_VERSION
_wpa-supplicant="2.6" but did not make any difference. The only thing that seems to work is removing the wpa-supplicant-wl18xx.bb recipe from meta-arago, but I'm thinking there has to be a better way.
Please advise,
--Tavi
Linux/AM5726: fastest way to share data with DSP
Part Number:AM5726
Tool/software: Linux
Hello everybody ,
I m using Linux on A15 . I would like to offload A15 , having some tasks moved in the DSP
being motor control I need a fast communication between the A15 and DSP .
as for now using rpmsg I got 70us just to exchange one message : I need to be much better ( ideally < 10uS )
how can I proceed ? where to find info on doing this ?
could LInuxRT give me better results ?
best regards
Carlo
AM5718: HW Design Checklist - ferrite beads on unused interface power pins?
Part Number:AM5718
Sitara Team,
In the HW Design Checklist document, SPRACK7, sections 2.7.4 and 2.7.6 say:
2.7.4 If HDMI is not Used
• VDDA_HDMI should be connected through a ferrite bead to V1_8D
2.7.6 If SATA is not Used
• VDDA_SATA should be connected to V1_8D through a ferrite bead.
What are the purpose of the ferrite beads, and are they really necessary?
Regards,
David
CCS/TMS320C6678: How to use ti-processor-sdk-rtos-c667x-evm-05.02.00.10 for platform library ... SYS/BIOS ?
Part Number:TMS320C6678
Tool/software: Code Composer Studio
Hello.
I had developed the c6678 board using MCSDK 2.1.2.6 (old SDK).
Now, we're going to use ti-processor-sdk-rtos-c667x-evm-05.02.00.10 attempt to develop RTSC project.
CCS 8.3
- bios_6_73_01_01
- ipc_3_50_03_04
- openmp_dsp_c667x_2_06_02_01
- pdk_c667x_2_0_12
Ask questions use the new SDK because it differs from the old SDK method.
1. The previously used platform lib could not be declared in the *.cfg file in the new SDK.
ex) var ti_platform_evmc6678l_Settings = xdc.useModule ('ti.platform.evmc6678l.Settings');
Program.sectMap["platform_lib"] = "DDR3";;
>> How should platform library be used in the new SDK on the SYS/BIOS? Include related header only? PDK build??
< new SDK ... There isn't platform / evmc6678l >
< MCSDK 2.1.2.6(old SDK) project capture There is a platform / evmc6678l>
2. I can't see the example project(pcie or hyperlink example) into new SDK(ti-processor-sdk-rtos-c667x-evm-05.02.00.10) .
Looking at the PDK folder (C:\ti\pdk_c667x_2_0_12\packages),
"pdkProjectCreate.bat C6678 all little hyplnk example dsp",
"pdkProjectCreate.bat C6678 all little pcie example dsp",
I got an example project.
> "Run project" type as an "example" to create two example projects.
What is the difference between two example projects?
< Hyperlink >
hyplnk_evmc667_C66BiosExampleProject ( ??)
hyplnk_evmc667_C66DevLibBiosExampleProject(?! test)
< PCIE >
PCIE_evmc6678_wSoCFile_C66BiosExampleProject ( ??)
PCIE_evmc6678_wSoCLib_C66BiosExampleProject (?! test)
thanks
Linux/TDA2EVM5777: in iva_enc/encLink_common.c: (width
Part Number:TDA2EVM5777
Tool/software: Linux
I need a code width = 4 * 1280, height = 4 * 720 one frame image. However, the following problems occur
: in iva_enc/encLink_common.c: (width <= UTILS_ENCDEC_RESOLUTION_CLASS_16MP_WIDTH) && (height <= UTILS_ENCDEC_RESOLUTION_CLASS_16MP_HEIGHT) : failed !!!
I will #defineUTILS_ENCDEC_RESOLUTION_CLASS_16MP_WIDTH (4*1024) #define UTILS_ENCDEC_RESOLUTION_CLASS_16MP_HEIGHT (4*1024) in utils_encdec.h Change into #defineUTILS_ENCDEC_RESOLUTION_CLASS_16MP_WIDTH (4*1280) #define UTILS_ENCDEC_RESOLUTION_CLASS_16MP_HEIGHT (4*1024).
What else do I need to change?
Linux/DRA712: How to connect FPD-Link III signal in DRA712 use CSI-2 port
Part Number:DRA712
Tool/software: Linux
Hello guys :
I need to get FPD-Link III serializer signal into DRA712, I want use [ DS90UB940 -----> CSI-2 port of DRA712 ] structure, About there there are three questions need fix:
1: are there any low level driver code for DS90UB940 in DRA712 SDK
2: which working mode of DS90UB940 should I select ??
working mode shown on page 38 on this link www.ti.com/lit/ds/symlink/ds90ub940-q1.pdf
3: DRA712 CSI-2 port just has CSI2_0_DX[2:0] and CSI2_0_DY[2:0] , but DS90UB940 has D[3:0]+/- and CLK+/-
Thanks
RZ
Linux/AM5728: AM5728 is shutting down at temperature 65C
AM5728: AM5728 IDK .brd is empty
Part Number:AM5728
Customer said the .brd file download from this URL is empty, I don't have CAD tools to verify, Would you please confirm.
AUDIOCAPDSP-C55X: Connecting a speaker
Part Number:AUDIOCAPDSP-C55X
Hi,
I need help according to audio capactive booster pack. I want to connect speaker with this booster pack instead of headset, how can I do this, any one help me
Regard
Asim Gulzar