Big-Endian

I don't think so, but I've never used the LPC11xx series. What did the data sheet for the LPC11C35 say? That's the first place I'd look.

We want to use big-endian format at our variables.

Even though your CPU is little endian, you can still do it. Simply explicitly convert the value to big endian every time you save it in a variable.
But why would you want to do it? Surely you can ask your question in a more meaningful way?

Dear Jonathan,

thank you for your time.

i had already looked at the datasheet and found __REV and __REV16 instructions that reverse the endian. The thing is that i do not want to do it programmatically because bugs might occur.

Dear Mike,

i don want to do such thing programmatically in order to avoid bugs. We need the big-endian format because the device is a part of a network that uses RS485 communication with big-endian format and it is easier and safer to have just another big-endian device than converting data all the time.

Thank you for your time.

Dear friends,

I needed to build a man door with arm.I searched rfid shields butthat work from 10cm distance which is too small. then I looked after other rfid reader/tag solutions not for people, and I could not find anything. I know that rfid technology is close range technology but I cannot attach a heavy and large object that includes batteries onto man's collar. there are these kind ofsolutions for dogs but they are mush more powerfull than men.

any suggestions about which kind of technology should I use ? I guess minimum 25-30 cm would be required to sense the "specific man with collar".

thanks.

That's a strange argument. I think you are overestimating the complexity involved in endian conversion. People use ntohs/htons/ntohl/htonl all the time, it's nothing new. The good practice would be to test all the parts of the protocol anyway, be it big endian or little endian.
If you insist on a big endian CPU, have a look at ColdFire. They have a very nice range of MCU's.