readme.txt 2.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  1. Kontron SMARC-sAL28
  2. ===================
  3. How to build it
  4. ===============
  5. Configure Buildroot:
  6. $ make kontron_smarc_sal28_defconfig
  7. Change settings to fit your needs (optional):
  8. $ make menuconfig
  9. Compile everything and build the rootfs image:
  10. $ make
  11. Copying the image to a storage device
  12. =====================================
  13. Buildroot builds an image which can be written to the internal eMMC
  14. storage, a SD card or an USB thumb drive. You can use the following
  15. command on your host:
  16. $ sudo dd if=output/images/sdcard-emmc.img of=/dev/sdx bs=1M
  17. Where /dev/sdx is the corresponding block device of your SD card or USB
  18. thumb drive. To flash it on your internal eMMC use the following command on
  19. the board:
  20. # dd if=sdcard-emmc.img of=/dev/mmcblk1 bs=1M
  21. Be sure you have not booted from the internal eMMC in this case!
  22. Booting the board
  23. =================
  24. By default the bootloader will search for the first valid image, starting
  25. with the internal eMMC. Consult the vendor documentation on how to use the
  26. DIP switches to select specific boot devices. To use the bootloader
  27. environment set the boot_targets correspondingly. E.g.:
  28. # setenv boot_targets usb0
  29. To boot from an USB thumb drive.
  30. The device tree is loaded according to the filename in fdtfile. The
  31. following command will set the default device tree, which works on almost
  32. all variants (with less features of course):
  33. # setenv fdtfile freescale/fsl-ls1028a-kontron-sl28.dtb
  34. Set this to a device tree which fits your board variant.
  35. Connect your serial cable to SER1 and open your favorite terminal emulation
  36. program (baudrate 115200, 8n1). E.g.:
  37. $ picocom -b 115200 /dev/ttyUSB0
  38. You will get a warning reported by fdisk when you examine the SD card.
  39. This is because the genimage.cfg file doesn't specify the SD card size
  40. (as people will naturally have different sized cards), so the
  41. secondary GPT header is placed after the rootfs rather than at the end
  42. of the disk where it is expected to be.
  43. You will see something like this at boot time:
  44. [ 4.552797] GPT:Primary header thinks Alt. header is not at the end of the disk.
  45. [ 4.560237] GPT:266272 != 7864319
  46. [ 4.563565] GPT:Alternate GPT header not at the end of the disk.
  47. [ 4.569596] GPT:266272 != 7864319
  48. [ 4.572925] GPT: Use GNU Parted to correct GPT errors.
  49. Updating the bootloader
  50. =======================
  51. Buildroot will automatically build the u-boot bootloader. The resulting
  52. image is called u-boot.rom and you can find it in the images/ directory.
  53. To update the bootloader on the board you could either copy it to an
  54. USB thumb drive or you could put it on a TFTP server. The following
  55. example assumes you have the bootloader image copied to the root of
  56. a thumb drive:
  57. # usb start
  58. # load usb 0:1 $loadaddr u-boot.rom
  59. # sf probe 0 && sf update $fileaddr 0x210000 $filesize