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.

PROCESSOR-SDK-AM335X: sfdisk not part of build package

Part Number: PROCESSOR-SDK-AM335X

Tool/software:

Hi , Liu, ,

I have seen a observation that when we were in process of migration of our application.

we observed that "sfdisk" was not included as a part of pacakge.. later when we included "linux-utils" to our image we are able to get sfdisk commad or utility? mau i know whu this improvement ?

also may i know what are the utilities are there like sfdisk as mentioned above?

It helps a lot for further debuging on this migration actvities

  • Hi Manu,

    I am missing some background here. Do you refer to some Yocto recipe? Any file system definition or recipes are most likely not a TI definition or decision. We work with the community on this and many packages in Linux that may contain multiple programs are not maintained by TI. So I am not sure we can answer such questions in any detail. For "utilities like sfdisk" could you please be more specific what you are looking for? Linux apps space is really huge. I assume there are a lot better forums and email lists for Linux tools than the TI one :-). That is the beauty of Linux, you have such a wide selection of SW that you can use on many (embedded) platforms. Even if the HW vendor doesn't know anything about them.

    Regards, Frank

  • Yes, intention to ask the above query is that.. in latest TISDK we are not able to see eMMC device file like mmcblk1p1, mmcblk1p2 , mmcblk1p3  in /dev directory.. 

    but in case of earlier TISDK(8.2) we are able to see the above mmcblk1p1. etc entries.

    in u-boot i am able to access and read emmc.. but in kernel RFS we are not able to see above mmcblk1p1 entries..

  • Hi Manu,

    but that is a a totally different topic... if you see a change between SDKs (assuming same HW and test) it is most likely a change in configuration. Did you compare the kernel device tree config? How does the HW look like that your are testing?

    On our side we would need to check what has changed. But it may require a new thread to get the right people involved.

    Regards, Frank

  • OK, please check from your end.

    Do i need to open a new thread for furter communications ?

  • yes, please use the right question/issue and specify your HW and tested SW versions. Any logs/details will help. I will close this one.

    Regards, Frank