LPC5528 - CM33 with USB 2 HS + PHY - Page 1
Forum section: electronics / general

author: bson
author_rank: Unknown
timestamp: November 22, 2019, 01:30:45 am
content: It looks like the LPC5528 has a USB 2 HS controller and a built-in PHY. 512k flash, 256k SRAM, 150MHz clock, Cortex-M33 (CPU1) - and the usual assortment of ADC, SPI, I2C, I2S, etc. There's also an S2x series with built-in AES, secure boot, and other related security features (CM33 CPU0). The debug interface looks to be SWD, which means it can be used with OpenOCD. The LPC552x looks to have the CM33 DSP + SIMD extension. It's pretty new, but I'm wondering if anyone has had a chance to give it a spin yet? A cursory look through the datasheet and user guide suggests the USB 2 HS PHY is available even in the smallest QFP64 package.

author: ataradov
author_rank: Super Contributor
timestamp: November 22, 2019, 02:21:48 am
content: Well, I instantly hate their User Manual format (see attached image). Seriously, do they not expect people to use PDF readers? And it took answering some pretty invasive registration question to even download that.Other than this, if 64-pin devices will have working HS USB, it would be an excellent device. I've got a bit too much on my plate right now, but when 64-pin device comes out, I'm definitely making a board to play with one.

author: cv007
author_rank: Frequent Contributor
timestamp: November 22, 2019, 03:38:48 am
content: >Seriously, do they not expect people to use PDF readers?I don't see anything wrong. I have this pdf open in foxit reader on a Linux pc. What am I missing? I think nxp has good datasheets. The Freescale datasheets, not so much. I got one of those imxrt1010 $10.10 boards and forgot its a freescale part with its freescale inspired datasheet. The nxp datasheets have a 'Basic Configuration' section for each peripheral, that lays out what is needed to get going- clocks, power, etc., which is nice. Maybe others are similar enough, but many seem to leave out important things that it seems you are just supposed to know or figure out or piece together from various sections in the chapter.>And it took answering some pretty invasive registration question to even download that.What the h is wrong with these dudes. You have to login to download a user manual, and you are not done once you login as you are in for round 2 of questioning. Its tiring having to use a disposable email address every time you want something. Atmelchip seems to be the only sane company left in this department, and I hope that doesn't change.

author: ataradov
author_rank: Super Contributor
timestamp: November 22, 2019, 03:44:00 am
content: Quote from: cv007 on November 22, 2019, 03:38:48 amJump quickly to the ADC chapter without going to the main TOC and making the chapter list take half the screen. All those "Chapter N: LPC55S6x/LPC......" in front of every chapter are unnecessary and make it impossible to navigate the document from the side panel listing chapters.

author: cv007
author_rank: Frequent Contributor
timestamp: November 22, 2019, 04:00:55 am
content: I must be doing it wrong, I guess. I do agree there is no need to list every possible lpc series in the title of each chapter, and it makes no sense. If I had to use this document, I would see if the pdf document could be modified to change the chapter titles.

author: mark03
author_rank: Frequent Contributor
timestamp: November 22, 2019, 03:53:25 pm
content: Quote from: bson on November 22, 2019, 01:30:45 amThis is just the same SIMD set as the CM4. Nothing new AFAIK. The bigger deal will be when the new vector extension (codenamed Helium) starts hitting products.IMO the CM33 offers very little for hobbyists, versus the older CM4. It's just extra security crud that you don't want or need, and potentially costs extra time and effort to work around.The on-chip HS PHY on this one is cool though.

author: mikerj
author_rank: Super Contributor
timestamp: November 22, 2019, 05:01:58 pm
content: Quote from: mark03 on November 22, 2019, 03:53:25 pmI could see some of the coprocessors that CM33 enables being pretty handy, e.g. the PowerQuad on the higher end LPC parts giving accelerated FFT/DCT/FIR and CORDIC functions.

author: MT
author_rank: Super Contributor
timestamp: November 22, 2019, 05:47:48 pm
content: Quote from: ataradov on November 22, 2019, 03:44:00 amTry this instead, no log in, no strange chapters:https://www.nxp.com/docs/en/data-sheet/LPC55S2X-LPC552X.pdf

author: ataradov
author_rank: Super Contributor
timestamp: November 22, 2019, 06:33:00 pm
content: Quote from: MT on November 22, 2019, 05:47:48 pmThat is a totally different document. Both are necessary for designs using this MCU. But the actual User Manual is necessary for software development.

author: bson
author_rank: Unknown
timestamp: November 23, 2019, 02:29:44 am
content: Interesting, I didn't have to sign in or anything, but maybe I have a cookie already. Obviously, the PHY is the really cool feature here!

author: ataradov
author_rank: Super Contributor
timestamp: November 23, 2019, 02:34:25 am
content: Quote from: bson on November 23, 2019, 02:29:44 amYou only need to sign in for the User Manual. All other documentation is free to download. It is not a big deal, there are plenty of 5 minute mail services. I just have no idea why they need a database of junk accounts.

author: ehughes
author_rank: Frequent Contributor
timestamp: November 23, 2019, 02:16:01 pm
content: I am doing an Active design with it now. Very neat chip. Primarily using it for the powerquad section.The active power consumption is quite good. The 1st parts were 96MHz. 3mA. I had both cores running and the power quads doing continuous FFT and I got @5mAOne aspect to all of the LPC devices that I live is a bootloader in rom that works over many of the interfaces. I.e. SPI, I2C, serial, USB, etc

author: bson
author_rank: Unknown
timestamp: November 23, 2019, 05:45:05 pm
content: Quote from: ataradov on November 23, 2019, 02:34:25 amMaybe, but I downloaded the user manual first thing.One annoying thing with NXP documentation is they use tables for pinout instead of drawn packages. So the first thing I end up doing with their processors is get it into a spreadsheet, then use KiPart to generate footprints and print those. The actual pin layout matters to create a pin plan, and for evaluation it matters to make sure a sensible pin plan is possible. They really should start putting graphical pin layouts in the datasheets. I don't care if it doesn't look neat, I care that I don't have to sit and do it myself. Or at least let me download the pin list as a spreadsheet without copy-pasta from their PDFs (which are frequently inconsistently formatted to boot). And then spend 45min cleaning that up into a csv.Their I2S master implementation is still unusable. While they provide a DMA-filled FIFO in the Flexcomm block, they still can't clock it using an external sample clock and insist on having to generate the clock themselves. Which still makes their efforts look laughable next to XMOS. Not holding my breath for them (and many others) to one day figure out I2S needs to exist in a different, external, clock domain and the job of the on-chip peripheral is to interface it to the µC's clock domain. The coin is truly stuck on this one!I think the secure CM33 features are interesting, but I guess it depends on whether one finds secure devices, secure comms, and security in general to be an interesting problem.

author: up8051
author_rank: Frequent Contributor
timestamp: November 23, 2019, 07:03:04 pm
content: Quote from: bson on November 23, 2019, 05:45:05 pmI'm also interested in uP with USB HS PHY and I2SI never used LPC chips but in "User manual UM11126" table 675 we can find:MCLK I/O MCLK Master clock. A multiple of the sample clock can optionally be provided bya master to other devices in the system, or can be received and divideddown within a Flexcomm Interface to locally generate SCK and/or WS.This clock is not created inside the I2S block. If MCLK is supported as aninput to the device, it can be routed to the I2S block and used to operateits functions. If MCLK is an output from the device, the clock that is usedto create that MCLK can also be routed to the I2S block and used tooperate its functions.So, can I2S Master work with an external master clock or not?

author: Bassman59
author_rank: Super Contributor
timestamp: November 23, 2019, 07:10:34 pm
content: Quote from: ataradov on November 23, 2019, 02:34:25 amThey haven't figured out yet that they have a database of junk accounts.

author: iMo
author_rank: Super Contributor
timestamp: November 23, 2019, 07:14:52 pm
content: Be sure there are people get paid for achieving certain number of new junk accounts per quarter (I've seen similar KPIs once at a TLA company).

author: bson
author_rank: Unknown
timestamp: November 24, 2019, 06:23:23 pm
content: Quote from: up8051 on November 23, 2019, 07:03:04 pmThe whole µC can use an external clock. However, it's a clock domain bridging problem; USB has specific clocking needs, I2S has specific clocking needs, and they're not multiples of one another. You can't produce one from the other. In addition even if it were possible, if the system PLL used to derive the USB clock (40MHz) is restarted because you switch external clocks (and run off the internal RCO while doing so), you'll fall off the bus and have to reattach.

author: up8051
author_rank: Frequent Contributor
timestamp: November 24, 2019, 07:45:34 pm
content: Quote from: bson on November 24, 2019, 06:23:23 pmI found in the User Manual:If I2s is present in Flexcomm we can select MCLK_IN clock (from I/O Pin) as a source for I2S.