Hi Denys,

Thank you for the suggestions. I used the poky tag "rocko-18.0.3" and meta-ti 
"ti2018.03" to build core-image-base. Two manual steps need to be done for it 
to work:
- Manually deploy modules-am335x-evm.tgz to the target rootfs.
- Manually run "depmod" to create the module dependency database on the target. 

Questions:
1. I was under the impresstion that core-image-base will install modules to 
into rootfs automatically, but it did not do that. How do we install them on 
the rootfs automatically in the build system?
2. How do we create module dependency database in the rootfs automatically in 
the build system, not on the target?


Thank you for your help!

-----Original Message-----
From: Denys Dmytriyenko [mailto:[email protected]] 
Sent: Wednesday, September 26, 2018 12:35 PM
To: Tsai, Matt <[email protected]>
Cc: Leo Meza <[email protected]>; [email protected]
Subject: Re: [meta-ti] Poky and meta-ti advice for Beaglebone Black

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


On Wed, Sep 26, 2018 at 06:27:10PM +0000, Tsai, Matt wrote:
> Leo,
>
> Thanks for sharing the experience.
> Questions:
>
>   1.  Do you set MACHINE ?= “am3335x-evm” in local.conf and build
>   core-image-minimal? Or other image target is used?

Don't use core-image-minimal - it won't install modules or DTBs into rootfs 
automatically. You'd have to install those manually. Or use at least 
core-image-base or some custom image.


>   2.  Do you have to modify anything to make Linux OS (not bootloader)
>   Ethernet and USB to work?

Shouldn't need to.


> I used poky tag “sumo-19.0.0” and meta-ti tag “ti2018.02” and set 
> MACHINE ?= “beaglebone” to build core-image-minimal.

Please use matching branches - i.e. "rocko" from all branches.
There were recent reports that "beaglebone" machine had some boot issues.
Use "am335x-evm" instead - it does support Beaglebone.


> The USB host does not work. I  wonder if I am using a good base to 
> start with.

Check if you have corresponding modules installed and loaded.


> Also, a question about the Linux kernel 
> meta-ti/recipes-kernel/linux/linux-ti-staging-4.14/defconfig content:
> The original in “ti2018.02” tag is “use-tisdk-config= ti_sdk_omap2_release”.
> But I also see people changing it to “use-tisdk-config= 
> ti_sdk_am3x_release”. I tried both, but USB host working. So I wonder 
> what is the correct one to use?

The defconfig is being selected based on the machine you build for. When 
building "am335x-evm" or "beaglebone", the defconfig with ti_sdk_am3x_release 
is used.


> Thank you for your help!
>
>
> From: Leo Meza [mailto:[email protected]]
> Sent: Wednesday, September 26, 2018 6:28 AM
> To: Tsai, Matt <[email protected]>
> Cc: [email protected]
> Subject: Re: [meta-ti] Poky and meta-ti advice for Beaglebone Black
>
> CAUTION: This email originated from outside of the organization. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe.
>
> Matt,
>
> I've been having some success with the "rocko" branches (meta-ti, etc), and 
> using the "am335x-evm" machine for beaglebone black.
>
> I haven't done any i2c yet, but Ethernet and USB are working fine. I'm still 
> on the left of the learning curve though, maybe someone else on this thread 
> has better advice.
>
> -Leo
>
> On Tue, Sep 25, 2018, 4:19 PM Tsai, Matt 
> <[email protected]<mailto:[email protected]>> wrote:
> Hi all,
>
> I am new to Yocto and was trying to use poky and meta-ti to customize Linux 
> to run on Beaglebone Black. There are a couple of questions I encountered, 
> hopefully I can get some advice here:
>
>   1.  What is the recommended poky and meta-ti branch/tag to use?
>   2.  If we need to enable some common device support such as Ethernet, USB 
> host port, I2C, …etc., what do we need to modify on these recommended poky 
> and meta-ti software?
>
> Thank you for your help!
>
> --
> _______________________________________________
> meta-ti mailing list
> [email protected]<mailto:[email protected]>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoprojec
> t.org_listinfo_meta-2Dti&d=DwIDaQ&c=q6k2DsTcEGCcCb_WtVSz6hhIl8hvYssy7s
> H8ZwfbbKU&r=LfbDghM-XW_5RT-h77pAoNBiz4zBr-sjgQI-UHuV1XU&m=ztoRzwEqUnXT
> _d_hVm6COtAO29iQxsRzicIHGlpZGLI&s=4Rm9NIgBG62W0AEvKqKwgfSKpEBTN5skKehV
> -26-zZs&e=<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> yoctoproject.org_listinfo_meta-2Dti&d=DwMFaQ&c=q6k2DsTcEGCcCb_WtVSz6hh
> Il8hvYssy7sH8ZwfbbKU&r=LfbDghM-XW_5RT-h77pAoNBiz4zBr-sjgQI-UHuV1XU&m=U
> uF_TrnC3fiw_PH3rBROKHlrXnfbfuQsyAh86iV9mU8&s=CNQxEhuNF6ot6MXd-CTbz-U3Z
> LFsc_vqgRx_lnW3HkM&e=>

> --
> _______________________________________________
> meta-ti mailing list
> [email protected]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoprojec
> t.org_listinfo_meta-2Dti&d=DwIDaQ&c=q6k2DsTcEGCcCb_WtVSz6hhIl8hvYssy7s
> H8ZwfbbKU&r=LfbDghM-XW_5RT-h77pAoNBiz4zBr-sjgQI-UHuV1XU&m=ztoRzwEqUnXT
> _d_hVm6COtAO29iQxsRzicIHGlpZGLI&s=4Rm9NIgBG62W0AEvKqKwgfSKpEBTN5skKehV
> -26-zZs&e=

-- 
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

Reply via email to