Short answer - YES! Using an MK10DN512... Similar issues with signal names etc. Had one beef wi= th interrupts and precisely when the flags were set during boot-up. (We had= an unexpected interrupt as the boot process was proceeding. The processor = starts at Vdd =3D 1.7 V but connected H/W at ~ 2.7 V so a state change was = detected. Even holding the reset didn't seem to fix it. Fortunately I am ju= st the H/W guy - my F/W colleagues had to sort it...) But yes - the documentation is a slog. Stephen p.s. NXP - I am still waiting for a response to the support ticket I raised= - 10 days later... -----Original Message----- From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of= Sean Breheny Sent: Thursday, 14 December 2017 2:20 AM To: Microcontroller discussion list - Public. Subject: [EE] NXP/Freescale documentation Hi all, I would assume that some of you are using the ARM processors produced by Fr= eescale (now NXP) in their "Kinetis" line. I am working on a project using = the MK20DX256VLH7 which is an ARM Cortex M4 with 256KB flash and a host of = peripherals. It is a pretty amazing chip and my first venture into ARM terr= itory. I am using a Teensy 3.2 module, an Arduino-compatible device, which = contains this processor. I'm very happy with the processor itself so far but the NXP/Freescale docum= entation is horrible for this part. I feel the need to rant a bit and see i= f my experience is common. I am used to the evil which lurks in the Microch= ip datasheets (references to info found only in other documents which only = partially applies to your chip, specs which are never declared valid but go= straight from "preliminary" to "not recommended for new designs", etc.) bu= t I didn't expect to have similar problems with this because I've had fairl= y good experiences with Freescale Power-PC-based processor documentation. The first problem I've had is that there doesn't seem to be any overall gui= de to the manual, which is needed because it is 1400 pages long. It took me= a long time to realize that you not only had to enable peripherals but you= also have to enable the clock path to each peripheral, which is listed und= er a section called "System Integration Module" and there is no warning und= er, say, the ADC section that you need to enable its clock in the "SIM". Not only that but you have to enable the clock FIRST and then the periphera= l's own enable. The second problem is that signal names are mentioned in peripherals and th= en never mentioned again anywhere in the entire 1400 page document, so that= you don't know what other internal signals those connect with. For example= , the ADC has both a hardware trigger ADHWT and "hardware trigger channel s= elects" called ADHWTSn where n can be A or B on this chip. It turns out tha= t these connect to "pre-trigger" signals coming from the Programmable Delay= Block, but it never says that anywhere. I had to figure it out from guessi= ng and inference. Thirdly, much of the wording is very vague. In one spot it says: PDB channel's corresponding pre-trigger asserts when the counter reaches th= e channel delay register *and* one peripheral clock cycle after a rising ed= ge is detected on selected trigger input source or software trigger is sele= cted and SETRIG is written with 1. The asterisks around AND are mine. What they really mean here is OR, becaus= e EITHER of the two conditions they specify can assert the pre-trigger. (as= an additional issue, SETRIG should really be SWTRIG) They also use the term "ping-pong operation" to refer to what is usually ca= lled "round robin". I've never heard of ping-pong ever including more than = two states. These are only a few examples of the problems which made it take two days f= or me to get hardware-triggered ADC working. Anyone else have similar problems with this NXP/Freescale ARM documentation= ? Sean -- http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/chang= e your membership options at http://mailman.mit.edu/mailman/listinfo/piclis= t --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .