±1 LSB INL; no missing codes. – Programmable throughput up to ksps. – Up to 17 external inputs; programmable as single-ended or. CF Datasheet PDF Download – Full Speed USB Flash MCU, CF data sheet. Explore the latest datasheets, compare past datasheet revisions, and confirm part lifecycle. Preview and Download. Download Datasheet CF

Author: Zolozshura Malkree
Country: Estonia
Language: English (Spanish)
Genre: Video
Published (Last): 21 July 2005
Pages: 154
PDF File Size: 5.57 Mb
ePub File Size: 7.51 Mb
ISBN: 336-6-15963-135-6
Downloads: 7741
Price: Free* [*Free Regsitration Required]
Uploader: Marn

Well the copying itself works well I looked up at the flash memory and it saved my data right datashwet If I now disconnect my uC and connect it again in like 5 secs, the data is still there. Now as in the data sheet described I save all the data in between the addresses 0x – 0x I have can CF Microcontroller from Silabs.


By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies. But if I leave it disconnected any longer my data gets more or less “resetted” – that means it gets everytime almost the same “reset values”. It compiles without problems, but like i already said, it has problems with passing the function parameters Only then you can write to it.

Toby 1, 10 36 I wrote a little Interface which stores Information in the non-volatile flash memory from the uC. Normaly, erasing done by sectors.


Not sure why your stepping into function call would how the wrong parameter. Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.


Sign up or log in Sign up using Google. You should datasheey an address toward the top of your flash memory, like 0xF Okay that link to the application note from silabs helped.

Down there I tried to implement the example for the F into my code. I mean isnt the flash data non volatile or did I get something wrong?

I use the example functions from the AP for the F Make sure that memcpy internally use it.

Sign up using Facebook. But if you want to write to it, you have to the first of all erase it set all bits to 1. Is there any way? They called erase sectors. By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.

Yeah youre right, 0x was not the best idea, but according to the datasheet and the AP 0x should be right. Actually you helped me a lot in making progress – I still have some weird problem left. I mean there can only be one address 0x?! Maximum that you can – read from it as from normal memory only if you have NOR flash.

I don’t know why that is??? You can not just write to it. However I question your use of 0x for a Flash address to use for data, that would normally be right in the middle of where your code is placed, unless you have modified your linker script.


Stack Overflow works best with JavaScript enabled.

Based on the code you displayed in your question, you are trying to write to external data xdatawhich is RAM, not non-volatile flash memory. Yea according to the datasheet I need to unlock it there is a procedure described there but how do I pick a dxtasheet

(PDF) C8051F340 Datasheet download

Email Required, but never shown. Re your question re the MOVX instruction, the app note says: Acording to datasheet of your CPU, to write you have to use special instruction.

Post as a guest Name.

Sign up using Email and Password. See datasheet of your microcontroller about their size. To copy my data there I just use memcpy. If I call the function like its designed it doesnt work – if I make a global variable to “pass” the function arguments it works To write to flash memory, you need to follow a specific protocol to unlock the flash programming circuitry, then erase the area you will be writing to, and then write the bytes using MOVX instructions as described in Section 12 of the datasheet.

The reason the data disappears after a few seconds, is the power supply capacitor still powers the chip long enough to keep the internal RAM alive.

Back to top