11 years, 4 months ago.

LPC11U36 compatility

I've done some projects with the LPC11U24 now, and one thing that I notice,
is that I have to do my programming non-sloppy (I'm no PRO programmer, everything is Google-taught).

I found the LPC11U36 from NXP, with flash size 96 kB, instead of the 32 kB the LPC11U24 has.

Would the compiler be able to compile directly for this MCU, or does it need some setup?
In this case, would I be able to do it in Keil?

I could of course just test the MCU out by buying one, and throwing a .BIN at it,
but if any of you have an answer, this would be easier.

Thanks in advance.

Lerche

4 Answers

11 years, 4 months ago.

Also on LPC11U36 you will have 10 kB RAM instead of the 8 kB in LPC11U24. But because mbed online compiler initializes the stack pointer to the top of the 8 kB RAM, this shouldn't be a problem. You just won't be able to use the remaining upper 2 kB for variables defined in the mbed online compiler. You can of course then still access that space by using pointers to absolute addresses.

Best regards
Neni

Accepted Answer

sorry, my bad, i looked up the wrong device number. LPC11U24FBDxx have also 10 kB SRAM. Only FET48 and FHI33 have 8 kB.

posted by Nenad Milosevic 10 Dec 2012
11 years, 1 month ago.

- Thanks guys. Now that the compiler is completely opensource, would it be possible to add the U36 support? (Easily that is, compiler-thingy-support is NOT my strong side), I'm more of a hardware-dude.

11 years, 4 months ago.

I expect the .bin will work as is, but you won't be able to get the online compiler produce code for 96KB ROM, as it does not have a setting for LPC11U36. Keil should work, though.

10 years, 2 months ago.

I tried the LPC11U37 in Keil, but becuase I was using the evaluation version, the linker wouldn't allow me to compile. So far, I've used the LPC11U35 as a target (64kB instead of 128kB on the LPC11U37), and it runs the code, though we lose half the flash space.