Hello Community,
First a bit of background:
I am a Google Summer of Code'18 student working on Bosch BME680 sensor
https://summerofcode.withgoogle.com/projects/#6691473790074880
The driver has been merged by Jonathan Cameron(IIO subsytem maintainer &
secondary mentor) recently:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?h=testing&id=1b3bd8592780c87c5eddabbe98666b086bbaee36
But somehow it won't land up the recent kernel release since probably
merge window is next week. So, it will be in mainline kernel after the merge
window closes.
Anyway, I want to test my driver on BeagleBone Black Wireless:
debian@beaglebone:~$ uname -a
Linux beaglebone 4.14.49-ti-r54 #1 SMP PREEMPT Fri Jun 15 22:14:13 UTC 2018 armv7l GNU/Linux
So, I referred few articles online explaining different stuff and found
one suitable enough:
http://www.cs.sfu.ca/CourseCentral/433/bfraser/other/DriverCreationGuide.pdf
But the problem is that it involves a lot of complexity using USB-TTL
cable and wants:
3.1 Supported Connections:
To perform these steps, you need both:
1. A TTL serial connection to the target (such as through the Zen Cape’s
TTL over USB conection, or a separate USB to TTL cable).
2. A real Ethernet connection between the host and the target.
...
..
* It is not possible to use Ethernet over USB (passthroguh) for working
with UBoot.
How would I solve such a problem since BBBW doesn't have a
dedicated ethernet port ?
Isn't there some easy to follow guide ? Like simplying copying those
zimage & dtb directly like we do for mass-storage or tftp is also fine
while tinkering uBoot.txt/uEnv.txt perhaps ?
Aside from that, I also would need other drivers working in the same
current state and not just a 'minimal' support since I would be using
python bindings of
libiio(https://wiki.analog.com/resources/tools-software/linux-software/libiio)
to demonstrate the sensor readings with various live gaphs of the
temperature, pressure, humidity & gas channel present in the sensor.
So, I would need the BBBW to work and support as it is working
now!
Lastly, the driver involved some heavy 64 bit mulitiplications and
divisions(div64_s64) so in order to disasseble object files through
gdb would CONFIG_DEBUG_INFO = y suffice ?
Would definitely love it see how 64bit math works on 32bit environment.
PS: although you wouldn't care but I would like to tell you that I
tested my driver using https://diolan.com/dln-2 adapter under my QEMU
testing ennvironment. So, that was really easy!
Pass the kernel image & .ko files(of my driver only) to QEMU, or better
to make symbolic links and rest everything is fine.
Thanks