Part Number:LINUXSDK-OMAPL138
Tool/software:TI-RTOS
hi
I have one question.
I can not understand.
Always say you do not support mcsdk.
And tell them to use the processor sdk.
Then processor sdk should be better, but I do not look any better.
Why use u-boot in SOC and do you distribute zImage only on processor sdk?
I used ti-processor-sdk-linux-am335x-evm-04.02.00.09.
I used ti-processor-sdk-linux-omapl138-lcdk-04.02.00.09.
The above processor-sdk has only u-boot but no uImage.
So I set it up to run tftp / nfs using setup.sh.
I did make all.
However, no uImage is created.
Do you really know that this package is wrong?
You provide this image (u-boot and zImage).
Do not you have to tell them exactly how to test?
Are u-boot and zImage loaded and working normally?
Or will uImage be created in the processor-sdk configuration you provide?
Why not create uImage while providing tftp / nfs mode?
Do you offer tftp / nfs mode while providing sdk, which is not that either?
Why did uImage not be provided and configured to use u-boot?
You will ask me if I have a prebuilt image.
I have.
You know.
Providing uImage is mcsdk, not processor sdk.
processor sdk is zImage.
Try installing these two sdk.
You will see that there is no uImage anywhere.
Please let me know if I do not know.
I would prefer to use tftp / nfs for development first.