RT1020, anything Device, IDE, SWO etc related issues. - Page 1
Forum section: electronics / general

author: MT
author_rank: Super Contributor
timestamp: August 03, 2018, 08:49:06 pm
content: Edit: found info.Edit again:Quad timers,disappoint! 16bit with 8 stage prescaler, thats simply 1988! DAC's 6bit, draconian bad!

author: MT
author_rank: Super Contributor
timestamp: August 03, 2018, 10:48:07 pm
content: Quote from: luiHS on August 03, 2018, 07:41:54 pmI have hopes one can boot from single wire classic sluggish bog standard SPI as well but i havent read boot pages yet.Edit: yes it does 4 different settings.QuoteThe impression i get from the RT1020 DMA v.s F4 its more flexible but also quite eaysier to setup and use.

author: MT
author_rank: Super Contributor
timestamp: August 03, 2018, 10:53:11 pm
content: Quote from: luiHS on August 03, 2018, 07:54:09 pmI just installed MCUxpresso and saw that one can start a plain MCU only project so i assume one can import individual peripheral code as well. I wish NXP could do a SWO dongle or a similar Nucleo/disco board. Well see perhaps it will come later.

author: MT
author_rank: Super Contributor
timestamp: August 04, 2018, 08:56:35 pm
content: Quote from: evb149 on August 04, 2018, 04:45:46 pmThanks for info, everything is confusing, my brain is configed to think in broken french STM32F4 lingo!Just learned that a K20/K25 loaded with DAP-link OpenSDAv2 is what apparently is onboard the RT1020 EVK is the actual debug programming dongle/probe/gobblegookbox. The OM13054 seams to be the default NXP LPC-Link2 probe equivalent of ST STlink2, but not a "direkt" indikation it's compatible with RT1020 but its docks gives hints it is, this guy below says it works but then one could aswell just buy the damned RT1020EVK (58Euro) no big deal and use that as a prog/debug/dongle, it's just abit bulky and i would most likely have to build a box for it else i will short the thing.https://mcuoneclipse.com/2017/12/16/mcuxpresso-ide-v10-1-0-with-i-mx-rt1052-crossover-processorBut i assume a number of Kinetiz K20/5, FRDM-KL25Z boards do as well. But is seams lot of faff to get it working.Cant find anything of STLink reprogged with DAP-link/OpenSDA. Edit i actually found one old.https://mvdlande.wordpress.com/2015/10/05/cmsis-dap-on-a-cheap-st-link-v2-mini-adapterDAP link OpenOSD project have a comparability page:https://github.com/ARMmbed/DAPLink/blob/master/README.mdhttps://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/lpc-cortex-m-mcus/lpc1100-cortex-m0-plus-m0/lpc-link2:OM13054Glory for the RT1050 EVK board but no RT1020 EVK, will be later i assume.https://www.nxp.com/products/processors-and-microcontrollers/applications-processors/i.mx-applications-processors/i.mx-rt-series/i.mx-rt1050-evaluation-kit:MIMXRT1050-EVK

author: luiHS
author_rank: Frequent Contributor
timestamp: August 04, 2018, 10:58:39 pm
content: You can make your own device based on OpenSDA / DAP Link, with a Kinetis MK20. The diagrams are available on both RT1020 / RT1050 evaluation boards, and the firmware, both binary and sources, are free to download on the NXP website.The other alternative, for production is to load the software to the RT1020 / RT1050 using a USB port and the free utility MFG Tool from NXP.What I did not try yet is to make Debug directly connecting SWD to the microcontroller, but I'm sure it can be done, as long as you use a device that has drivers recognized by MCUXpresso, as is the case with Jlink and Multilink PE.My suggestion, for the development stage, to use the evaluation board and for production programmed by USB with MFG Tool. Unless the product is very sensitive to the length of tracks and you can not use a shield connected to the Arduino type expansion port of the evaluation board, in that case it is best to make your own device with MK20 and OpenSDA, it is very simple, I will probably do it if I have problems with the shield that I have already manufactured to use with the evaluation board.My only question is if using DAP-LINK, you can load an image of the firmware, which is encrypted, something absolutely essential when the product and a commercial version. The programming process, using MCUXpresso, is done automatically and I do not think the firmware is being encrypted before being upload to the microcontroller. In the manuals, it deals with the encryption of the firmware, before upload it with MFG Tools via USB.

author: MT
author_rank: Super Contributor
timestamp: August 04, 2018, 11:04:02 pm
content: Quote from: luiHS on August 04, 2018, 10:58:39 pmThats what im listing in my post, its to much faff, just want a easy to buy 10euro SWD/SCK/NRST el cheapo dongle and thats it and off i go. Just like STLink dongle, USB in SWO out. Not about production but debug and develop code.

author: luiHS
author_rank: Frequent Contributor
timestamp: August 04, 2018, 11:22:20 pm
content: Quote from: MT on August 04, 2018, 11:04:02 pmThen you must make your own DAP-LINK device based on Kinetis MK20. I recently searched for Google and Aliexpress and did not find any commercial products ready to use. It seems strange to me, because the Chinese copy everything and offer it at a low price on Aliexpress, and in this case it would also be a legal product because everything is open source.

author: MT
author_rank: Super Contributor
timestamp: August 04, 2018, 11:30:44 pm
content: Quote from: luiHS on August 04, 2018, 11:22:20 pmAnd as already said i dont want to.QuotePrincely, thats my point, why NXP cant take their thump out of the rear end and produce a SWO dongle for 10 euron thats compatible with all their MCU's and end al hassle and faff NXP should make just as ST Nucleo/Disco boards. Im not keen on the Chinese copy stuff, there is a reason to have NXP to make their own standalong dongles, can ST , Cypress etc, afford it on all their el cheapo boards surely NXP can to.

author: luiHS
author_rank: Frequent Contributor
timestamp: August 04, 2018, 11:31:30 pm
content: I remembered, there is a product, Segger J-Link-OB, original or Chinese copy, it is very cheap in both cases, but I have not tried it. Its supported by MCUXpresso.https://www.amazon.com/gp/product/B0791MFJZ3/ref=ox_sc_act_title_1?smid=ACDL71MQNDI3F&psc=1https://es.aliexpress.com/store/product/J-Link-OB-ARM-Debugger-Programmer-Downloader-replace-v8-SWD/1987383_32758602079.htmlMore information about the features of the product, on the Segger website:https://www.segger.com/products/debug-probes/j-link/models/j-link-ob/I ordered one just now to test it, to Amazon Spain. As it is so cheap nothing is lost, and it may be useful, we know for sure that MCUXpresso supports it. I will receive on Wednesday.https://www.amazon.es/gp/product/B0769K2BGK/ref=ox_sc_act_title_1?smid=A80IWAZC4BCUO&psc=1

author: MT
author_rank: Super Contributor
timestamp: August 05, 2018, 02:25:45 am
content: Quote from: luiHS on August 04, 2018, 10:58:39 pmShort glance in documentation it seams you use MFG tool and Elftosb tool who does the actual encryption of your image developed with MCUXpresso who does not while decryption is hardware on the fly. There are several types of encryption and non encrypted images depending on where you are in the development process. Well this is over my head for now anyway.

author: MT
author_rank: Super Contributor
timestamp: August 05, 2018, 02:44:47 am
content: All right! In this thread SWO is mentioned as default interface through the onboard K20 OpenOSB DAP-link software but its buggy slow so SEGGER JLINK directly to SWO is more adekvate at that point in time, RT1050 EVK has newer SWO firmware.https://www.eevblog.com/forum/microcontrollers/fail-debugprogram-with-mcuxpresso-and-evk-mimxrt1020-or-mimxrt1050-evk/msg1674296/?topicseen#msg1674296Edit:SWO progress!https://www.eevblog.com/forum/microcontrollers/nxp-rt1020-programdebug-by-swd/msg1732772/#msg1732772