Re: [beagleboard] How to replace 4.4.x Linux kernel in BBB eMMC after cross compiling from source?
Thank you very much, this worked well! Please, could you tell me, what is the default make path of kernel modules? A have not found them after compilation. Dne úterý 9. ledna 2018 22:49:08 UTC+1 Dennis K napsal(a): > > Robert, > > Thanks that was just what I needed. > I have successfully rebooted the system with the new kernel. > > I did have to do some more research since I had neglected to compile and > install the modules to a folder, but I was able to get through that. > > One thing that bothers me is whether I need to do anything about the > kernel headers. > > I was wondering since I still can not access /dev/mem. > There is something locking me out that I need to find and change. > > I know that the c program that I have to access /dev/mem works since I was > able to get it to work with an older kernel but I was forced to upgrade > because with the older kernel the pru_rproc driver did not work. > > Dennis > > On Friday, January 5, 2018 at 4:08:14 PM UTC-5, RobertCNelson wrote: >> >> On Fri, Jan 5, 2018 at 2:59 PM, Dennis K >> wrote: >> > >> > I need to recompile my current Beaglebone Black Linux kernel (4.4.91) >> to set >> > CONFIG_STRICT_DEVMEM=n. >> > This will allow the use of mmap to access the SPI interface hardware >> > directly, among other things. >> > >> > So far... >> > I have loaded the latest version of arm-linux-gnueabihf gcc. >> > Cloned the latest kernel source ( >> https://github.com/beagleboard/linux/git) >> > which is currently 4.4.91. >> > Modified the kernel config options to set CONFIG_STRICT_DEVMEM=n. >> > Compiled the kernel. >> > Cloned, patched, and compiled u-boot. >> > >> > At this point the instructions that I have been following diverge and >> are >> > more concerned with creating a bootable image >> > on the SD card for testing or for replacing the entire contents of the >> eMMC >> > on the Beaglebone. >> > >> > What I want to do is replace the existing kernel on eMMC with minimal >> impact >> > to the current configuration. >> > My current filesystem is BeagleBoard.org Debian Image 2016-05-13. >> > >> > Can someone explain the process to replace the kernel on eMMC? >> >> First cat ./include/generated/utsrelease.h in your build directory: >> >> You'll see something similar like: >> >> #define UTS_RELEASE "4.14.12-4-gdb0cd0519e45" >> >> That's your Kernel Version, then just follow this: >> >> Copy zImage to /boot/vmlinuz-`Kernel Version` >> Copy *.dtb to /boot/dtbs/`Kernel Version`/ >> Copy modules to /lib/modules/`Kernel Version` >> Edit /boot/uEnv.txt and update uname_r=`Kernel Version` >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/fb9edae5-edc5-45db-bce3-c92887bb0aa7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to replace 4.4.x Linux kernel in BBB eMMC after cross compiling from source?
Thank You very much, it works well! Please, could you tell me, what is the default path of module compiling output? I have compiled kernel and modules, kernel is in ./linux/arch/arm/boot/, but I can not find .ko files anywhere... Many thanks. Dne pátek 5. ledna 2018 22:08:14 UTC+1 RobertCNelson napsal(a): > > On Fri, Jan 5, 2018 at 2:59 PM, Dennis K > wrote: > > > > I need to recompile my current Beaglebone Black Linux kernel (4.4.91) to > set > > CONFIG_STRICT_DEVMEM=n. > > This will allow the use of mmap to access the SPI interface hardware > > directly, among other things. > > > > So far... > > I have loaded the latest version of arm-linux-gnueabihf gcc. > > Cloned the latest kernel source ( > https://github.com/beagleboard/linux/git) > > which is currently 4.4.91. > > Modified the kernel config options to set CONFIG_STRICT_DEVMEM=n. > > Compiled the kernel. > > Cloned, patched, and compiled u-boot. > > > > At this point the instructions that I have been following diverge and > are > > more concerned with creating a bootable image > > on the SD card for testing or for replacing the entire contents of the > eMMC > > on the Beaglebone. > > > > What I want to do is replace the existing kernel on eMMC with minimal > impact > > to the current configuration. > > My current filesystem is BeagleBoard.org Debian Image 2016-05-13. > > > > Can someone explain the process to replace the kernel on eMMC? > > First cat ./include/generated/utsrelease.h in your build directory: > > You'll see something similar like: > > #define UTS_RELEASE "4.14.12-4-gdb0cd0519e45" > > That's your Kernel Version, then just follow this: > > Copy zImage to /boot/vmlinuz-`Kernel Version` > Copy *.dtb to /boot/dtbs/`Kernel Version`/ > Copy modules to /lib/modules/`Kernel Version` > Edit /boot/uEnv.txt and update uname_r=`Kernel Version` > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/5237fc69-9ba1-4da6-a662-207c6edce742%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to replace 4.4.x Linux kernel in BBB eMMC after cross compiling from source?
Robert, Thanks that was just what I needed. I have successfully rebooted the system with the new kernel. I did have to do some more research since I had neglected to compile and install the modules to a folder, but I was able to get through that. One thing that bothers me is whether I need to do anything about the kernel headers. I was wondering since I still can not access /dev/mem. There is something locking me out that I need to find and change. I know that the c program that I have to access /dev/mem works since I was able to get it to work with an older kernel but I was forced to upgrade because with the older kernel the pru_rproc driver did not work. Dennis On Friday, January 5, 2018 at 4:08:14 PM UTC-5, RobertCNelson wrote: > > On Fri, Jan 5, 2018 at 2:59 PM, Dennis K > wrote: > > > > I need to recompile my current Beaglebone Black Linux kernel (4.4.91) to > set > > CONFIG_STRICT_DEVMEM=n. > > This will allow the use of mmap to access the SPI interface hardware > > directly, among other things. > > > > So far... > > I have loaded the latest version of arm-linux-gnueabihf gcc. > > Cloned the latest kernel source ( > https://github.com/beagleboard/linux/git) > > which is currently 4.4.91. > > Modified the kernel config options to set CONFIG_STRICT_DEVMEM=n. > > Compiled the kernel. > > Cloned, patched, and compiled u-boot. > > > > At this point the instructions that I have been following diverge and > are > > more concerned with creating a bootable image > > on the SD card for testing or for replacing the entire contents of the > eMMC > > on the Beaglebone. > > > > What I want to do is replace the existing kernel on eMMC with minimal > impact > > to the current configuration. > > My current filesystem is BeagleBoard.org Debian Image 2016-05-13. > > > > Can someone explain the process to replace the kernel on eMMC? > > First cat ./include/generated/utsrelease.h in your build directory: > > You'll see something similar like: > > #define UTS_RELEASE "4.14.12-4-gdb0cd0519e45" > > That's your Kernel Version, then just follow this: > > Copy zImage to /boot/vmlinuz-`Kernel Version` > Copy *.dtb to /boot/dtbs/`Kernel Version`/ > Copy modules to /lib/modules/`Kernel Version` > Edit /boot/uEnv.txt and update uname_r=`Kernel Version` > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/14f0a508-f3c5-46da-9aba-fc0592436180%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to replace 4.4.x Linux kernel in BBB eMMC after cross compiling from source?
On Fri, Jan 5, 2018 at 2:59 PM, Dennis K wrote: > > I need to recompile my current Beaglebone Black Linux kernel (4.4.91) to set > CONFIG_STRICT_DEVMEM=n. > This will allow the use of mmap to access the SPI interface hardware > directly, among other things. > > So far... > I have loaded the latest version of arm-linux-gnueabihf gcc. > Cloned the latest kernel source (https://github.com/beagleboard/linux/git) > which is currently 4.4.91. > Modified the kernel config options to set CONFIG_STRICT_DEVMEM=n. > Compiled the kernel. > Cloned, patched, and compiled u-boot. > > At this point the instructions that I have been following diverge and are > more concerned with creating a bootable image > on the SD card for testing or for replacing the entire contents of the eMMC > on the Beaglebone. > > What I want to do is replace the existing kernel on eMMC with minimal impact > to the current configuration. > My current filesystem is BeagleBoard.org Debian Image 2016-05-13. > > Can someone explain the process to replace the kernel on eMMC? First cat ./include/generated/utsrelease.h in your build directory: You'll see something similar like: #define UTS_RELEASE "4.14.12-4-gdb0cd0519e45" That's your Kernel Version, then just follow this: Copy zImage to /boot/vmlinuz-`Kernel Version` Copy *.dtb to /boot/dtbs/`Kernel Version`/ Copy modules to /lib/modules/`Kernel Version` Edit /boot/uEnv.txt and update uname_r=`Kernel Version` Regards, -- Robert Nelson https://rcn-ee.com/ -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYjPP07ryvAXqLRUdvgaunnzhOTgnxX6M0MyAq%2BWKe_hiQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] How to replace 4.4.x Linux kernel in BBB eMMC after cross compiling from source?
I need to recompile my current Beaglebone Black Linux kernel (4.4.91) to set CONFIG_STRICT_DEVMEM=n. This will allow the use of mmap to access the SPI interface hardware directly, among other things. So far... I have loaded the latest version of arm-linux-gnueabihf gcc. Cloned the latest kernel source (https://github.com/beagleboard/linux/git) which is currently 4.4.91. Modified the kernel config options to set CONFIG_STRICT_DEVMEM=n. Compiled the kernel. Cloned, patched, and compiled u-boot. At this point the instructions that I have been following diverge and are more concerned with creating a bootable image on the SD card for testing or for replacing the entire contents of the eMMC on the Beaglebone. What I want to do is replace the existing kernel on eMMC with minimal impact to the current configuration. My current filesystem is BeagleBoard.org Debian Image 2016-05-13. Can someone explain the process to replace the kernel on eMMC? -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f3be046f-d8f4-4cae-ad50-0494691bb0b5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
