As a new to the small white of embedded development board, held it is really a face of meng force, have a week to understand! Original drive running really./. Bin file
First of all, is to write driver code, this is port configuration, etc., then generate. Ko file
Second is to write application code, simply is to use the port you configured to assign a value to it! Then generate. Bin file

And will in the end. Ko file. Bin files are transferred to the development board (download a variety of ways, I am using TFTP download) and then by ismod speak first. Ko file installed, then run. Bin file,

CodePudding user response:

Should not be. Bin file, suffixes can be driven. Ko, but application is generally no suffix, I is according to the newsletter for steps, is very simple

CodePudding user response:

Actually all can run files are binary data, file suffix is what not directly influence, you can use the file command to check after you compile the generated files, cross ARM compiled file such as the ELF 32 - bit LSB executable that ARM, version 1 (GNU/Linux), dynamically linked (USES Shared libs), for the GNU/Linux 3.2.0, not stripped.