DIY ImxRT1010 board, sharing hardware debugging experience

RCSN

DIY ImxRT1010 board, sharing hardware debugging experience [Copy link]

 

According to the previous post, the host bought the MIMXRT1010-EVK board post https://en.eeworld.com/bbs/thread-1095711-1-1.html , but the official board has too many jumper cap settings. I also want to know whether this NXP M7 hardware is difficult to design. Facts have proved that in the design of the imxrt series, except for the different kernel, other power supplies and Boot are similar to the Imx6 series. Compared with the simplicity and crudeness of H7, the hardware design of the imxrt series does not really consider the feelings of MCU users, and some places are also very particular. The host shares some experience gained from this board design. This is the board drawn by the host. It is inevitable that the hand soldering is ugly. Hope you understand.

Let's talk about some features of imxrt1011 first, which is also a pitfall. First of all, from the IO allocation, Imxrt1010 has a total of 80 IOs, but less than 30 IOs are available. Almost 30 IOs are occupied by power-related, 12 IOs are occupied by boot settings and qspi flash, and JTAG, using the minimum pins to debug SWD, also requires 2 IOs, and JTAG debugging must be enabled by grounding JTAG_MOD. This also occupies 3 IOs, and the crystal oscillator has an HSE and an RTC, and a reset pin, which also occupies 5 IOs. In this way, 50 IOs have been occupied, and the IOs available for users are only 30 IOs . NXP uses Feika's Imx series, and it may not be too serious to squeeze the toothpaste. NXP advertises that the M7 is the cheapest in the industry, with a bulk price of US$1, but in reality, it may cost more than 10 yuan to users (retail investors). According to such hardware IO allocation, except for the higher main frequency, it seems that the cost performance is not very high.


This content is originally created by RCSN , a user of EEWORLD forum . If you want to reprint or use it for commercial purposes, you need to obtain the author's consent and indicate the source

RCSN

Secondly, from the peripherals, Imxrt1011 has common peripherals and Feika's unique peripherals, which is quite rich. What needs to be complained is that the flexio nominally has 27 pins, but after being occupied by boot and qspi flash, there are only less than 18 pins. They are reused in a mess, for example, the camera interface of flexio cannot be used, it is occupied by boot and qspi in turn, and the camera data interface cannot be continuous.

RCSN

Third, for the Imxrt series, it is best to use LDO+DCDC power supply. LDO powers the system SNVS, and DCDC powers GPIO, ADC, etc. After SNVS is started, the internal DCDC will step down 3.3V to 1.2 and output it to the M7 core related power supply. For this reset design, it is recommended to use a dedicated reset chip. The imxrt series is more particular about reset. I tried to reset it with an RC circuit and found that there was a probability of failure during the debugging and downloading process. It was normal after using the reset chip.

Fourth, the boot settings must be strictly in accordance with the official board design, which is indispensable. Regarding QSPI, there are too many flash memories on the market, and when selecting a model, you need to pay attention to whether it supports QPI, that is, XIP.

RCSN

Officially, there are quite a lot of examples, especially USB examples. But the official SDK and MDK PACK have not been updated since October. Some examples have some bugs, such as the lgvl example. Here are two examples, one UVC and one emwin.

freebsder

Mighty Brother

lcofjp

My freeloading brother-in-law is awesome, is there no chip with more pins in this series?

RCSN

lcofjp posted on 2019-12-8 22:48 The free brother-in-law is awesome, is there no chip with more pins in this series?

Good evening, Captain. The imxrt1011 series currently has 400M and 500M main frequencies, both in LQFP80 package.

lcofjp

RCSN posted on 2019-12-8 22:51 Good evening, Captain. The imxrt1011 series currently has 400M and 500M main frequencies, both in LQFP80 package.

Then you should take me to play nuc980

RCSN

lcofjp posted on 2019-12-8 22:57 Then you should take me to play nuc980

Captain, you have to lead me on this.

lcofjp

RCSN posted on 2019-12-8 23:08 Captain, you have to lead me in this

I won't talk to you anymore. It won't be good if I get on the moderator ranking list! Haha

dcexpert

The i.MX.RT port of OpenMV is also out

RCSN

dcexpert posted on 2019-12-8 23:23 The i.MX.RT port of OpenMV is also out

This 1011 cannot be done because there is no relevant external RAM interface and nothing related to camera.

dcexpert

RCSN posted on 2019-12-8 23:29 This 1011 can't be done, there is no relevant external RAM interface, nor camera related.

There is already one

https://github.com/RockySong/micropython-rocky

chenzhufly

Good craftsmanship

hotsauce1861

You did a great job.

RCSN

dcexpert posted on 2019-12-8 23:51 There is already one https://github.com/RockySong/micropython-rocky

Yes, I know this. I mean Imxrt1011 can't do this porting.

sblpp

When 1021 first came out, I couldn’t wait to try it out. I came with great joy but left with disappointment!

I gave up before I even started, luckily I jumped out quickly :)

RCSN

sblpp posted on 2019-12-9 15:16 When 1021 first came out, I couldn't wait to get started. I came with great joy but left disappointed! I gave up before I even got started. Fortunately, I jumped out quickly...

The price of 1011 series is not very attractive at present. I am a little disappointed after finishing 1011. I feel that NXP has no intention to design and just wants to release more series of imxrt. I tried my best to squeeze the toothpaste of Feika's imx, but the series released are more and more castrated. In the end, I feel that the original imxrt1052 is still powerful.

leifengfirst

dcexpert posted on 2019-12-8 23:51 There is already one https://github.com/RockySong/micropython-rocky

Has anyone used this for QR code recognition?

qjp1988113

NXP has gone further and further in terms of the practicality of MCUs and the readability of information.