Forums » Software Development »
Network Communication MitySOM Custom Kernel Configuration
Added by Brian Wentworth over 8 years ago
Hello,
I have a MitySOM dev board with the 5CSE-H4-3YA. I am able to use the pre-built binary SD card image for network communication using Firefox Copper with udp COAP packets. The program has no problem identifying the host IP information and i can read the data and process accordingly.. My problem is that I need to add serial uarts to the build and must compile a new kernel to handle the uarts with the .dtb. So, as soon as I add the new compiled kernel (compiled as shown on your "Building Linux Kernel", just enabling uarts in the menu config) I can no longer send and receive packets from Firefox Copper running the same program,.. no context available for interface"::". Seems the board cannot resolve the client IP address. Is there a configuration in the kernel build that needs to be checked that will allow this (Something you check that is not checked on the base configuration)?? Like I say, the uImage that comes with the dev kit works just fine. Attached is the Linux boot that I get from the custom build.
Thanks,
Brian
| Booting_CustomKernel (11.2 KB) Booting_CustomKernel |
Replies (6)
RE: Network Communication MitySOM Custom Kernel Configuration - Added by Jonathan Cormier over 8 years ago
Can you post your .config file?
Thanks
Jonathan Cormier
RE: Network Communication MitySOM Custom Kernel Configuration - Added by Brian Wentworth over 8 years ago
I have both the L2_3Y8 and H4_3YA.. Attached is the config file for my 3YA. Dont think it really matters. Both error with the Firefox COAP.
Thanks for the help,
Brian
| BJD.config (73.8 KB) BJD.config |
RE: Network Communication MitySOM Custom Kernel Configuration - Added by Brian Wentworth over 8 years ago
Jonathan,
So I built a new kernel setting the base configuration as mitysom5csx_devkit_defconfig without doing the menuconfig and building the uImage. Then I added that uImage to the /boot folder in the rootfs that is on the SD image that Critical Link supplies. Booting this freshly compiled uImage causes my test network program to crash. Then changing the environment to revert back and boot the uImage-3.16.0-g2067793 that comes with the card, my test program works fine.
I see an rpcbind error with the custom kernel (Starting rpcbind daemon...rpcbind: cannot create socket for udp6
rpcbind: cannot create socket for tcp6)
And my test program crashes with the following error (Nov 08 01:08:32 EMRG coap_new_context: socket no context available for interface '::')
Attached is the boot log that shows these errors. Take a look and see of anything sticks out.
Thanks,
Brian
| ScripErrorMesg.txt (1.4 KB) ScripErrorMesg.txt |
RE: Network Communication MitySOM Custom Kernel Configuration - Added by Jonathan Cormier over 8 years ago
Both udp6/tcp6 and '::' points to an error with ipv6 support. Looking at your .config file shows ipv6 being built as a module (CONFIG_IPV6=m). If you either build ipv6 support into your kernel or insert the kernel module and see if this solves the crash?
RE: Network Communication MitySOM Custom Kernel Configuration - Added by Daniel Vincelette over 8 years ago
Hi Brian,
I've updated the wiki for building the kernel and have added steps for building the modules, it can be found here: https://support.criticallink.com/redmine/projects/mityarm-5cs/wiki/Linux_Kernel
The steps at the bottom (steps 10-12) are for dealing with the kernel modules.
We do have IPV6 setup as a module so you'll need to build and copy over the modules when you rebuild the kernel. Or as Jon suggested you could change IPV6 to be built into your kernel so you won't need to deal with the modules.
Dan
RE: Network Communication MitySOM Custom Kernel Configuration - Added by Brian Wentworth over 8 years ago
Jonathan/Dan,
Solved.... Yes, that was the difference in the two kernels, ipv6 was being built as a module in the custom. Changed to be built into kernel and all works as expected. Thanks for the support.
Brian
