├── LICENSE
├── README.md
├── Yocto_Linux.md
├── Yocto_STM32MP157F-DK2_Linux_Image.pdf
├── cross_compile.txt
├── fdcan.md
├── images
├── STM32MP157F-DK2_board.png
└── stm32mp1_ethernet_and_can.png
├── qt5_on_stm32mp1.md
├── stm32mp1_sdk_check.sh
└── yocto.txt
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 3, 29 June 2007
3 |
4 | Copyright (C) 2007 Free Software Foundation, Inc.
5 | Everyone is permitted to copy and distribute verbatim copies
6 | of this license document, but changing it is not allowed.
7 |
8 | Preamble
9 |
10 | The GNU General Public License is a free, copyleft license for
11 | software and other kinds of works.
12 |
13 | The licenses for most software and other practical works are designed
14 | to take away your freedom to share and change the works. By contrast,
15 | the GNU General Public License is intended to guarantee your freedom to
16 | share and change all versions of a program--to make sure it remains free
17 | software for all its users. We, the Free Software Foundation, use the
18 | GNU General Public License for most of our software; it applies also to
19 | any other work released this way by its authors. You can apply it to
20 | your programs, too.
21 |
22 | When we speak of free software, we are referring to freedom, not
23 | price. Our General Public Licenses are designed to make sure that you
24 | have the freedom to distribute copies of free software (and charge for
25 | them if you wish), that you receive source code or can get it if you
26 | want it, that you can change the software or use pieces of it in new
27 | free programs, and that you know you can do these things.
28 |
29 | To protect your rights, we need to prevent others from denying you
30 | these rights or asking you to surrender the rights. Therefore, you have
31 | certain responsibilities if you distribute copies of the software, or if
32 | you modify it: responsibilities to respect the freedom of others.
33 |
34 | For example, if you distribute copies of such a program, whether
35 | gratis or for a fee, you must pass on to the recipients the same
36 | freedoms that you received. You must make sure that they, too, receive
37 | or can get the source code. And you must show them these terms so they
38 | know their rights.
39 |
40 | Developers that use the GNU GPL protect your rights with two steps:
41 | (1) assert copyright on the software, and (2) offer you this License
42 | giving you legal permission to copy, distribute and/or modify it.
43 |
44 | For the developers' and authors' protection, the GPL clearly explains
45 | that there is no warranty for this free software. For both users' and
46 | authors' sake, the GPL requires that modified versions be marked as
47 | changed, so that their problems will not be attributed erroneously to
48 | authors of previous versions.
49 |
50 | Some devices are designed to deny users access to install or run
51 | modified versions of the software inside them, although the manufacturer
52 | can do so. This is fundamentally incompatible with the aim of
53 | protecting users' freedom to change the software. The systematic
54 | pattern of such abuse occurs in the area of products for individuals to
55 | use, which is precisely where it is most unacceptable. Therefore, we
56 | have designed this version of the GPL to prohibit the practice for those
57 | products. If such problems arise substantially in other domains, we
58 | stand ready to extend this provision to those domains in future versions
59 | of the GPL, as needed to protect the freedom of users.
60 |
61 | Finally, every program is threatened constantly by software patents.
62 | States should not allow patents to restrict development and use of
63 | software on general-purpose computers, but in those that do, we wish to
64 | avoid the special danger that patents applied to a free program could
65 | make it effectively proprietary. To prevent this, the GPL assures that
66 | patents cannot be used to render the program non-free.
67 |
68 | The precise terms and conditions for copying, distribution and
69 | modification follow.
70 |
71 | TERMS AND CONDITIONS
72 |
73 | 0. Definitions.
74 |
75 | "This License" refers to version 3 of the GNU General Public License.
76 |
77 | "Copyright" also means copyright-like laws that apply to other kinds of
78 | works, such as semiconductor masks.
79 |
80 | "The Program" refers to any copyrightable work licensed under this
81 | License. Each licensee is addressed as "you". "Licensees" and
82 | "recipients" may be individuals or organizations.
83 |
84 | To "modify" a work means to copy from or adapt all or part of the work
85 | in a fashion requiring copyright permission, other than the making of an
86 | exact copy. The resulting work is called a "modified version" of the
87 | earlier work or a work "based on" the earlier work.
88 |
89 | A "covered work" means either the unmodified Program or a work based
90 | on the Program.
91 |
92 | To "propagate" a work means to do anything with it that, without
93 | permission, would make you directly or secondarily liable for
94 | infringement under applicable copyright law, except executing it on a
95 | computer or modifying a private copy. Propagation includes copying,
96 | distribution (with or without modification), making available to the
97 | public, and in some countries other activities as well.
98 |
99 | To "convey" a work means any kind of propagation that enables other
100 | parties to make or receive copies. Mere interaction with a user through
101 | a computer network, with no transfer of a copy, is not conveying.
102 |
103 | An interactive user interface displays "Appropriate Legal Notices"
104 | to the extent that it includes a convenient and prominently visible
105 | feature that (1) displays an appropriate copyright notice, and (2)
106 | tells the user that there is no warranty for the work (except to the
107 | extent that warranties are provided), that licensees may convey the
108 | work under this License, and how to view a copy of this License. If
109 | the interface presents a list of user commands or options, such as a
110 | menu, a prominent item in the list meets this criterion.
111 |
112 | 1. Source Code.
113 |
114 | The "source code" for a work means the preferred form of the work
115 | for making modifications to it. "Object code" means any non-source
116 | form of a work.
117 |
118 | A "Standard Interface" means an interface that either is an official
119 | standard defined by a recognized standards body, or, in the case of
120 | interfaces specified for a particular programming language, one that
121 | is widely used among developers working in that language.
122 |
123 | The "System Libraries" of an executable work include anything, other
124 | than the work as a whole, that (a) is included in the normal form of
125 | packaging a Major Component, but which is not part of that Major
126 | Component, and (b) serves only to enable use of the work with that
127 | Major Component, or to implement a Standard Interface for which an
128 | implementation is available to the public in source code form. A
129 | "Major Component", in this context, means a major essential component
130 | (kernel, window system, and so on) of the specific operating system
131 | (if any) on which the executable work runs, or a compiler used to
132 | produce the work, or an object code interpreter used to run it.
133 |
134 | The "Corresponding Source" for a work in object code form means all
135 | the source code needed to generate, install, and (for an executable
136 | work) run the object code and to modify the work, including scripts to
137 | control those activities. However, it does not include the work's
138 | System Libraries, or general-purpose tools or generally available free
139 | programs which are used unmodified in performing those activities but
140 | which are not part of the work. For example, Corresponding Source
141 | includes interface definition files associated with source files for
142 | the work, and the source code for shared libraries and dynamically
143 | linked subprograms that the work is specifically designed to require,
144 | such as by intimate data communication or control flow between those
145 | subprograms and other parts of the work.
146 |
147 | The Corresponding Source need not include anything that users
148 | can regenerate automatically from other parts of the Corresponding
149 | Source.
150 |
151 | The Corresponding Source for a work in source code form is that
152 | same work.
153 |
154 | 2. Basic Permissions.
155 |
156 | All rights granted under this License are granted for the term of
157 | copyright on the Program, and are irrevocable provided the stated
158 | conditions are met. This License explicitly affirms your unlimited
159 | permission to run the unmodified Program. The output from running a
160 | covered work is covered by this License only if the output, given its
161 | content, constitutes a covered work. This License acknowledges your
162 | rights of fair use or other equivalent, as provided by copyright law.
163 |
164 | You may make, run and propagate covered works that you do not
165 | convey, without conditions so long as your license otherwise remains
166 | in force. You may convey covered works to others for the sole purpose
167 | of having them make modifications exclusively for you, or provide you
168 | with facilities for running those works, provided that you comply with
169 | the terms of this License in conveying all material for which you do
170 | not control copyright. Those thus making or running the covered works
171 | for you must do so exclusively on your behalf, under your direction
172 | and control, on terms that prohibit them from making any copies of
173 | your copyrighted material outside their relationship with you.
174 |
175 | Conveying under any other circumstances is permitted solely under
176 | the conditions stated below. Sublicensing is not allowed; section 10
177 | makes it unnecessary.
178 |
179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
180 |
181 | No covered work shall be deemed part of an effective technological
182 | measure under any applicable law fulfilling obligations under article
183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or
184 | similar laws prohibiting or restricting circumvention of such
185 | measures.
186 |
187 | When you convey a covered work, you waive any legal power to forbid
188 | circumvention of technological measures to the extent such circumvention
189 | is effected by exercising rights under this License with respect to
190 | the covered work, and you disclaim any intention to limit operation or
191 | modification of the work as a means of enforcing, against the work's
192 | users, your or third parties' legal rights to forbid circumvention of
193 | technological measures.
194 |
195 | 4. Conveying Verbatim Copies.
196 |
197 | You may convey verbatim copies of the Program's source code as you
198 | receive it, in any medium, provided that you conspicuously and
199 | appropriately publish on each copy an appropriate copyright notice;
200 | keep intact all notices stating that this License and any
201 | non-permissive terms added in accord with section 7 apply to the code;
202 | keep intact all notices of the absence of any warranty; and give all
203 | recipients a copy of this License along with the Program.
204 |
205 | You may charge any price or no price for each copy that you convey,
206 | and you may offer support or warranty protection for a fee.
207 |
208 | 5. Conveying Modified Source Versions.
209 |
210 | You may convey a work based on the Program, or the modifications to
211 | produce it from the Program, in the form of source code under the
212 | terms of section 4, provided that you also meet all of these conditions:
213 |
214 | a) The work must carry prominent notices stating that you modified
215 | it, and giving a relevant date.
216 |
217 | b) The work must carry prominent notices stating that it is
218 | released under this License and any conditions added under section
219 | 7. This requirement modifies the requirement in section 4 to
220 | "keep intact all notices".
221 |
222 | c) You must license the entire work, as a whole, under this
223 | License to anyone who comes into possession of a copy. This
224 | License will therefore apply, along with any applicable section 7
225 | additional terms, to the whole of the work, and all its parts,
226 | regardless of how they are packaged. This License gives no
227 | permission to license the work in any other way, but it does not
228 | invalidate such permission if you have separately received it.
229 |
230 | d) If the work has interactive user interfaces, each must display
231 | Appropriate Legal Notices; however, if the Program has interactive
232 | interfaces that do not display Appropriate Legal Notices, your
233 | work need not make them do so.
234 |
235 | A compilation of a covered work with other separate and independent
236 | works, which are not by their nature extensions of the covered work,
237 | and which are not combined with it such as to form a larger program,
238 | in or on a volume of a storage or distribution medium, is called an
239 | "aggregate" if the compilation and its resulting copyright are not
240 | used to limit the access or legal rights of the compilation's users
241 | beyond what the individual works permit. Inclusion of a covered work
242 | in an aggregate does not cause this License to apply to the other
243 | parts of the aggregate.
244 |
245 | 6. Conveying Non-Source Forms.
246 |
247 | You may convey a covered work in object code form under the terms
248 | of sections 4 and 5, provided that you also convey the
249 | machine-readable Corresponding Source under the terms of this License,
250 | in one of these ways:
251 |
252 | a) Convey the object code in, or embodied in, a physical product
253 | (including a physical distribution medium), accompanied by the
254 | Corresponding Source fixed on a durable physical medium
255 | customarily used for software interchange.
256 |
257 | b) Convey the object code in, or embodied in, a physical product
258 | (including a physical distribution medium), accompanied by a
259 | written offer, valid for at least three years and valid for as
260 | long as you offer spare parts or customer support for that product
261 | model, to give anyone who possesses the object code either (1) a
262 | copy of the Corresponding Source for all the software in the
263 | product that is covered by this License, on a durable physical
264 | medium customarily used for software interchange, for a price no
265 | more than your reasonable cost of physically performing this
266 | conveying of source, or (2) access to copy the
267 | Corresponding Source from a network server at no charge.
268 |
269 | c) Convey individual copies of the object code with a copy of the
270 | written offer to provide the Corresponding Source. This
271 | alternative is allowed only occasionally and noncommercially, and
272 | only if you received the object code with such an offer, in accord
273 | with subsection 6b.
274 |
275 | d) Convey the object code by offering access from a designated
276 | place (gratis or for a charge), and offer equivalent access to the
277 | Corresponding Source in the same way through the same place at no
278 | further charge. You need not require recipients to copy the
279 | Corresponding Source along with the object code. If the place to
280 | copy the object code is a network server, the Corresponding Source
281 | may be on a different server (operated by you or a third party)
282 | that supports equivalent copying facilities, provided you maintain
283 | clear directions next to the object code saying where to find the
284 | Corresponding Source. Regardless of what server hosts the
285 | Corresponding Source, you remain obligated to ensure that it is
286 | available for as long as needed to satisfy these requirements.
287 |
288 | e) Convey the object code using peer-to-peer transmission, provided
289 | you inform other peers where the object code and Corresponding
290 | Source of the work are being offered to the general public at no
291 | charge under subsection 6d.
292 |
293 | A separable portion of the object code, whose source code is excluded
294 | from the Corresponding Source as a System Library, need not be
295 | included in conveying the object code work.
296 |
297 | A "User Product" is either (1) a "consumer product", which means any
298 | tangible personal property which is normally used for personal, family,
299 | or household purposes, or (2) anything designed or sold for incorporation
300 | into a dwelling. In determining whether a product is a consumer product,
301 | doubtful cases shall be resolved in favor of coverage. For a particular
302 | product received by a particular user, "normally used" refers to a
303 | typical or common use of that class of product, regardless of the status
304 | of the particular user or of the way in which the particular user
305 | actually uses, or expects or is expected to use, the product. A product
306 | is a consumer product regardless of whether the product has substantial
307 | commercial, industrial or non-consumer uses, unless such uses represent
308 | the only significant mode of use of the product.
309 |
310 | "Installation Information" for a User Product means any methods,
311 | procedures, authorization keys, or other information required to install
312 | and execute modified versions of a covered work in that User Product from
313 | a modified version of its Corresponding Source. The information must
314 | suffice to ensure that the continued functioning of the modified object
315 | code is in no case prevented or interfered with solely because
316 | modification has been made.
317 |
318 | If you convey an object code work under this section in, or with, or
319 | specifically for use in, a User Product, and the conveying occurs as
320 | part of a transaction in which the right of possession and use of the
321 | User Product is transferred to the recipient in perpetuity or for a
322 | fixed term (regardless of how the transaction is characterized), the
323 | Corresponding Source conveyed under this section must be accompanied
324 | by the Installation Information. But this requirement does not apply
325 | if neither you nor any third party retains the ability to install
326 | modified object code on the User Product (for example, the work has
327 | been installed in ROM).
328 |
329 | The requirement to provide Installation Information does not include a
330 | requirement to continue to provide support service, warranty, or updates
331 | for a work that has been modified or installed by the recipient, or for
332 | the User Product in which it has been modified or installed. Access to a
333 | network may be denied when the modification itself materially and
334 | adversely affects the operation of the network or violates the rules and
335 | protocols for communication across the network.
336 |
337 | Corresponding Source conveyed, and Installation Information provided,
338 | in accord with this section must be in a format that is publicly
339 | documented (and with an implementation available to the public in
340 | source code form), and must require no special password or key for
341 | unpacking, reading or copying.
342 |
343 | 7. Additional Terms.
344 |
345 | "Additional permissions" are terms that supplement the terms of this
346 | License by making exceptions from one or more of its conditions.
347 | Additional permissions that are applicable to the entire Program shall
348 | be treated as though they were included in this License, to the extent
349 | that they are valid under applicable law. If additional permissions
350 | apply only to part of the Program, that part may be used separately
351 | under those permissions, but the entire Program remains governed by
352 | this License without regard to the additional permissions.
353 |
354 | When you convey a copy of a covered work, you may at your option
355 | remove any additional permissions from that copy, or from any part of
356 | it. (Additional permissions may be written to require their own
357 | removal in certain cases when you modify the work.) You may place
358 | additional permissions on material, added by you to a covered work,
359 | for which you have or can give appropriate copyright permission.
360 |
361 | Notwithstanding any other provision of this License, for material you
362 | add to a covered work, you may (if authorized by the copyright holders of
363 | that material) supplement the terms of this License with terms:
364 |
365 | a) Disclaiming warranty or limiting liability differently from the
366 | terms of sections 15 and 16 of this License; or
367 |
368 | b) Requiring preservation of specified reasonable legal notices or
369 | author attributions in that material or in the Appropriate Legal
370 | Notices displayed by works containing it; or
371 |
372 | c) Prohibiting misrepresentation of the origin of that material, or
373 | requiring that modified versions of such material be marked in
374 | reasonable ways as different from the original version; or
375 |
376 | d) Limiting the use for publicity purposes of names of licensors or
377 | authors of the material; or
378 |
379 | e) Declining to grant rights under trademark law for use of some
380 | trade names, trademarks, or service marks; or
381 |
382 | f) Requiring indemnification of licensors and authors of that
383 | material by anyone who conveys the material (or modified versions of
384 | it) with contractual assumptions of liability to the recipient, for
385 | any liability that these contractual assumptions directly impose on
386 | those licensors and authors.
387 |
388 | All other non-permissive additional terms are considered "further
389 | restrictions" within the meaning of section 10. If the Program as you
390 | received it, or any part of it, contains a notice stating that it is
391 | governed by this License along with a term that is a further
392 | restriction, you may remove that term. If a license document contains
393 | a further restriction but permits relicensing or conveying under this
394 | License, you may add to a covered work material governed by the terms
395 | of that license document, provided that the further restriction does
396 | not survive such relicensing or conveying.
397 |
398 | If you add terms to a covered work in accord with this section, you
399 | must place, in the relevant source files, a statement of the
400 | additional terms that apply to those files, or a notice indicating
401 | where to find the applicable terms.
402 |
403 | Additional terms, permissive or non-permissive, may be stated in the
404 | form of a separately written license, or stated as exceptions;
405 | the above requirements apply either way.
406 |
407 | 8. Termination.
408 |
409 | You may not propagate or modify a covered work except as expressly
410 | provided under this License. Any attempt otherwise to propagate or
411 | modify it is void, and will automatically terminate your rights under
412 | this License (including any patent licenses granted under the third
413 | paragraph of section 11).
414 |
415 | However, if you cease all violation of this License, then your
416 | license from a particular copyright holder is reinstated (a)
417 | provisionally, unless and until the copyright holder explicitly and
418 | finally terminates your license, and (b) permanently, if the copyright
419 | holder fails to notify you of the violation by some reasonable means
420 | prior to 60 days after the cessation.
421 |
422 | Moreover, your license from a particular copyright holder is
423 | reinstated permanently if the copyright holder notifies you of the
424 | violation by some reasonable means, this is the first time you have
425 | received notice of violation of this License (for any work) from that
426 | copyright holder, and you cure the violation prior to 30 days after
427 | your receipt of the notice.
428 |
429 | Termination of your rights under this section does not terminate the
430 | licenses of parties who have received copies or rights from you under
431 | this License. If your rights have been terminated and not permanently
432 | reinstated, you do not qualify to receive new licenses for the same
433 | material under section 10.
434 |
435 | 9. Acceptance Not Required for Having Copies.
436 |
437 | You are not required to accept this License in order to receive or
438 | run a copy of the Program. Ancillary propagation of a covered work
439 | occurring solely as a consequence of using peer-to-peer transmission
440 | to receive a copy likewise does not require acceptance. However,
441 | nothing other than this License grants you permission to propagate or
442 | modify any covered work. These actions infringe copyright if you do
443 | not accept this License. Therefore, by modifying or propagating a
444 | covered work, you indicate your acceptance of this License to do so.
445 |
446 | 10. Automatic Licensing of Downstream Recipients.
447 |
448 | Each time you convey a covered work, the recipient automatically
449 | receives a license from the original licensors, to run, modify and
450 | propagate that work, subject to this License. You are not responsible
451 | for enforcing compliance by third parties with this License.
452 |
453 | An "entity transaction" is a transaction transferring control of an
454 | organization, or substantially all assets of one, or subdividing an
455 | organization, or merging organizations. If propagation of a covered
456 | work results from an entity transaction, each party to that
457 | transaction who receives a copy of the work also receives whatever
458 | licenses to the work the party's predecessor in interest had or could
459 | give under the previous paragraph, plus a right to possession of the
460 | Corresponding Source of the work from the predecessor in interest, if
461 | the predecessor has it or can get it with reasonable efforts.
462 |
463 | You may not impose any further restrictions on the exercise of the
464 | rights granted or affirmed under this License. For example, you may
465 | not impose a license fee, royalty, or other charge for exercise of
466 | rights granted under this License, and you may not initiate litigation
467 | (including a cross-claim or counterclaim in a lawsuit) alleging that
468 | any patent claim is infringed by making, using, selling, offering for
469 | sale, or importing the Program or any portion of it.
470 |
471 | 11. Patents.
472 |
473 | A "contributor" is a copyright holder who authorizes use under this
474 | License of the Program or a work on which the Program is based. The
475 | work thus licensed is called the contributor's "contributor version".
476 |
477 | A contributor's "essential patent claims" are all patent claims
478 | owned or controlled by the contributor, whether already acquired or
479 | hereafter acquired, that would be infringed by some manner, permitted
480 | by this License, of making, using, or selling its contributor version,
481 | but do not include claims that would be infringed only as a
482 | consequence of further modification of the contributor version. For
483 | purposes of this definition, "control" includes the right to grant
484 | patent sublicenses in a manner consistent with the requirements of
485 | this License.
486 |
487 | Each contributor grants you a non-exclusive, worldwide, royalty-free
488 | patent license under the contributor's essential patent claims, to
489 | make, use, sell, offer for sale, import and otherwise run, modify and
490 | propagate the contents of its contributor version.
491 |
492 | In the following three paragraphs, a "patent license" is any express
493 | agreement or commitment, however denominated, not to enforce a patent
494 | (such as an express permission to practice a patent or covenant not to
495 | sue for patent infringement). To "grant" such a patent license to a
496 | party means to make such an agreement or commitment not to enforce a
497 | patent against the party.
498 |
499 | If you convey a covered work, knowingly relying on a patent license,
500 | and the Corresponding Source of the work is not available for anyone
501 | to copy, free of charge and under the terms of this License, through a
502 | publicly available network server or other readily accessible means,
503 | then you must either (1) cause the Corresponding Source to be so
504 | available, or (2) arrange to deprive yourself of the benefit of the
505 | patent license for this particular work, or (3) arrange, in a manner
506 | consistent with the requirements of this License, to extend the patent
507 | license to downstream recipients. "Knowingly relying" means you have
508 | actual knowledge that, but for the patent license, your conveying the
509 | covered work in a country, or your recipient's use of the covered work
510 | in a country, would infringe one or more identifiable patents in that
511 | country that you have reason to believe are valid.
512 |
513 | If, pursuant to or in connection with a single transaction or
514 | arrangement, you convey, or propagate by procuring conveyance of, a
515 | covered work, and grant a patent license to some of the parties
516 | receiving the covered work authorizing them to use, propagate, modify
517 | or convey a specific copy of the covered work, then the patent license
518 | you grant is automatically extended to all recipients of the covered
519 | work and works based on it.
520 |
521 | A patent license is "discriminatory" if it does not include within
522 | the scope of its coverage, prohibits the exercise of, or is
523 | conditioned on the non-exercise of one or more of the rights that are
524 | specifically granted under this License. You may not convey a covered
525 | work if you are a party to an arrangement with a third party that is
526 | in the business of distributing software, under which you make payment
527 | to the third party based on the extent of your activity of conveying
528 | the work, and under which the third party grants, to any of the
529 | parties who would receive the covered work from you, a discriminatory
530 | patent license (a) in connection with copies of the covered work
531 | conveyed by you (or copies made from those copies), or (b) primarily
532 | for and in connection with specific products or compilations that
533 | contain the covered work, unless you entered into that arrangement,
534 | or that patent license was granted, prior to 28 March 2007.
535 |
536 | Nothing in this License shall be construed as excluding or limiting
537 | any implied license or other defenses to infringement that may
538 | otherwise be available to you under applicable patent law.
539 |
540 | 12. No Surrender of Others' Freedom.
541 |
542 | If conditions are imposed on you (whether by court order, agreement or
543 | otherwise) that contradict the conditions of this License, they do not
544 | excuse you from the conditions of this License. If you cannot convey a
545 | covered work so as to satisfy simultaneously your obligations under this
546 | License and any other pertinent obligations, then as a consequence you may
547 | not convey it at all. For example, if you agree to terms that obligate you
548 | to collect a royalty for further conveying from those to whom you convey
549 | the Program, the only way you could satisfy both those terms and this
550 | License would be to refrain entirely from conveying the Program.
551 |
552 | 13. Use with the GNU Affero General Public License.
553 |
554 | Notwithstanding any other provision of this License, you have
555 | permission to link or combine any covered work with a work licensed
556 | under version 3 of the GNU Affero General Public License into a single
557 | combined work, and to convey the resulting work. The terms of this
558 | License will continue to apply to the part which is the covered work,
559 | but the special requirements of the GNU Affero General Public License,
560 | section 13, concerning interaction through a network will apply to the
561 | combination as such.
562 |
563 | 14. Revised Versions of this License.
564 |
565 | The Free Software Foundation may publish revised and/or new versions of
566 | the GNU General Public License from time to time. Such new versions will
567 | be similar in spirit to the present version, but may differ in detail to
568 | address new problems or concerns.
569 |
570 | Each version is given a distinguishing version number. If the
571 | Program specifies that a certain numbered version of the GNU General
572 | Public License "or any later version" applies to it, you have the
573 | option of following the terms and conditions either of that numbered
574 | version or of any later version published by the Free Software
575 | Foundation. If the Program does not specify a version number of the
576 | GNU General Public License, you may choose any version ever published
577 | by the Free Software Foundation.
578 |
579 | If the Program specifies that a proxy can decide which future
580 | versions of the GNU General Public License can be used, that proxy's
581 | public statement of acceptance of a version permanently authorizes you
582 | to choose that version for the Program.
583 |
584 | Later license versions may give you additional or different
585 | permissions. However, no additional obligations are imposed on any
586 | author or copyright holder as a result of your choosing to follow a
587 | later version.
588 |
589 | 15. Disclaimer of Warranty.
590 |
591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
599 |
600 | 16. Limitation of Liability.
601 |
602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
610 | SUCH DAMAGES.
611 |
612 | 17. Interpretation of Sections 15 and 16.
613 |
614 | If the disclaimer of warranty and limitation of liability provided
615 | above cannot be given local legal effect according to their terms,
616 | reviewing courts shall apply local law that most closely approximates
617 | an absolute waiver of all civil liability in connection with the
618 | Program, unless a warranty or assumption of liability accompanies a
619 | copy of the Program in return for a fee.
620 |
621 | END OF TERMS AND CONDITIONS
622 |
623 | How to Apply These Terms to Your New Programs
624 |
625 | If you develop a new program, and you want it to be of the greatest
626 | possible use to the public, the best way to achieve this is to make it
627 | free software which everyone can redistribute and change under these terms.
628 |
629 | To do so, attach the following notices to the program. It is safest
630 | to attach them to the start of each source file to most effectively
631 | state the exclusion of warranty; and each file should have at least
632 | the "copyright" line and a pointer to where the full notice is found.
633 |
634 |
635 | Copyright (C)
636 |
637 | This program is free software: you can redistribute it and/or modify
638 | it under the terms of the GNU General Public License as published by
639 | the Free Software Foundation, either version 3 of the License, or
640 | (at your option) any later version.
641 |
642 | This program is distributed in the hope that it will be useful,
643 | but WITHOUT ANY WARRANTY; without even the implied warranty of
644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645 | GNU General Public License for more details.
646 |
647 | You should have received a copy of the GNU General Public License
648 | along with this program. If not, see .
649 |
650 | Also add information on how to contact you by electronic and paper mail.
651 |
652 | If the program does terminal interaction, make it output a short
653 | notice like this when it starts in an interactive mode:
654 |
655 | Copyright (C)
656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657 | This is free software, and you are welcome to redistribute it
658 | under certain conditions; type `show c' for details.
659 |
660 | The hypothetical commands `show w' and `show c' should show the appropriate
661 | parts of the General Public License. Of course, your program's commands
662 | might be different; for a GUI interface, you would use an "about box".
663 |
664 | You should also get your employer (if you work as a programmer) or school,
665 | if any, to sign a "copyright disclaimer" for the program, if necessary.
666 | For more information on this, and how to apply and follow the GNU GPL, see
667 | .
668 |
669 | The GNU General Public License does not permit incorporating your program
670 | into proprietary programs. If your program is a subroutine library, you
671 | may consider it more useful to permit linking proprietary applications with
672 | the library. If this is what you want to do, use the GNU Lesser General
673 | Public License instead of this License. But first, please read
674 | .
675 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Development on STM32MP157F-DK2 board
2 |
3 | ### -> *[Jump to the tutorial](https://github.com/darkquesh/stm32mp1/blob/main/Yocto_Linux.md)*
4 |
5 | A general-purpose microprocessor portfolio enabling easy development for a broad range of applications, the [STM32MP1 series][1] is based on an Arm Cortex-A7 and Cortex-M4 cores architecture. The Cortex-A7 core provides access to open-source operating systems (Linux/Android) while the Cortex-M4 core leverages the STM32 MCU ecosystem.
6 |
7 | STM32MP157-DK2 discovery kit includes a touchscreen and also embeds up to 37 communication peripherals including 10/100M or Gigabit Ethernet, 3x USB 2.0 Host/OTG, 29x Timers and Advanced Analog.
8 |
9 | 
10 |
11 | This guide includes
12 | - How to set up Linux environment on your host computer
13 | - Build your own Linux image
14 | - Configure the kernel
15 | - Add layers and custom recipes to Linux image
16 | - Customise device tree and apply patches for peripherals including I2C and CAN-FD
17 | - Communicate over Ethernet and FDCAN simultaneously on your board
18 |
19 |
20 |
21 | ### I highly recommend you to refer to the [tutorial I have written](https://github.com/darkquesh/stm32mp1/blob/main/Yocto_Linux.md) for every essential information to begin your journey into Embedded Linux on your STM32MP157x board (also in [PDF](https://github.com/darkquesh/stm32mp1/blob/main/Yocto_STM32MP157F-DK2_Linux_Image.pdf)).
22 |
23 | #### I would be appreciated if you let me know when you come across any typo or outdated information, thanks!
24 |
25 |
26 |
27 |
28 |
29 | ## Extra Resources
30 | ### Reference of this tutorial
31 | Although a bit outdated, the Digikey's tutorial on STM32MP1 board is also quite useful (which mine is based on): [Introduction to Embedded Linux | Digikey](https://www.youtube.com/playlist?list=PLEBQazB0HUyTpoJoZecRK6PpDG31Y7RPB)
32 | ### Device tree usage
33 | https://elinux.org/Device_Tree_Usage
34 |
35 |
36 | [1]: "STM32MP1"
37 |
--------------------------------------------------------------------------------
/Yocto_Linux.md:
--------------------------------------------------------------------------------
1 | # How to Use Yocto Project to Create a Custom Linux Image
2 |
3 | ### STM32MP157F-DK2 Development Kit - Yocto kirkstone
4 | #### September 2022
5 |
6 | ## Contents
7 |
8 | - 1 [Creating a Custom Linux Image](#Creating-a-Custom-Linux-Image)
9 | - Tutorials
10 | - Required Hardware
11 | - Required Software
12 | - 1.1 Install Dependencies
13 | - 1.2 Download Layers
14 | - 1.3 Configure Build
15 | - 1.4 Configure Kernel
16 | - 1.5 Build Image
17 | - 2 [Final Image for SD Card](#Final-Image-for-SD-Card)
18 | - 2.1 Creating the Final Image
19 | - 2.2 Flashing the Image to SD Card
20 | - 3 [Testing the Image](#Testing-the-Image)
21 | - 3.1 Boot into Linux
22 | - 4 [Adding Build Tools](#Adding-Build-Tools)
23 | - 5 [Creating Custom Layer and Image](#Creating-Custom-Layer-and-Image)
24 | - 5.1 Default Image Recipes
25 | - 5.2 Create Custom Layer
26 | - 5.3 Create Custom Image
27 | - 5.4 Add Layer to Build Process
28 | - 6 [Device Tree Patches](#Device-Tree-Patches)
29 | - 6.1 Create Device Tree Patch
30 | - 6.2 Enable I2C and FDCAN
31 | - 6.3 Applying Patch to Device Tree
32 | - 6.4 Enable i2cdetect and can-utils
33 | - 7 [Building Custom Image](#Building-Custom-Image)
34 | - 7.1 Build and Flash the Custom Image
35 | - 7.2 Testing I2C and FDCAN
36 | - 7.2.1 I2C Tools and Sensor Connection
37 | - 7.2.2 FDCAN Initialisation and Loopback Test
38 | - [References](#References)
39 |
40 |
41 | # Creating a Custom Linux Image
42 |
43 | ### Tutorials
44 |
45 | - https://www.youtube.com/playlist?list=PLEBQazB0HUyTpoJoZecRK6PpDG31Y7RPB
46 | - https://www.digikey.com/en/maker/projects/intro-to-embedded-linux-part-2-yocto-project/2c08a1ad09d74f20b9844e566d332da
47 | - https://www.cocoacrumbs.com/blog/2021-10-15-building-a-linux-distro-for-the-stm32mp157f-dk2/
48 | - https://bootlin.com/blog/building-a-linux-system-for-the-stm32mp1-basic-system/
49 |
50 | ### Required Hardware
51 |
52 | - STM32MP157F-DK2 Development Kit
53 | - USB-C to USB-A power cable
54 | - Micro USB to USB-A cable for connecting to the board via terminal
55 | - A minimum of 8 GB SD card
56 | - At least 4 GB of RAM on your host PC
57 |
58 | ### Required Software
59 |
60 | You will need Linux for this project, as all of the tools we are using must be run in Linux. How-
61 | ever, the steps shown below are tested in Ubuntu 20.04 using dual-boot. While you can set up a
62 | virtual Linux machine (e.g. Oracle VM VirtualBox) to build a Linux image, it would take way
63 | longer time than installing Ubuntu natively on your PC. You may follow the tutorials given be-
64 | low for installing Ubuntu on a virtual machine or alongside another OS (like Windows).
65 |
66 | Dual-boot (_recommended_): https://www.tecmint.com/install-ubuntu-alongside-with-windows-dual-boot
67 |
68 | Virtualbox: https://itsfoss.com/install-linux-in-virtualbox
69 |
70 | Also, you should allocate more than 70 GB disk space to download and build source files
71 |
72 |
73 | ### 1.1 Install Dependencies
74 |
75 | Boot into Ubuntu on your host computer and run the following commands.
76 |
77 | ```
78 | sudo apt update
79 | sudo apt upgrade
80 | sudo apt install -y bc build-essential chrpath cpio diffstat gawk git texinfo
81 | wget gdisk python3 python3-pip gedit nano
82 | sudo apt install -y libssl-dev
83 | ```
84 | Because the Yocto Project tools rely on the "python" command, you will likely need to alias
85 | "python" to "python3". Edit your .bashrc file:
86 |
87 | ```
88 | gedit ~/.bashrc
89 | ```
90 | Scroll to the bottom and add the following to a new line
91 |
92 | ```
93 | alias python=python3
94 | ```
95 | Save and exit (’esc’ followed by entering ":wq"). Re-run the .bashrc script to update your shell:
96 |
97 | ```
98 | source ~/.bashrc
99 | ```
100 | ### 1.2 Download Layers
101 |
102 | Download the Yocto Project poky reference distribution:
103 |
104 | ```
105 | mkdir -p ~/Projects/yocto
106 | cd ~/Projects/yocto
107 | git clone https://git.yoctoproject.org/poky.git
108 | cd poky
109 | ```
110 | You will want your poky layer branch to match the branches of all other third-party layers you
111 | download (such as the STM32MP1 BSP). You can view the available poky release names here:
112 | https://wiki.yoctoproject.org/wiki/Releases. We are going to have all layers be on the "kirk-stone" branch.
113 |
114 | ```
115 | git checkout kirkstone
116 | ```
117 | Next, you will want to download the STM32MP board support package (BSP) as a separate
118 | layer:
119 |
120 |
121 | ```
122 | cd ~/Projects/yocto
123 | git clone https://github.com/STMicroelectronics/meta-st-stm32mp
124 | cd meta-st-stm32mp
125 | git checkout kirkstone
126 | ```
127 | View the readme to see what other layers are needed for this particular BSP:
128 |
129 | ```
130 | less README
131 | ```
132 | In there, you can see that we need the meta-openembedded layer. Specifically, we need the meta-oe and meta-python layers in the meta-openembedded layer. Also, install any dependencies mentioned in that file.
133 |
134 | ```
135 | cd ~/Projects/yocto
136 | git clone https://github.com/openembedded/meta-openembedded.git
137 | cd meta-openembedded
138 | git checkout kirkstone
139 | ```
140 | ### 1.3 Configure Build
141 |
142 | To start using bitbake you need to source the "oe-init-build-env" script located into poky/ directory. So you should do something like thiseverytime using bitbake:
143 |
144 | ```
145 | cd ~/Projects/yocto
146 | source poky/oe-init-build-env build-mp
147 | ```
148 | You can view the layers that will be included in the build with the following:
149 |
150 | ```
151 | bitbake-layers show-layers
152 | ```
153 | You should only have the default poky layers to start. We need to edit bblayers.conf in our build to add the necessary STM32MP BSP and dependency layers:
154 |
155 | ```
156 | gedit conf/bblayers.conf
157 | ```
158 |
159 | Update the BBLAYERS variable to be the following (change to your actual user-name):
160 |
161 | ```
162 | BBLAYERS ?= " \
163 | /home//Projects/yocto/poky/meta \
164 | /home//Projects/yocto/poky/meta-poky \
165 | /home//Projects/yocto/poky/meta-yocto-bsp \
166 | /home//Projects/yocto/meta-openembedded/meta-oe \
167 | /home//Projects/yocto/meta-openembedded/meta-python \
168 | /home//Projects/yocto/meta-st-stm32mp \
169 | "
170 | ```
171 | Save and exit. Check the layers again with:
172 |
173 | ```
174 | bitbake-layers show-layers
175 | ```
176 | You can view the available machine names and settings in∼ _/Projects/yocto/meta-st-stm32mp/conf/machine_. We will use "stm32mp1" for our build. To do this, edit local.conf:
177 |
178 | ```
179 | gedit conf/local.conf
180 | ```
181 | Change the MACHINE variable to the following (comment out the "qemu" emulator and add "stm32mp1" as the machine):
182 |
183 | ```
184 | #MACHINE ??= “qemux86-64”
185 | MACHINE = “stm32mp1”
186 | ```
187 |
188 | ### 1.4 Configure Kernel
189 |
190 | Now that your build system is set up, you can make changes to the kernel. To do that, enter:
191 |
192 | ```
193 | bitbake -c menuconfig virtual/kernel
194 | ```
195 | Note that the first time you run bitbake for a particular build, it will take some time parsing all the required metadata. This could take 15 minutes or more, depending on your host computer, so be patient. After it finishes, you should be presented with a menu.
196 |
197 | 
198 |
199 |
200 | You can change various kernel settings. However, we will leave everything at their defaults for now, so just select Exit and press ’enter’.
201 |
202 | To make kernel changes permanent whenever you modify the kernel, you should run:
203 |
204 | ```
205 | bitbake -c savedefconfig virtual/kernel
206 | ```
207 |
208 | ### 1.5 Build Image
209 |
210 | Now, it is time to actually build your image! We need to choose an image to build from various images that are supported by the default poky installation here:https://docs.yoctoproject.org/ref-manual/images.html
211 | For now, we won’t need any extra packages, so we’ll skip adding the OpenSTLinux layer and just focus on the bare minimum, which is provided by the core-image-minimal image. Once you have everything configured to your liking, just run the following command:
212 |
213 | ```
214 | bitbake core-image-minimal
215 | ```
216 | The first time you build an image with bitbake, it will likely take many hours (the first build might take around 2-3 hours). One big advantage of the Yocto Project is that it builds everything in stages and layers. If you make any changes (e.g. add a layer, change to a different image, tweak kernel settings), subsequent builds will take far less time. This speeds up development process when you are trying to add low-level support in Linux.
217 |
218 | If you want to start over (e.g. you press ’ctrl + c’ or something gets corrupted/tainted)
219 |
220 | ```
221 | bitbake -c cleanall core-image-minimal
222 | ```
223 | To clean out everything
224 |
225 | ```
226 | rm -rf tmp
227 | ```
228 | Once building is complete without any errors, you can find all of the output images in the deploy folder:
229 |
230 | ```
231 | ls tmp/deploy/images/stm32mp
232 | ```
233 |
234 | # Final Image for SD Card
235 |
236 | ### 2.1 Creating the Final Image
237 |
238 | Finally, we can begin deploying the final image and flash it to an SD card for booting the system. In most cases, booting into Linux requires several bootloader programs to run in sequence. This is known as a "boot chain" or "boot sequence". For embedded Linux, this process will often look something like this:
239 |
240 | ROM > First Stage Bootloader (FSBL) > Second Stage Bootloader (SSBL) > Kernel
241 |
242 | While it is possible to format partitions manually, there is a script that does it automatically. First, stand in the following directory:
243 |
244 | ```
245 | cd ~/Projects/yocto/build-mp1/tmp/deploy/images/stm32mp1/scripts
246 | ```
247 | A _create_sdcard_from_flashlayout.sh_ script can be found in that folder. Let us choose _FlashLayout_sdcard_stm32mp157f-dk2-extensible.tsv_ to create the image by executing this command line:
248 |
249 | ```
250 | ./create_sdcard_from_flashlayout.sh ../flashlayout_core-image-minimal/extensible/FlashLayout_sdcard_stm32mp157f-dk2-extensible.tsv
251 | ```
252 |
253 | ### 2.2 Flashing the Image to SD Card
254 |
255 | ST recommends using their STM32CubeProgrammer to flash the SD card. However, we will do things manually so you can get an idea of how to configure an SD card with the various image files.
256 |
257 | Navigate to the output directory for your images:
258 |
259 | ```
260 | cd ~/Projects/yocto/build-mp1/tmp/deploy/images/stm32mp
261 | ```
262 | From here, you can figure out which image files ST would use to flash an SD card by looking at the flashlayout_core-image-minimal/trusted/FlashLayout_sdcard_stm32mp157f-dk2-trusted.tsv file in a text editor.
263 |
264 | ```
265 | gedit flashlayout_core-image-minimal/trusted/FlashLayout_sdcard_stm32mp157f-dkc2-trusted.tsv
266 | ```
267 |
268 | 
269 |
270 | This will show you the name of the image files to use for the FSBL, metadata, SSBL, bootfs, vendorfs, rootfs and userfs.
271 |
272 | To flash the final image, plug your SD card into your host computer and check where it is mounted. We can use `sudo fdisk -l` or `lsblk` command for that.
273 |
274 | In my case, the SD card is mounted at/dev/mmcblk0.
275 |
276 | Make sure to unmount any partitions that were automounted when you plugged in the SD card. (Using sudo umount /dev/mmcblk0 or through GUI like gparted or file system).
277 | As we will be writing to the SD card, any previous data and partitions should be formatted. To do that run this line:
278 |
279 | ```
280 | sudo fdisk /dev/mmcblk0
281 | ```
282 |
283 | 
284 |
285 |
286 | In fdisk, perform the following actions:
287 |
288 |
289 | - ’p’ to view the partitions
290 | - ’d’ to delete a partition
291 | **-** Select one of the partitions
292 | **-** Repeat this process until all partitions have been deleted
293 | - If your SD card is not a GPT layout, you will need to change it to GPT.
294 | **-** Type ’p’ and look at "Disklabel type." It should say "gpt"
295 | **-** ’g’ to change the layout to GPT
296 | - ’w’ to write changes to the SD card and exit
297 |
298 | You can confirm that the changes were made by entering the `lsblk` command again.
299 |
300 | Now we can flash the SD card:
301 |
302 | ```
303 | sudo dd if =../flashlayout_core-image-minimal/extensible/../../FlashLayout_sdcard_stm32mp157f-dk2-extensible.raw of=/dev/mmcblk0 bs=8M conv=fdatasync status=progress oflag=direct
304 | ```
305 |
306 | 
307 |
308 |
309 | # Testing the Image
310 |
311 | ### 3.1 Boot into Linux
312 |
313 | Plug the SD card into the STM32MP157F-DK2 board. Connect a USB micro cable from your host computer to the ST-LINK (CN11) port on the board. On your host computer, enter the
314 | following:
315 |
316 | ```
317 | sudo apt install picocom
318 | sudo picocom -b 115200 /dev/ttyACM1
319 | ```
320 | `/ttyACM1` part might be different on your host PC, so you could also try `/ttyACM0`. If you wish to exit picocom, press [Ctrl][A] followed by [Ctrl][X].
321 |
322 | If everything went well, you should see the FSBL (TF-A) post a few lines to the console followed by the SSBL (U-Boot). U-Boot will launch the kernel, and after a few seconds, you should be presented with a login prompt. Enter "root" (no password) to gain access to Linux.
323 |
324 | 
325 |
326 |
327 | ## Adding Build Tools
328 |
329 | The core-image-minimal system is installed with minimal packages, as suggested by its name. Although it does not have any basic tools such as apt, gcc or nano package; we can add them by configuring our build.
330 |
331 | First, navigate to this directory and edit _local.conf_ :
332 |
333 | ```
334 | cd ~/Projects/yocto/build-mp1/conf
335 | gedit local.conf
336 | ```
337 |
338 | 
339 |
340 |
341 | Add the following lines:
342 |
343 | ```
344 | IMAGE_INSTALL:append = " packagegroup-core-buildessential"
345 | IMAGE_INSTALL:append = " nano"
346 | IMAGE_INSTALL:append = " apt"
347 | ```
348 | The first line will append the typical GCC build tools. The second line will add the Nano editor (in case you prefer not to work with the VI editor that is part of the minimal Linux system).
349 |
350 | Also, pay attention to syntax changes in newer versions while changing build configurations: https://docs.yoctoproject.org/next/migration-guides/migration-3.4.html
351 |
352 | Now rebuild the Linux system and flash it to an SD Card (you can follow 1.5 and 2.1). If all went well, you can now use GCC and the Nano editor natively on your STM32MP157F-DK2 board.
353 |
354 |
355 | # Creating Custom Layer and Image
356 |
357 | Until now, we built our Linux image, flashed it onto an SD card and boot into Linux on the STM32MP157F-DK2 board. In this chapter, we will walk through the process of creating your own layer in the Yocto project and using it to make changes to the Linux image. Specifically, we will expand the rootfs size (to give you more space for modules, packages, and applications).
358 |
359 | ### 5.1 Default Image Recipes
360 |
361 | The poky reference distribution comes with a main image recipe that is used during the bitbake build process in order to construct the Linux image. Up until now, we have been working with core-image-minimal as our target image. core-image-minimal inherits the core-image class recipe, which can be found here
362 |
363 | ```
364 | cd ~/Projects/yocto/poky/meta
365 | gedit classes/core-image.bbclass
366 | ```
367 | Note that it is a class recipe (.bbclass), which acts as a template for other recipes to import (or "inherit"). It assigns various packagegroups to _IMAGE_INSTALL_ , which is an important variable used to tell bitbake what things to include in our image (e.g. what modules and packages to include).
368 | Look at the core-image-minimal recipe to see what was being included in our previous builds:
369 |
370 | ```
371 | gedit recipes-core/images/core-image-minimal.bb
372 | ```
373 |
374 | 
375 |
376 |
377 | ### 5.2 Create Custom Layer
378 |
379 | One of the main advantages of the Yocto Project is its ability to pull in source material from a variety of places (git repositories, websites, local files, etc.). Most of this is accomplished by keeping files (e.g. metadata, recipes) in "layers." We previously downloaded the poky and meta-st-stm32mp board support package (BSP) layers.
380 |
381 | By creating your own layer, you can easily keep it under version control (e.g. git) so that you can easily configure custom images for future builds. This is especially important if you are creating a product and want to reproduce the full image at any time during production. All you need to do is create a build directory, include your layer (along with other required layers, such as poky and the BSP), and call "bitbake ".
382 |
383 | Start by enabling the OpenEmbedded build environment again:
384 |
385 | ```
386 | cd ~/Projects/yocto
387 | source poky/oe-init-build-env build-mp
388 | ```
389 | Then, create a custom layer that sits at the same directory level as our other layers:
390 |
391 | ```
392 | cd ~/Projects/yocto
393 | bitbake-layers create-layer meta-custom
394 | ```
395 | The "bitbake-layers" tool automatically constructs the appropriate directory structure for our layer and gives us an example recipe in `../meta-custom/recipes-example/example/example_0.1.bb`. Feel free to open and look at that example.
396 |
397 | ### 5.3 Create Custom Image
398 |
399 | Instead of using core-image-minimal, we are going to write a recipe that builds a custom image.
400 | Start by creating the following directory structure:
401 |
402 | ```
403 | cd meta-custom
404 | mkdir -p recipes-core/images
405 | ```
406 | Then, we shall copy the core-image-minimal.bb recipe to use a starting point for our custom recipe:
407 |
408 | ```
409 | cp ../poky/meta/recipes-core/images/core-image-minimal.bb
410 | recipes-core/images/custom-image.bb
411 | gedit recipes-core/images/custom-image.bb
412 | ```
413 | You may change the custom recipe to add a user and password; but we will leave it as it is for now.
414 |
415 |
416 | ### 5.4 Add Layer to Build Process
417 |
418 | We need to add our custom layer to the build process. Do that with the following:
419 |
420 | ```
421 | cd ../build-mp1/
422 | gedit conf/bblayers.conf
423 | ```
424 | Add "/home//Projects/yocto/meta-custom \" to the BBLAYERS variable.
425 |
426 | 
427 |
428 | Next, we are going to include some features to our custom image.
429 |
430 | ```
431 | cd ../build-mp1/
432 | gedit conf/local.conf
433 | ```
434 |
435 | 
436 |
437 | Make sure that _debug-tweaks_ is enabled and append this line to the configuration file:
438 |
439 | `EXTRA_IMAGE_FEATURES += "hwcodecs tools-sdk tools-debug splash ssh-server-openssh
440 | package-management"`
441 |
442 | You can view the IMAGE_FEATURES variable with the following command:
443 |
444 | 
445 |
446 | Moreover, you can check out other image features here:https://docs.yoctoproject.org/ref-manual/features.html?highlight=extra_image_features.
447 |
448 |
449 | # Device Tree Patches
450 |
451 | If you look at the [datasheet for the STM32MP157D-DK1 development board](https://www.st.com/resource/en/user_manual/um2637-discovery-kits-with-increasedfrequency-800-mhz-stm32mp157-mpus-stmicroelectronics.pdf), you can see that there are 6 I2C busses available. By default I2C ports 1 and 4 are enabled and used to control other components on the board. We want to enable port 5 (as it is broken out to the Raspberry Pi-style header on the board) and use it to communicate with a temperature sensor. SDA is on top header (CN2) pin 3 and SCL is on pin 5.
452 |
453 | 
454 |
455 | If you look at the [STM32MP157 reference manual](https://www.st.com/resource/en/reference_manual/dm00327659-stm32mp157-advanced-arm-based-32-bit-mpus-stmicroelectronics.pdf), you can see that I2C port 5 is controlled by registers starting at memory address 0x40015000.
456 |
457 | 
458 |
459 | ### 6.1 Create Device Tree Patch
460 |
461 | On your host computer, navigate to the build directory and copy the device tree source (.dts) file to a temporary working directory. Then, create a copy of the original. Open it to make changes. Feel free to look through this guide to learn more about device trees.
462 |
463 | ```
464 | cd ~/Projects/yocto/build-mp1/
465 | cp tmp/work-shared/stm32mp1/kernel-source/arch/arm/boot/dts/stm32mp157f-dk2.dts
466 | ~/Documents
467 | cd ~/Documents
468 | cp stm32mp157f-dk2.dts stm32mp157f-dk2.dts.orig
469 | gedit stm32mp157f-dk2.dts
470 | ```
471 |
472 | ### 6.2 Enable I2C and FDCAN
473 |
474 | At the bottom of the file, add the following device tree nodes in order to enable I2C5 and FD-CAN1:
475 |
476 | ```
477 | &i2c5 {
478 | pinctrl-names = "default", "sleep";
479 | pinctrl-0 = <&i2c5_pins_a>;
480 | pinctrl-1 = <&i2c5_sleep_pins_a>;
481 | i2c-scl-rising-time-ns = <185>;
482 | i2c-scl-falling-time-ns = <20>;
483 | clock-frequency = <100000>;
484 | status = "okay";
485 | };
486 |
487 | &m_can1 {
488 | pinctrl-names = "default", "sleep";
489 | pinctrl-0 = <&m_can1_pins_a>;
490 | pinctrl-1 = <&m_can1_sleep_pins_a>;
491 | status = "okay";
492 | };
493 | ```
494 |
495 | 
496 |
497 | Save and exit. Then, create a diff patch. Note the "–no-index" argument allows us to perform `git diff` on two different files that are not part of a git repository.
498 |
499 | ```
500 | git diff --no-index stm32mp157f-dk2.dts.orig stm32mp157f-dk2.dts > 0001-add-i2c5-userspace-dts.patch
501 | ```
502 | However, because bitbake expects such diff files to be part of a repository, we need to make a couple of manual changes to the file so that it will be applied to the correct file (in a particular directory structure in the working area of build-mp1/tmp/). Open the file with:
503 |
504 | ```
505 | gedit 0001-add-i2c5-userspace-dts.patch
506 | ```
507 | Change the file header so that it points to the correct file locations:
508 |
509 | ```
510 | --- a/arch/arm/boot/dts/stm32mp157f-dk2.dts
511 | +++ b/arch/arm/boot/dts/stm32mp157f-dk2.dts
512 | ```
513 |
514 | 
515 |
516 | ### 6.3 Applying Patch to Device Tree
517 |
518 | Enable our build environment and navigate to the custom layer we created earlier:
519 |
520 | ```
521 | cd ~/Projects/yocto/
522 | source poky/oe-init-build-env build-mp1/
523 | cd ../meta-custom/
524 | ```
525 |
526 | Create a directory structure for kernel recipes. The naming is important! The patch file must be in "linux/."
527 |
528 | ```
529 | mkdir -p recipes-kernel/linux/stm32mp1/
530 | ```
531 | Now, we copy our patch file:
532 |
533 | ```
534 | cp ~/Documents/0001-add-i2c5-userspace-dts.patch recipes-kernel/linux/stm32mp1/
535 | ```
536 | You can run the following to discover the name of the kernel we are working with:
537 |
538 | ```
539 | oe-pkgdata-util lookup-recipe kernel
540 | ```
541 | It should say "linux-stm32mp". In the linux/ directory, create a custom .bbappend file (which will be added to our main kernel recipe). Once again, the name is important! It must be "_version.bbappend". We can use ’%’ as the version number to be a wildcard that matches any version of that file.
542 |
543 | ```
544 | gedit recipes-kernel/linux/linux-stm32mp_%.bbappend
545 | ```
546 |
547 | In this file, add the following lines, which tell the kernel recipe to look in "this directory" (the directory containing this .bbappend file) and apply the patch to the kernel.
548 |
549 | ```
550 | FILESEXTRAPATHS_prepend := "${THISDIR}:"
551 | SRC_URI += "file://0001-add-i2c5-userspace-dts.patch"
552 | ```
553 |
554 | 
555 |
556 |
557 | ### 6.4 Enable i2cdetect and can-utils
558 |
559 | In order to send and receive CAN data, we need the _can-utils_ package. First, navigate to the following directory:
560 |
561 | ```
562 | cd ~/Projects/yocto/build-mp1/conf
563 | gedit local.conf
564 | ```
565 | Then, append these lines to the end of the file:
566 |
567 |
568 | ```
569 | IMAGE_INSTALL:append = " can-utils"
570 | IMAGE_INSTALL:append = " curl"
571 | IMAGE_INSTALL:append = " gnupg"
572 | ```
573 |
574 | Your final _local.conf_ file should look like this
575 |
576 | 
577 |
578 |
579 | To test a I2C sensor, we want to probe it on the I2C bus. The easiest way to do that is with the i2cdetect tool, which comes with busybox. However, it is not enabled by default for our image, so we need to enable it.
580 |
581 | Navigate to the build folder and bring up the busybox menuconfig screen:
582 |
583 | ```
584 | cd ../build-mp1
585 | bitbake -c menuconfig busybox
586 | ```
587 | In there, head to _Miscellaneous Utilities_ , highlight i2cdetect and the other i2c utilities, and press Y to enable. It should have an asterisk [∗] in the select box to denote that the tools will be included with busybox in the next build.
588 |
589 | 
590 |
591 | Select Exit with the arrow keys and press ’enter’ to leave that screen. Do that again to exit menuconfig. Save the configuration when asked.
592 |
593 |
594 | # Building Custom Image
595 |
596 | ### 7.1 Build and Flash the Custom Image
597 |
598 | Build the custom image:
599 |
600 | ```
601 | bitbake custom-image
602 | ```
603 |
604 | When the build process is finished, flash the image onto the SD card as discussed previously.
605 |
606 | ```
607 | cd ~/Projects/yocto/build-mp1/tmp/deploy/images/stm32mp1/scripts
608 | ./create_sdcard_from_flashlayout.sh ../flashlayout_custom-image/extensible/FlashLayout_sdcard_stm32mp157f-dk2-extensible.tsv
609 | sudo dd if =../flashlayout_custom-image/extensible/../../FlashLayout_sdcard_stm32mp157f-dk2-extensible.raw of=/dev/mmcblk0 bs=8M conv=fdatasync status=progress oflag=direct
610 | ```
611 |
612 | ### 7.2 Testing I2C and FDCAN
613 |
614 | #### 7.2.1 I2C Tools and Sensor Connection
615 |
616 | Plug the SD card into your STM32MP157F-DK2 and boot it up. Connect to the serial terminalwith the following (you may need to change ttyACM1 to some other device file):
617 |
618 | ```
619 | sudo picocom -b 115200 /dev/ttyACM1
620 | ```
621 |
622 | Log in to the board with "root" and run the following command line:
623 |
624 | ```
625 | ls -l /sys/bus/i2c/devices
626 | ```
627 |
628 | 
629 |
630 |
631 | This should show you which device files (in /dev/) are symbolically linked to i2c ports/drivers on the main processor. In my case, /dev/i2c-1 is linked to I2C-5 (address 0x40015000), which is the port we just enabled.
632 |
633 | Assuming that we have connected Waveshare MLX90640 thermal imaging camera (0x33 address) to the I2C5 pins on the board, we should be able to run the following command. Note
634 | that the bus number (1) should match the device file number.
635 |
636 | ```
637 | i2cdetect -y 1
638 | ```
639 |
640 | 
641 |
642 |
643 | If all goes well, you should see 0x33 being reported on the bus, which means you can communicate with the MLX90640!
644 |
645 | #### 7.2.2 FDCAN Initialisation and Loopback Test
646 |
647 | To communicate with the CAN-FD bus on your STM32MP157F-DK2 board, you can refer to the following tutorial: https://github.com/darkquesh/stm32mp1/blob/main/fdcan.md
648 |
649 |
650 |
651 | ## References
652 |
653 |
654 | [1] STM32MP15 Discovery kits - getting started, STMicroelectronics Wiki, https://wiki.st.com/stm32mpu/wiki/STM32MP15_Discovery_kits_-_getting_started
655 |
656 | [2] STM32MP157F-DK2 User Manual, STMicroelectronics, https://www.st.com/resource/en/user_manual/um2637-discovery-kits-with-increasedfrequency-800-mhz-stm32mp157-mpus-stmicroelectronics.pdf
657 |
658 | [3] STM32MP157F-DK2 Reference Manual, STMicroelectronics, https://www.st.com/resource/en/reference_manual/dm00327659-stm32mp157-advanced-arm-based-32-bit-mpus-stmicroelectronics.pdf
659 |
660 | [4] Yocto Project Reference Manual, Linux Foundation and Yocto Project, https://docs.yoctoproject.org/ref-manual/index.html
661 |
662 | [5] Github, https://github.com/darkquesh/stm32mp1
663 |
--------------------------------------------------------------------------------
/Yocto_STM32MP157F-DK2_Linux_Image.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/darkquesh/stm32mp1/beb0edeec6de1dd81f5c4cbf23f8c35776a58a30/Yocto_STM32MP157F-DK2_Linux_Image.pdf
--------------------------------------------------------------------------------
/cross_compile.txt:
--------------------------------------------------------------------------------
1 | arm-ostl-linux-gnueabi-gcc -o gtk_hello_world gtk_hello_world.c `pkg-config --cflags gtk+-3.0` `pkg-config --libs gtk+-3.0`
2 |
3 | arm-ostl-linux-gnueabi-gcc -I/home/STM32MPU_workspace/STM32MP1-Ecosystem-v4.0.0/Developer-Package/sysroots/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/usr/include -I./include -I/usr/include -o gtk_hello_world gtk_hello_world.c `pkg-config --cflags gtk+-3.0` `pkg-config --libs gtk+-3.0`
4 |
5 |
6 | # No error
7 |
8 | arm-ostl-linux-gnueabi-gcc --sysroot=/home/STM32MPU_workspace/STM32MP1-Ecosystem-v4.0.0/Developer-Package/sysroots/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/ -o gtk_hello_world gtk_hello_world.c `pkg-config --cflags gtk+-3.0` `pkg-config --libs gtk+-3.0` -mfloat-abi=hard -mfpu=fpv4-sp-d16
9 |
10 |
11 | # Disable martian source logging when ethernet is connected:
12 | echo 0 > /proc/sys/net/ipv4/conf/{all,default}/log_martians
13 |
14 | # DO NOT run GTK application with root; instead use weston (local) as given below
15 | cd /usr/local/
16 | su -l weston -c "/usr/local/gtk_hello_world"
17 |
--------------------------------------------------------------------------------
/fdcan.md:
--------------------------------------------------------------------------------
1 | # How to set up FDCAN on STM32MP157F-DK2 and communicate over Ethernet simultaneously
2 |
3 | ## TUTORIALS
4 | 1. https://wiki.st.com/stm32mpu/wiki/How_to_set_up_a_SocketCAN_interface
5 | 2. https://wiki.st.com/stm32mpu/wiki/How_to_send_or_receive_CAN_data
6 |
7 | ## TROUBLESHOOTING
8 | #### If ip link/iplink gives an error like
9 | > ip: either "dev" is duplicate, or "type" is garbage
10 |
11 | cd ../build-mp1
12 | bitbake -c menuconfig busybox
13 | #### Under Networking Utilities enable *iproute* and check these websites:
14 | http://www.armadeus.org/wiki/index.php?title=CAN_bus_Linux_driver
15 | https://developer.ridgerun.com/wiki/index.php/How_to_configure_and_use_CAN_bus
16 |
17 |
18 |
19 | ### 0. Activate CAN driver in kernel configuration (enabled by default)
20 |
21 | `cd ~/Projects/yocto/build-mp1`
22 | `bitbake -c menuconfig virtual/kernel`
23 |
24 | > [\*] Networking support --->
25 | > <\*> CAN bus subsystem support --->
26 | > CAN Device Drivers --->
27 | > <\*> Bosch M_CAN support
28 | > <\*> Bosch M_CAN support for io-mapped devices
29 |
30 |
31 |
32 | ### 1. First, install the required stuff
33 |
34 | `cd ~/Projects/yocto/build-mp1/conf`
35 | `gedit local.conf`
36 |
37 | #### Add the following line to local.conf for sending/receiving CAN data
38 |
39 | IMAGE_INSTALL:append = " can-utils"
40 | #### Rebuild the image, flash it onto an SD card and boot the system
41 |
42 |
43 |
44 | ### 2. Check the available CAN devices
45 |
46 | `ls /sys/class/net`
47 | `ifconfig -a`
48 |
49 |
50 |
51 | ### 3. Configure the available SocketCAN interface
52 |
53 | `ip link set can0 type can bitrate 1000000 dbitrate 2000000 fd on`
54 |
55 | #### Print the status of the SocketCAN link
56 |
57 | `ip -details link show can0`
58 |
59 |
60 |
61 | ### 4. Enable the CAN interface and check whether it is up
62 |
63 | `ip link set can0 up`
64 | `ip -details link show can0`
65 |
66 | #### To disable CAN, run
67 |
68 | `ip link set can0 down`
69 |
70 |
71 |
72 | ### 5. Hardware self-test / Loopback test mode; configure and enable in the same command line
73 |
74 | `ip link set can0 up type can bitrate 1000000 dbitrate 2000000 fd on loopback on`
75 | `ip -details link show can0`
76 |
77 | #### Send and receive message in internal loopback mode
78 |
79 | `candump can0 -L &`
80 | `cansend can0 300#AC.AB.AD.AE.75.49.AD.D1`
81 |
82 |
83 |
84 |
85 |
86 | ## Ping over Ethernet and send/receive CAN message simultaneously
87 |
88 | ### 1. We have been already using the board's terminal on serial port; however we need to set up ssh for also using the terminal over Ethernet. To do so, add the following line to local.conf
89 |
90 | `cd ~/Projects/yocto/build-mp1/conf`
91 |
92 | EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
93 | EXTRA_IMAGE_FEATURES += "ssh-server-openssh"
94 |
95 |
96 |
97 | ### 2. Get the IP address of your board
98 |
99 | `Board $> ip addr show`
100 |
101 |
102 |
103 | ### 3. Connect to your board over Ethernet
104 |
105 | `PC $> ssh root@`
106 |
107 |
108 |
109 | ### 4. Ping and test CAN data in two different terminals we set up
110 |
111 | `Terminal1 $> ping www.google.com`
112 |
113 | `Terminal2 $> ip link set can0 up type can bitrate 1000000 dbitrate 2000000 fd on loopback on`
114 | `Terminal2 $> ip -details link show can0`
115 |
116 | #### Make sure that the CAN link is up
117 |
118 | `Terminal2 $> candump can0 -L &`
119 | `Terminal2 $> for counter in {1..20000}; do cansend can0 300#AC.AB.AD.AE.75.49.AD.D1; done`
120 |
121 | 
122 |
--------------------------------------------------------------------------------
/images/STM32MP157F-DK2_board.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/darkquesh/stm32mp1/beb0edeec6de1dd81f5c4cbf23f8c35776a58a30/images/STM32MP157F-DK2_board.png
--------------------------------------------------------------------------------
/images/stm32mp1_ethernet_and_can.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/darkquesh/stm32mp1/beb0edeec6de1dd81f5c4cbf23f8c35776a58a30/images/stm32mp1_ethernet_and_can.png
--------------------------------------------------------------------------------
/qt5_on_stm32mp1.md:
--------------------------------------------------------------------------------
1 | ## Resources
2 |
3 | - https://wiki.dh-electronics.com/index.php/Add_Yocto_SDK_with_QT5_to_QT_Creator
4 | - https://www.emsyslabs.com/how-to-compile-linux-using-yocto-for-stm32mp1/
5 | - https://wiki.st.com/stm32mpu/wiki/How_to_build_and_use_an_SDK_for_QT
6 | - https://medium.com/@BradenSunwold/how-to-set-up-stm32mp1-with-qt-part-1-7576eec8f1fe
7 | - https://embeddeduse.com/2020/06/19/qt-embedded-systems-2-build-qt-sdk-with-yocto/
8 | - https://doc.qt.io/Boot2Qt/b2qt-meta-qt6.html
9 |
10 |
11 | ### Download the layer for Qt5
12 | cd ~/Projects/yocto
13 | git clone https://github.com/meta-qt5/meta-qt5
14 | cd meta-qt5
15 | git checkout kirkstone
16 |
17 | ### Then, edit the layer config file
18 | cd ~/Projects/yocto/build-mp1
19 | gedit conf/bblayers.conf
20 |
21 | ### Change BBLAYERS with the following
22 | >BBLAYERS ?= " \
23 | > /home/dell/Projects/yocto/poky/meta \\
24 | > /home/dell/Projects/yocto/poky/meta-poky \\
25 | > /home/dell/Projects/yocto/poky/meta-yocto-bsp \\
26 | > /home/dell/Projects/yocto/meta-openembedded/meta-oe \\
27 | > /home/dell/Projects/yocto/meta-openembedded/meta-python \\
28 | > /home/dell/Projects/yocto/meta-st-stm32mp \\
29 | > /home/dell/Projects/yocto/meta-custom \\
30 | > /home/dell/Projects/yocto/meta-qt5 \\
31 | > "
32 |
33 | ### save and exit, and run:
34 |
35 | bitbake meta-toolchain-qt5
36 |
--------------------------------------------------------------------------------
/stm32mp1_sdk_check.sh:
--------------------------------------------------------------------------------
1 | #Bash script to initialise STM32MP1 SDK
2 |
3 | #!/usr/bin/sudo bash
4 |
5 | cd /home/STM32MPU_workspace/STM32MP1-Ecosystem-v4.0.0/Developer-Package
6 |
7 | echo Inside the Developer-Package folder
8 |
9 | source SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
10 |
11 | echo Starting SDK...
12 | echo $'\n'
13 |
14 | echo Checking the target architecture *arm*
15 | echo $ARCH $'\n'
16 |
17 | echo Checking the toolchain binary prefix for the target tools *arm-ostl-linux-gnueabi-*
18 | echo $CROSS_COMPILE $'\n'
19 |
20 | echo Checking the C compiler version *arm-ostl-linux-gnueabi-gcc 11.2.0*
21 | echo $CC --version $'\n'
22 |
23 | echo Checking that the SDK version is the expected one *4.0.1-openstlinux-5.15-yocto-kirkstone-mp1-v22.06.15*
24 | echo $OECORE_SDK_VERSION $'\n'
25 |
26 | echo DO NOT close this terminal until cross-compilation is done!
27 |
28 | cd /home/STM32MPU_workspace/STM32MP1-Ecosystem-v4.0.0/Developer-Package/stm32mp1-openstlinux-22.06.15/sources/gtk_hello_world_example
29 |
30 | /bin/bash
31 |
--------------------------------------------------------------------------------
/yocto.txt:
--------------------------------------------------------------------------------
1 | ### To start using bitbake you need to source the "oe-init-build-env" script located into poky/ directory. So you should do something like this every time using bitbake:
2 |
3 | cd ~/Projects/yocto
4 | source poky/oe-init-build-env build-mp1
5 | cd build-mp1
6 |
7 | bitbake-layers show-layers
8 |
9 | bitbake -c menuconfig virtual/kernel
10 |
11 | bitbake core-image-minimal # or one of the images here https://docs.yoctoproject.org/ref-manual/images.html
12 |
13 | # You may continue building the image without starting over by executing the following command
14 |
15 | bitbake -f core-image-minimal
16 |
17 | # If you want to start over
18 |
19 | bitbake -c cleanall core-image-minimal
20 |
21 | # To clean out everything
22 |
23 | rm -rf tmp
24 |
25 |
26 |
27 | ### Create the final image for the SD card
28 |
29 | cd ~/Projects/yocto/build-mp1/tmp/deploy/images/stm32mp1/scripts
30 |
31 | ./create_sdcard_from_flashlayout.sh ../flashlayout_core-image-minimal/extensible/FlashLayout_sdcard_stm32mp157f-dk2-extensible.tsv
32 |
33 | # After unmounting the SD card
34 |
35 | sudo dd if=../flashlayout_core-image-minimal/extensible/../../FlashLayout_sdcard_stm32mp157f-dk2-extensible.raw of=/dev/mmcblk0 bs=8M conv=fdatasync status=progress oflag=direct
36 |
37 | ## Voila!
38 |
39 |
40 | # Adding build tools (including GCC and Nano) to the Linux system
41 |
42 | Find the local.conf file (in .../yocto-labs/build/conf) and add these lines (doesn’t seem to matter where but the space before the package name seems to be important!):
43 |
44 | IMAGE_INSTALL:append = " packagegroup-core-buildessential"
45 | IMAGE_INSTALL:append = " nano"
46 | IMAGE_INSTALL:append = " apt"
47 |
48 | The first line will append the typical GCC build tools. The second line will add the Nano editor (in case you prefer not to work with the VI editor that is part of the minimal Linux system).
49 |
50 | # Pay attention to syntax changes in newer versions: https://docs.yoctoproject.org/next/migration-guides/migration-3.4.html
51 |
52 |
53 | # Make Kernel Changes Permanent
54 |
55 | bitbake -c savedefconfig virtual/kernel
56 |
57 | Now rebuild the Linux system and flash it to an SD Card. If all went well, you can now use GCC and the Nano editor natively on the STM32MP157F-DK2 board.
58 |
59 | # If apt commands give an error like this E: flAbsPath on /var/lib/dpkg/status failed ; run the following
60 | touch /var/lib/dpkg/status
61 |
62 |
63 | sudo picocom -b 115200 /dev/ttyACM1
64 | # If you wish to exit picocom, press [Ctrl][a] followed by [Ctrl][x]
65 |
66 | # nano /etc/apt/sources.list.d/sources.list
67 |
68 | deb [trusted=yes] http://packages.openstlinux.st.com kirkstone InRelease
69 | deb [trusted=yes] http://packages.openstlinux.st.com kirkstone/main armhf Packages
70 | deb [trusted=yes] http://packages.openstlinux.st.com kirkstone/updates armhf Packages
71 |
72 | # nano /etc/apt/apt.conf
73 |
74 | APT::Architecture "${DPKG_ARCH}";
75 |
76 |
77 | ### Create custom layer and image
78 |
79 | # Enable the OpenEmbedded build environment
80 |
81 | cd ~/Projects/yocto
82 | source poky/oe-init-build-env build-mp1
83 |
84 | # Create a custom layer
85 |
86 | cd ~/Projects/yocto
87 | bitbake-layers create-layer meta-custom
88 |
89 | # Create custom image
90 |
91 | cd meta-custom
92 | mkdir -p recipes-core/images
93 |
94 | # Copy the core-image-minimal.bb recipe to use a starting point
95 |
96 | cp ../poky/meta/recipes-core/images/core-image-minimal.bb recipes-core/images/custom-image.bb
97 | vi recipes-core/images/custom-image.bb
98 |
99 | # Change the recipe to the following
100 |
101 |
102 | # Create the final custom image for the SD card
103 |
104 | cd ~/Projects/yocto/build-mp1/tmp/deploy/images/stm32mp1/scripts
105 |
106 | ./create_sdcard_from_flashlayout.sh ../flashlayout_custom-image/extensible/FlashLayout_sdcard_stm32mp157f-dk2-extensible.tsv
107 |
108 | sudo dd if=../flashlayout_custom-image/extensible/../../FlashLayout_sdcard_stm32mp157f-dk2-extensible.raw of=/dev/mmcblk0 bs=8M conv=fdatasync status=progress oflag=direct
109 |
110 |
111 | ## Enable peripherals like I2C
112 |
113 | cd ~/Projects/yocto/build-mp1/
114 | cp tmp/work-shared/stm32mp1/kernel-source/arch/arm/boot/dts/stm32mp157d-dk1.dts ~/Documents
115 | cd ~/Documents
116 | cp stm32mp157f-dk2.dts stm32mp157f-dk2.dts.orig
117 | vi stm32mp157f-dk2.dts
118 |
119 | git diff --no-index stm32mp157f-dk2.dts.orig stm32mp157f-dk2.dts > 0001-add-i2c5-userspace-dts.patch
120 |
121 | gedit 0001-add-i2c5-userspace-dts.patch
122 |
123 | # Change the file header so that it points to the correct file locations:
124 |
125 | --- a/arch/arm/boot/dts/stm32mp157f-dk2.dts
126 | +++ b/arch/arm/boot/dts/stm32mp157f-dk2.dts
127 |
128 |
--------------------------------------------------------------------------------