Quote:
Originally Posted by ayyasprings
1) Toolchain for that board.
|
Irrelevant reguirement.
There's crosstool-NG to build a custom GCC toolchain.
If you're in a rush, you can download a pre-built toolchain from GNU ARM, Linaro, Sourcery CodeBench, or maybe your PC's distro.
Quote:
Originally Posted by ayyasprings
2) Uboot source code supporting that so that I can Cross compile that Uboot on my own and creating binary and porting facility.
|
U-Boot is licensed under the GPL, so if it's used/distributed in binary form, then the source code should be available .
Quote:
Originally Posted by ayyasprings
3) Linux Kernel Source code supporting that so that I can configure and cross compile that kernel on my own,modify the device drivers and create image and porting facility.
|
Linux is licensed under the GPL, so if it's used/distributed in binary form, then the source code should be available.
Quote:
Originally Posted by ayyasprings
4)Root filesystem source with that I can pickup my required utilies and features/applications and compile and make rootfs image with my desired rootfs type eg) jffs2,squashfs to experiment on my own and port from host.
|
An unreasonable requirement since there is no consolidated repository of "
root filesystem source".
Tools such as Buildroot and Yocto are used to solve this issue.
Quote:
Originally Posted by ayyasprings
6)Having In built display or support to connect any external display as additional peripheral. If the display dont have touch facility then it should support keyboard as peripheral.
|
Rather vague requirement.
Display output could range from composite video (analog 480i) to HDMI (digital 1080p). Interface connection could be standard HDMI connector to a 50-pin FPC connector for LVDS.
Touchscreen interface could be raw input requiring A-to-D conversion or external converter with a USB connection.
A dedicated keyboard interface is deprecated; that's one of the reasons for USB.
Quote:
Originally Posted by ayyasprings
7)should have networking abilities atleast Ethernet.
|
Rather common for a development board, unless you're looking at something small and/or cheap intended for IOT.
Quote:
Originally Posted by ayyasprings
8)Also datasheets of the components should be available so that I can develop device drivers on my own and experiment.
|
This requirement disqualifies RPi and similar *Pi boards that use Broadcom or Allwinner SoCs.
TI, NXP/Freescale, and Atmel provide datasheets/TRMs for their SoCs consisting of 1000+ pages.