Howto.crosscompile for parrot drones - Revision history

Openuas: /* About */

2021-05-06T07:53:31Z

About

← Older revision		Revision as of 01:53, 6 May 2021
Line 1:		Line 1:
	=About=		=About=

	On this page you find one way to compile the drivers for a Parrot Bebop,Bebop2,Disco ~~or maybe even the nice Anafi~~.		On this page you find one way to '''compile the device drivers''' for a Parrot Bebop,Bebop2,Disco.
	~~Could well work~~ for ~~other~~ Parrot mini drones ~~also~~ with ~~maybe~~ slight modifications.		Works for Parrot mini drones like the Mambo and Swing as well with slight modifications.

			'''This is not the page for you''' if you only need to fly a Parrot Drone, in that case just follow regular instructions.

	For this to work, remember that there are many ways to Rome... This is just one.		For this to work, remember that there are many ways to Rome... This is just one.

2021-02-09T15:55:23Z

← Older revision		Revision as of 09:55, 9 February 2021
Line 18:		Line 18:
	=Install a Virtual machine=		=Install a Virtual machine=

	Use the ISO of Debian 7 32-bit this worked, find e.g. here https://cdimage.debian.org/cdimage/archive/7.11.0/i386/iso-dvd/ ~~but~~ a network install ~~also worked~~		Use the ISO of Debian 7 32-bit this worked, find e.g. here https://cdimage.debian.org/cdimage/archive/7.11.0/i386/iso-dvd/ , a network install might not work when the LTS period is over.

	==Guest additions==		==Guest additions==

2020-04-19T12:57:42Z

Mali

← Older revision		Revision as of 06:57, 19 April 2020
Line 181:		Line 181:

	==Mali==		==Mali==
	to prevent errors like '/bin/sh: line 0: cd: /drivers/parrot/gpu/mali400: No such file or directory' while compiling, create symlink (stupid, but works)		to prevent errors like '/bin/sh: line 0: cd: /drivers/parrot/gpu/mali400: No such file or directory' while compiling, create symlink (stupid way to do things, but a quick and dirty solution that works...)

	Where you have to change the path to where you copier your source files ofcourse. So for a developer ~~whou~~ stores all its code in a ~/develop directory and ~~want~~ to compile for ~~Disco~~ steps would like:		Where you have to change the path to where you copier your source files ofcourse. So for a developer who stores all its code in a ~/develop directory and wants to compile for e.g. Bebop2 steps would like:

	$ su		$ su
	# cd /		# cd /
	# ln -s /home/yourusername/develop/~~disco~~-opensource/sources/linux-3.4.11/linux-3.4.11/drivers drivers		# ln -s /home/yourusername/develop/bebop2-opensource/sources/linux-3.4.11/linux-3.4.11/drivers drivers

	=Config=		=Config=

2020-04-19T12:55:12Z

Mali

← Older revision		Revision as of 06:55, 19 April 2020
Line 187:		Line 187:
	$ su		$ su
	# cd /		# cd /
	# ln -s /home/~~$USER~~/develop/disco-opensource/sources/linux-3.4.11/linux-3.4.11/drivers drivers		# ln -s /home/yourusername/develop/disco-opensource/sources/linux-3.4.11/linux-3.4.11/drivers drivers

	=Config=		=Config=

2020-04-19T12:52:58Z

Mali

← Older revision		Revision as of 06:52, 19 April 2020
Line 182:		Line 182:
	==Mali==		==Mali==
	to prevent errors like '/bin/sh: line 0: cd: /drivers/parrot/gpu/mali400: No such file or directory' while compiling, create symlink (stupid, but works)		to prevent errors like '/bin/sh: line 0: cd: /drivers/parrot/gpu/mali400: No such file or directory' while compiling, create symlink (stupid, but works)

			Where you have to change the path to where you copier your source files ofcourse. So for a developer whou stores all its code in a ~/develop directory and want to compile for Disco steps would like:

	$ su		$ su
	# cd /		# cd /
	# ln -s /home/~~n3yh3hnii~~/develop/disco-opensource/sources/linux-3.4.11/linux-3.4.11/drivers drivers		# ln -s /home/$USER/develop/disco-opensource/sources/linux-3.4.11/linux-3.4.11/drivers drivers

	=Config=		=Config=

2020-04-19T12:45:19Z

Patch Parrot drivers sourcecode

@@ Line 140: / Line 140: @@
      +ccflags-y += -I$(DRIVER_DIR)/linux/license/gpl
      +#endif
   mali-y += \
      linux/mali_osk_atomics.o \
 ==changeMakefile:==

2020-04-19T12:31:05Z

← Older revision		Revision as of 06:31, 19 April 2020
Line 146:		Line 146:
	==changeMakefile:==		==changeMakefile:==

	open makefile		If you have a Disco then also change the makefile. Thus open makefile via:

	nano makefile		nano makefile

2019-02-26T08:27:44Z

Install a Virtual machine

← Older revision		Revision as of 02:27, 26 February 2019
Line 18:		Line 18:
	=Install a Virtual machine=		=Install a Virtual machine=

	Use the ISO of Debian 7 32-bit this worked,		Use the ISO of Debian 7 32-bit this worked, find e.g. here https://cdimage.debian.org/cdimage/archive/7.11.0/i386/iso-dvd/ but a network install also worked

	==Guest additions==		==Guest additions==

2019-02-26T08:26:08Z

← Older revision		Revision as of 02:26, 26 February 2019
Line 14:		Line 14:
	Install [[www.virtualbox.org \| virtual box]], we used v5.2 at the time of writing this page.		Install [[www.virtualbox.org \| virtual box]], we used v5.2 at the time of writing this page.

	Native cross-compiling 64-bit did not work for us, grrrr :(. Believe ~~us that~~ we spend ~~quite~~ an all-nighter on it. Thanks to uavpal and his disco4g hint that also his cross-compile efforts did not pan out. It did only work for ~~hime also~~ on a 32bit ~~machine~~. So yes, we admit, we are sissy boys. we gave up native ~~crosscompile~~ on 64bit ~~Linus fro~~ this Busybox one. Anyhow The way it is described, it all worked out, so let's be pragmatic for once...		Native cross-compiling 64-bit did not work for us, grrrr :(. Believe it, we spend an all-nighter on it. Thanks to uavpal and his disco4g's hint that also his cross-compile efforts did not pan out on native 64 OS. It did only work for him on a 32bit Linux OS. So yes, we admit, we are sissy boys; we gave up on native crosscompiling on 64bit Linux for this Busybox one. Anyhow The way it is described, it all worked out, so let's be pragmatic for once...

	=Install a Virtual machine=		=Install a Virtual machine=

2018-12-03T16:12:17Z

Environment

← Older revision		Revision as of 10:12, 3 December 2018
Line 170:		Line 170:
	=Environment=		=Environment=

	as root run:		as root run: (Hint: Where "yourpath" is the path where you installed your toolchain...)

	PATH=$PATH:/yourpath/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/libexec/gcc/arm-none-linux-gnueabi/4.6.3		PATH=$PATH:/yourpath/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/libexec/gcc/arm-none-linux-gnueabi/4.6.3