Hello Peter, On 08/02/2020 21:16, Peter Dufault wrote: > I will begin working on a BSP for the i.MX RT 10xx family. I require support > for a 1052 but will be developing on a 1064 so those two variants will have > some test coverage. > > I plan to start my work by making this a variant of the "imx" BSP. That > currently supports the "i.MX7D Applications Processor". > > I think that the network support provided by the "libbsd" "if_ffec" driver > will work with the ENET interface on the i.MX RT. > I think that initial support will be a straight-forward collection of already > working pieces. > > - If anyone has any warnings or "heads-up"s then let me know.
Note that we (embedded brains) are currently working on the imx BSP too. Our target is imx6ul/ull support (for some Phytec modules). I'll try to clean up the patches that are already nearly ready and send them to the list as soon as possible. For the ones that are not ready yet I'll try to give early warnings. Would be good if you could do the same thing. > - I haven't been working with "device trees". These are required for the > "imx" BSP. Is this the preferred direction for a BSP? >From my point of view it would be good to use the device tree for all targets that use a device tree for Linux or FreeBSD too. Especially if you want to use libbsd you can save a lot of necessary adaptions. > - If anyone has any suggestions for how to ultimately arrange things then let > me know. Right now, before I've gotten started, I plan to make this BSP a > variant in the "imx" BSP and to try to either re-use existing "chip" library > routines or add new ones. For the imx6 I still hope that no variant is necessary. But I planned to discuss this with Sebastian. > > Unfortunately this will definitely be a BSP supporting only what I need for > the current application. Like a lot of the BSPs that we have in RTEMS. Most of them grow whenever someone needs something new. Best regards Christian > > Peter > ----------------- > Peter Dufault > HD Associates, Inc. Software and System Engineering > > This email is delivered through the public internet using protocols subject > to interception and tampering. > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel > _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
