[meta-freescale] Issue with freescale git server at git.freescale.com

[georg]

On 18/10/2017 12:53, Otavio Salvador wrote:
> Hello Georg,
> 
> On Wed, Oct 18, 2017 at 6:14 AM, georg <g9685wd at gmail.com> wrote:
>> Hello Otavio,
>> On 17/10/2017 18:28, Otavio Salvador wrote:
>>> Hello Georg,
>>>
>>> On Tue, Oct 17, 2017 at 1:58 PM, georg <g9685wd at gmail.com> wrote:
>>>> On 16/10/2017 15:46, Otavio Salvador wrote:
>>>>> On Mon, Oct 16, 2017 at 11:05 AM, georg <g9685wd at gmail.com> wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> On Mon, Oct 16, 2017 at 6:27 AM, georg <g9685wd at gmail.com> wrote:
>>>>>>>> I have started a script this weekend which tries to do a git clone with
>>>>>>>> --mirror in a loop every hour till it succeeds. This was working, I have
>>>>>>>> now a cloned linux-imx.git repository which I can use in all future builds.
>>>>>>>>
>>>>>>>> Nonetheless it's very annoying to not be able to do a simple "bitbake
>>>>>>>> core-image-minimal" with a standard freescale evaluation board.
>>>>>>>
>>>>>>> I am curious to know which machine as we use linux-fslc-imx for most
>>>>>>> machines as default.
>>>>>>>
>>>>>> Ah, that's interesting. I thought it's the same repository for all
>>>>>> freescale processors. It's for imx6ull.
>>>>>
>>>>> If you can, test rocko and change the machine to use u-boot-fslc and
>>>>> linux-fslc-imx so we confirm it works there. If it does, we can
>>>>> change.
>>>>>
>>>> Hello,
>>>>
>>>> I have done my previous tests on master (morty doesn't support imx6ull).
>>>>
>>>> So if have tested rocko and change this file:
>>>> meta-freescale/conf/machine/imx6ullevk.conf. I have removed the
>>>> following lines:
>>>> PREFERRED_PROVIDER_u-boot = "u-boot-imx"
>>>> PREFERRED_PROVIDER_virtual/bootloader = "u-boot-imx"
>>>> PREFERRED_PROVIDER_virtual/kernel = "linux-imx"
>>>>
>>>> It seems that imx-base.inc let chose bitbake u-boot-fslc and linux-fslc-imx.
>>>> I have u-boot-fslc-v2017.09+gitAUTOINC+a6a15fedd1-r0 and
>>>> linux-fslc-imx-4.1-2.0.x+gitAUTOINC+6c1ad49339-r0 in my buildstats. So
>>>> now it's using u-boot-fslc and linux-fslc-imx.
>>>>
>>>> The download is slow too, but without connection errors. After several
>>>> hours, the kernel sources are downloaded.
>>>>
>>>> The build is successful, but boot sucks. U-boot boots correctly, but not
>>>> linux. I have a reboot without any kernel trace near the end of the
>>>> boot, like that:
>>>>
>>>>> Configuring network interfaces... fec 20b4000.ethernet eth0: Freescale
>>>>> FEC PHY driver [Micrel KSZ8081 or KSZ8091]
>>>>> (mii_bus:phy_addr=20b4000.ethernet:01, irq=-1)
>>>>> IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>>>>> udhcpc (v1.24.1) started
>>>>> Sending discover...
>>>>> Sending discover...
>>>>> fec 20b4000.ethernet eth0: Link is Up - 100Mbps/Full - flow control >rx/tx
>>>>> IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>>>>> Sending discover...
>>>>>
>>>>>
>>>>> U-Boot 2017.09+fslc+ga6a15fe (Oct 17 2017 - 13:56:43 +0200)
>>>>
>>>> I have no idea why. There is no kernel crash trace so it's perhaps
>>>> something like the watchdog.
>>>
>>> Thanks for running the tests.
>>>
>>> I did look about differences and you did test against kernel 4.9 it seems.
>>>
>>> I'd like to know if you can run same test but against linux-fslc (it
>>> uses 4.13 mainline). Is it possible?
>>>
>>
>> I have already seen in the release-notes that there are many different
>> kernel versions. It's not obvious to me which version to use for my
>> future project. I think mainline kernel is better for latest bugfixes.
>> Is my listing of kernels from freescale to mainline at the rate of
>> changes to mainline correct?:
>>  * linux-imx
>>  * linux-fslc-imx
>>  * linux-fslc
>>  * mainline
>> Thats just to know why this two version exist (linux-fslc-imx and
>> linux-fslc).
> 
> Basically:
> 
>  linux-imx: NXP Linux kernel fork
>  linux-fslc-imx: NXP Linux kernel fork plus FSLC changes (and stable
> releases merged)
>  linux-fslc: Mainline Linux kernel fork with FSLC chages
> 
>> For the test I have added the following lines to  machine/imx6ullevk.conf:
>>
>> PREFERRED_PROVIDER_virtual/kernel = "linux-fslc"
>> PREFERRED_PROVIDER_kernel = "linux-fslc"
>>
>> Not sure if the .._virtual... line is needed but it seems to use the
>> right kernel version. I get my log in:
>> build/tmp/work/imx6ullevk-poky-linux-gnueabi/linux-fslc/4.13+gitAUTOINC+e12ac43313-r0/temp/log.do_compile.30043
> 
> Right, please remove the dtb from KERNEL_DEVICETREE list so we can
> make sure it  all works ;-)

I didn't notice that this is coming form the machine configuration file.
I have remove it, the build works now.
But the boot don't, I have the same behavior as with the other kernel.
Near the end of the boot process, it restarts without any kernel trace
indicating a problem.

> 
>> I get the following compilation error:
>>
>> | make[3]: *** No rule to make target
>> 'arch/arm/boot/dts/imx6ull-14x14-evk-btwifi.dtb'.  Stop.
>> | arch/arm/Makefile:341: recipe for target
>> 'imx6ull-14x14-evk-btwifi.dtb' failed
>> | make[2]: *** [imx6ull-14x14-evk-btwifi.dtb] Error 2
>> | Makefile:145: recipe for target 'sub-make' failed
>> | make[1]: *** [sub-make] Error 2
>> | Makefile:24: recipe for target '__sub-make' failed
>> | make: *** [__sub-make] Error 2
>> | ERROR: oe_runmake failed
>>
>> It seems that imx6ull-14x14-evk-btwifi.dtb is missing.
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
> 
> 
>