Op ma 24 feb. 2020 05:03 schreef <[email protected]>: > > Hi, > > I recently purchased a beaglebone blue and tried it with pre-installed > image and the latest debian image from beagleboard.org. Everything is ok > and the wifi works perfectly. > > Now, I want to build my own custom image with buildroot. I have some > experience with buildroot and raspberry pi. I managed to have a bootable > image with linux console on uart. The problem is that when I try to > activate wlan0 (ip link set wlan0 up), the board hangs. I cannot connect > to ssh anymore (USB connection), I cannot access it via the uart linux > console (no more log from kernel), the heartbeat LED stops blinking, the > only thing i can do is ping the board (through USB). >
That sounds like a kernel panic. Is any logging of this event written to a file that you can look at after boot? Do you get any output the moment it happens? Do you have the kernel module for wlan compiled into the kernel? You might get a bit more logging if it is a module. > What I have tried so far, > > Use different firmware (/lib/firmware/ti-connectivity) from: > * Buildroot linux-firmware package > * Beaglebone Black wireless firmware (on github) > * Pre installed firmware from the official Debian image > > Use different device-tree > * am35x-boneblue.dts built with the linux kernel by buildroot > * the devicetree provided in the official Debian image > I trust you know that the device tree can be specific for a kernel. For my beaglebone black, there are huge differences between the beaglebone kernel and the stable kernel from kernel.org. I would try it as well with the beaglebone kernel and matching device tree. https://github.com/beagleboard/linux If you see that working you could backtrack where the differences are. > Use different libc > * µclibc > * glibc > I don't think that matters that much. Errors in those libraries are not that common and would probably cause more errors. Glibc is used more, so to be safe stick to that. > At this point I end up every time with the symptoms described before. > Could anyone help to investigate further? > > Thank you, > > Thomas > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/d9993f35-7307-4452-9789-be3aa5507d6e%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/d9993f35-7307-4452-9789-be3aa5507d6e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAHK0gJ3LcDYR1%2Brn_x4kcTR2NkPy7iuo%2BZAO%3DgpoMnmnytpKgQ%40mail.gmail.com.
