AnsweredAssumed Answered

Patched J1939 header files don't show up in SDK

Question asked by Craig Denson on Jun 2, 2014
Latest reply on Jun 11, 2014 by Craig Denson

We applied the J1939 patch for socketCAN which builds just fine, and the built kernel announces can J1939 SAE support at bootup. but when we build the sdk, using bitbake image -c populate_sdk, the modified kernel headers are NOT in .../usr/include/linux. We're currently building a 3.0.35 kernel, but it appears that the recipe for linux-libc-headers ignores whatever header files you've got in the linux-imx build and fetches the headers from source.

 

I've floundered around looking at how to get this to work, but if anyone knows how to get patched kernel headers into the sdk, I'd be much obliged.

 

After reading the Yocto docs and searching gmane.linux.embedded.yocto.meta-freescale, it seems like bitbake <image> -c populate_sdk should do what I want, but it doesn't.

 

"Use bitbake <image> -c populate_sdk. This method has significant advantages over the previous method because it results in a toolchain installer that contains the sysroot that matches your target root filesystem. "

 

I tested bitbake meta-toolchain and that gives me similar results.  Based on comments on the gmane mailing list from OtavioSalvador and others, it seems as though this is intentional, but to me it seems entirely wrong. I haven't tried the ADT installer method, but have little hope that will give different results.

 

Thanks,

Craig

Outcomes