i.MX RT1015 - Page 1
Forum section: electronics / general

author: ehughes
author_rank: Frequent Contributor
timestamp: September 07, 2018, 02:35:07 am
content: http://media.nxp.com/phoenix.zhtml?c=254228&p=irol-newsArticle&ID=2366031$1.50 in qty 10k500MHz100LQFPAvailable in Q4

author: luiHS
author_rank: Frequent Contributor
timestamp: September 07, 2018, 05:20:21 am
content: Interesting, probably with features lower than the RT1020, will be the younger brother of the family.We will have to see the comparison with the rest of RT, with an LQFP100 what is certain is that we can not connect an SDRAM or a Hyperflash.If the final price, for retail purchase, does not exceed 3 or 4 dollars, it will be extraordinary.

author: jaromir
author_rank: Unknown
timestamp: September 07, 2018, 08:02:52 am
content: Table comparing the RT10xx devices is in fact sheethttps://www.nxp.com/docs/en/fact-sheet/IMXRTSERIESFS.pdfthough proper datasheet would not hurt, too.

author: rjp
author_rank: Regular Contributor
timestamp: September 07, 2018, 08:05:42 am
content: seems the esp32 and the talk around open risc has dropped a bomb under the ARM vendors.dual issue . 500mhz micros with all the fruit , for next to nothing, amazeballs.

author: ehughes
author_rank: Frequent Contributor
timestamp: September 07, 2018, 02:41:38 pm
content: The price is related to the process technology. You can fit more of the RT parts in the same die size as the Kinetis family. Also, flash is a huge part of the IC area and cost. Remove it pushes cost way down.

author: ali_asadzadeh
author_rank: Super Contributor
timestamp: September 07, 2018, 02:46:45 pm
content: It's very nice, But I could not find a cool way of generating peripheral drivers, Something like STMCUBE, I could not find things in MCUxpressoOr Am I missing something totally wrong!!!I think STM32H7 value line regarding having 400MHz and having STMCUBE are better somehow, Unless I could find something for peripheral drivers!Also I prefer Keil over this stupid eclipse thing

author: luiHS
author_rank: Frequent Contributor
timestamp: September 07, 2018, 03:26:19 pm
content: For me, MCUXpresso is better than STM32 with Cubemx.In MCUXpresso, you can use wizards to configure Ports, Clock and Peripherals (as you can with Cubemx), and in the SDK there are many examples of source code, practically for everything you want to do. There is nothing you can have in Cubemx, and you miss it in MCUXpresso.Cubemx does not provide you with a library of examples of source code, and the program it generates is empty, you must write your own software. The functions for each peripheral that you have selected when configuring the Cubemx assistant are there, but there is no example of source code on how to use all those functions.For me it is essential, you have a large library of examples of source code for all the most used peripherals, so I can see how to make my own program or modify some of the examples by adding new code. For example, Arduino also includes a lot of source code samples, although NXP with MCUXpresso and the SDKs are better organized and documented.I have worked with PIC32, Atmel SAM S70, NXP Kinetis, Arduino for Teensy, STM32 with Cubemx, and without hesitation I prefer MCUXpresso with the new RT from NXP. From version 10.2, MCUXpresso integrates all the assistants within the IDE itself, so that the ready-to-use program is generated, or by importing any of the numerous sample sources of the SDK.NXP, it seems that he is dedicating a lot of work to the MCUXpresso, so that it becomes a good working tool for all its microcontrollers, LPC, Kinetis and i.MX, and for now they are getting it.

author: ehughes
author_rank: Frequent Contributor
timestamp: September 07, 2018, 04:30:38 pm
content: https://mcuxpresso.nxp.com/en/welcomeYou 1st generate an SDK. Once an SDK installed, MCUXpresso will generate example programs, etc and include all of the drivers in any newly created project.

author: mark03
author_rank: Frequent Contributor
timestamp: September 07, 2018, 05:12:40 pm
content: For those who have looked at both CubeMX and MCUXpresso, could you compare the two on:1) bloat2) quality / readability of the source code3) bugginess?On STM32 I would never in a million years dream of using CubeMX or the ST HAL. I find it utterly appalling. But I am new to IMXRT, and aware that the IMX6 heritage means their peripherals may be a bit more complicated, and also I have never looked at MCUXpresso. Just curious if this particular specimen of vendor code stands any chance of winning me over

author: ali_asadzadeh
author_rank: Super Contributor
timestamp: September 08, 2018, 05:20:45 am
content: QuoteThanks for the tips, Is there any Good tutorial out there?

author: luiHS
author_rank: Frequent Contributor
timestamp: September 08, 2018, 01:45:08 pm
content: Quote from: ali_asadzadeh on September 08, 2018, 05:20:45 amFor MCUXpresso, the user manuals in PDF that are installed in the application directory, mainly the "MCUXpresso IDE User's Guide" and the "MCUXpresso Configuration Tools User's Guide".And for SDK there are also User Manuals that you can download when create the SDK in the NXP web site. The main is "MCUXpresso SDK API Reference Manual".

author: ali_asadzadeh
author_rank: Super Contributor
timestamp: September 09, 2018, 11:04:49 am
content: QuoteThanks for the help, are you using MCUXpresso or keil for your projects? can I export the projects to keil?

author: luiHS
author_rank: Frequent Contributor
timestamp: September 09, 2018, 04:35:59 pm
content: Quote from: ali_asadzadeh on September 09, 2018, 11:04:49 amI work with MCUXpresso, it's free without limitations and professional features, I prefer to always work with free tools if they are of good quality. For NXP I use MCUXpresso, and for STM32 I work with Eclipse + AC6 and Cubemx, all for free.When you generate the SDK on the NXP website, you can choose the destination tool, with options for MCUXpresso, GCC, IAR, Keil and you can also choose the OS, Windows, Mac or Linux.

author: ali_asadzadeh
author_rank: Super Contributor
timestamp: September 10, 2018, 05:12:56 am
content: Thanks