Building Kernel Modules Fails on 4.4.59 For GadgetFS

[mta....@gmail.com]

Hello,

I am using a BeagleBone Black with the following kernel version that I build and installed from here: https://github.com/RobertCNelson/bb-kernel/tree/am33x-v4.4

After building the kernel, which resulted in the following deb files:

linux-firmware-image-4.4.59-bone17_1cross_armhf.deb  linux-headers-4.4.59-bone17_1cross_armhf.deb  linux-image-4.4.59-bone17_1cross_armhf.deb  linux-libc-dev_1cross_armhf.deb

I installed the resulting .deb files on my BeagleBone Black  by running

sudo dpkg -i *.deb

and am now running the following kernel:

Linux beaglebone 4.4.59-bone17 #1 Thu Apr 6 13:05:33 EDT 2017 armv7l GNU/Linux

I have the following Makefile that I am using to attempt to patch the GadgetFS driver as instructed here: https://github.com/nccgroup/umap2/tree/master/gadget

ccflags-y := -I$(srctree)/drivers/usb/gadget/
ccflags-y += -I$(srctree)/drivers/usb/gadget/udc/
ccflags-y += -I$(srctree)/drivers/usb/gadget/function/


#
# We need this trick to set the name of the module to
# gadgetfs and not inode
#
obj-m+=gadgetfs.o
gadgetfs-objs=inode.o
codepath=/lib/modules/$(shell uname -r)/build/
aux=
modules:
    make $(aux) -C $(codepath) M=$(PWD) modules
clean:
    make $(aux) -C $(codepath) M=$(PWD) clean

When I attempt to run make modules, I get the following error:

debian@beaglebone:~/test/umap2/gadget$ sudo make modules
make  -C /lib/modules/4.4.59-bone17/build/ M= modules
make[1]: Entering directory '/usr/src/linux-headers-4.4.59-bone17'
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
make[2]: *** No rule to make target 'arch/arm/tools/gen-mach-types', needed by 'include/generated/mach-types.h'.  Stop.
arch/arm/Makefile:313: recipe for target 'archprepare' failed
make[1]: *** [archprepare] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.4.59-bone17'
Makefile:19: recipe for target 'modules' failed
make: *** [modules] Error 2

I am certain that there is some sort of configuration error on my part and I have been hunting for a solution for some time now. Does anyone have any ideas or recommendations for what I need to do in order to get these modules to build properly?