-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sama5d2 config files have inconsistencies #65
Comments
The sama5d2-xplained machine is supposed to have at91bootstrap, u-boot, the kernel and devicetree on the SPI flash then boot on a rootfs on the SD card. This PR solves that: linux4sam/u-boot-at91#4 Regarding the bitrate. It has been changed consistently to 115200 in the latest versions of at91bootstrap and u-boot. This PR solves that: #70 |
And now, I've submitted #71 to solve the last issue. It uses wic to generate sdcard image ready to be flashed using dd. I think we can close that issue once the PR are merged. |
@alexandrebelloni 's PR taken and merged. |
I have a SAMA5D3 xplained board. Moreover, I am interested to configure the system such that the console operates over the USB port (USB-A, J6), and in my computer I would see it as /dev/ttyACM0. This the behavior for the factory image on the board and also for demo images (see here), but I do not know how to do it with Yocto, or when I build the kernel myself. It would be nice if this is added as an option in conf files. |
The documentation available here :
http://www.at91.com/linux4sam/bin/view/Linux4SAM/Sama5d2XplainedMainPage#Build_Yocto_Poky_rootfs_from_sou
Describes how to rebuild a full linux system for the xplained boardusing the "sama5d2-xplained" config file
However the given example produces images which are hard to use, in particular the resulting u-boot binary ships with an "ubi" command line while the rootfs is provided in .tar.gz format
Regarding the sama5d2-xplained-sd MACHINE,
S0:12345:respawn:/sbin/getty -L 115200 ttyS0
, however u-boot is setup with baudrate=56700, and boots the kernel with "bootargs=console=ttyS0,57600", therefore once the kernel has booted, the console outputs garbage.The text was updated successfully, but these errors were encountered: