Solved

Posted on June 11, 2014 at 23:06Hi, I am familiar with Standard Pheripheral Library on STM32F100 MCU. ==== The problem is that on nucleo-053 (SPL is not available for this MCU) I cannot make USART working properly. I generated the code using CubeMX 4.2 (USART2 enabled, NO parity, 1 stopbit, 8 data bits). When I use the following piece of code:     uint8_t pData[40];     int k;        for(k=0;k<40;k++){pData[k]=48+k;}     HAL_UART_Transmit(&huart2, pData, 40, 10); only numbers and @ are sent correctly. Letters ('abcd', etc ) are displayed as if they have extended ASCI codes (extra bit was added in front of the original code making it extended code). I know that for 9B & parity the HAL driver plays this way. But it's not the cae, I guess (no 9B & parity). I do not use physical uart port - Virtual COM is used (ST-link 2.1 feature). === Anyway, could you please share USART code example for nucleo-L0

Posted on June 25, 2014 at 22:55At: http://www.st.com/web/en/catalog/tools/FM147/CL1794/SC961/SS1743/LN1898/PF260788 in 'Get Software' section, when we click 'Download' we get the 'stm32snippetl0.zip' (15.1MB file) which contains inside the CubeL0 INSTEAD of the snippetL0. #stm32snippetsl0

Posted on June 23, 2014 at 09:24Hi, Maybe stupid question... Is this possible to upgrade the STM32VLDiscovery debugger firmware to the latest ST-LINK v2.1 or at least v2 version? Bogdan

Posted on June 11, 2014 at 14:55 Hello, I'm trying to create new project (Starting Code Generating) with SPC5 Studio Version (2 or 3) for SPC56B/Cxx Series. But It doesn't generated. SPC5 Console Out: Begin processing component resource com.st.tools.spc5.components.platform.spc560bcxx_1.0.0.201405131114/component/root_wo/ > Processing main.c > Processing debug.wsx > Processing stm_xpc560b_minimodule_debug_jtag.cfg > Processing user.mak Begin processing component resource com.st.tools.spc5.components.platform.spc560bcxx_1.0.0.201405131114/component/root_wa/ > Processing application.ld.ftl Error: Expression conf.instance.runtime_settings.irq_stack_size.value[0] is undefined on line 28, column 29 in application.ld.ftl. Error: FMPP processing session failed. Error: An error occurred while generating component SPC560B/Cxx Platform Component Begin processing component resource com.st.tools.spc5.components.platform.spc560bcxx_1.0.0.201405131114/component/cfg/ > P

Posted on June 11, 2014 at 22:54Hi, I used CubeMX 4.2 to generate code skeleton for L053. I have no problem with simple programs (LED blinking, etc). But I cannot use systick. I understand that HAL_init() takes care of setuping the systick. Unfortunately HAL_GetTick() does not return updated values. It seems that the systick interrupt is not initialized/enabled. Could you please share working examples for L053? I have no such issues using Standard  Pheripheral Library on STM32F10x MCUs. Thanks, Bogdan

Posted on May 26, 2014 at 23:23What is the recommended way to mange simultaneous I�C and RF data transfers with M24SR IC and 2 Host MCU & NFC Phone?I have implemented mechanism with time Slice , so that each Host has time window to communicate with the M24SR , but still have some issues to resolve , such as the size of Time Slice , number of retry etc. if anyone has better idea i will appreciate very much .  #m24sr #session #rf #rf-session #gpo #i2c #i2c #m24sr

Posted on June 02, 2014 at 15:00Hello, in my last project I changed the eeprom to the M24LR64E. Now I want to creat an expansion device with an reader Ic. Which ic is the best/easyest for the data connection of the two devices.thank you and greetings from Germany #m24lr #reader

Posted on May 05, 2014 at 15:37Hello, I am using your stsw-m24sr001 firmware with a M24SR (from the M24SR matrix antenna) and a STM32F4-discovery with a STm32F407VG. I have many problems to use the functions of lib_ M24SR.c. When I use the M24SR_Initialization(), the program always stops here in the drv_I2C_M24SR.c :   while ((!I2C_CheckEvent(M24SR_I2C, I2C_EVENT_MASTER_TRANSMITTER_MODE_SELECTED)) && M24SR_Timeout)/* EV6 */   {     if (--M24SR_Timeout == 0) goto Error;   } I found by uncommenting  &sharpdefine USE_FULL_ASSERT    1 in the stm32f4xx_conf.h I fixed the problem but I don't understand why. I think this could be a question of delay but i'm not sure. Can you give some details ? Thx #debug-mode #m24sr

Posted on May 23, 2014 at 19:21Can anybody offer any knowledge of using STANDBY mode?  I am putting the chip in STANDBY and it appears to go there, as the processor goes dormant until I cause a wakeup event.  But the current draw on the VDD_LV power-input (2.1v) is ridiculously high (~100ma).   I've confirmed that the power is not going out the ports - those are all ok - it appears to be going to core/peripherals (hence VDD_LV).  Following the spec carefully, with weeks of scrutiny and experimentation.   Can give more details if anybody has experience here... tnx, -mark #powerconsumption-power-standby

Posted on May 22, 2014 at 14:11Hi ST guys,On NDEF spec, the Read and Write access byte is 0x00 and 0xFF.The 0x80 is ST proprietary ? any other company can use it ?Thanks.--Ten  #ndef

Posted on May 06, 2014 at 11:42Detecting the presence of tags with the CR95HF works fine. But is it possible to detect the removal of a tag within the antenna field? I was thinking about polling the Tag Detect command with a very short timeout. As long as the wakeup event is ''tag'' and the timeout doesn't occur the tag is still present. But for my application power consumption is very important, meaning I want to stay in Sleep as long as possible. What�s the best way to implement the detection of a tag removal? #cr95hf #cr95hf #cr95hf-iso15693 #tag-detect #an3433

Posted on May 14, 2014 at 15:03Hello,I wish to use the M24LR16E as a NFC tag. In order to do this I have an ANT1-M24LR16E, a CR95HF and an Aardvark for the I2C communication.With the M24LRxx_Application_Software I send a text through the RF (with the CR95HF) and then I am trying to change this text through the I2C with the Aardvark.The batch code below:<aardvark>  <configure i2c=''1'' spi=''0'' gpio=''0'' tpower=''1'' pullups=''1''/>  <i2c_bitrate khz=''400''/>  <i2c_write addr=''0x53'' count=''2'' radix=''16''  >  00 00</i2c_write>  <i2c_write addr=''0x53'' count=''4'' radix=''16''  >  E1 40 FF 05 </i2c_write>  <i2c_write addr=''0x53'' count=''4'' radix=''16'' >  03 09 D1 01</i2c_write>  <i2c_write addr=''0x53'' count=''4'' radix=''16''  > 05 54 02 65</i2c_write>  <i2c_write addr=''0x53'' count=''4'' radix=''16''  > 6E 64 61 FE</i2c_write&gt

Posted on May 06, 2014 at 16:49Hello,I am searching for XPC560BADPT208S mini module realated docs, but i can't found it, any help of any related docs is higly appreciated. 

Posted on May 13, 2014 at 15:41Seen things crash a couple of times, all the post information seems broken, either not displaying the correct last poster, or being off by at least one.

Posted on April 23, 2014 at 11:19Hi, can I disable the RF field of the M24SR by writing a 0x00 in the 0x06 offset of the system file 0xE101? Do I need to send any password-related command before? Can anybody please the NAK question in [DEAD LINK /public/STe2ecommunities/memories/Lists/M24SR%20Series/Flat.aspx?RootFolder=/public/STe2ecommunities/memories/Lists/M24SR%20Series/Cannot%20write%20M24SR%20after%20MCU%20read&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000ED3A9C6410AD9C49B9619F3BDE3D015F&TopicsView=https%3a//my.st.com/public/STe2ecommunities/memories/Lists/M24SR%2520Series/AllItems.aspx&currentviews=42]this link? Thanks, I will be waiting for your answers. #password #i2c #m24sr

Posted on April 02, 2014 at 12:27Hi, as [DEAD LINK /public/STe2ecommunities/memories/Lists/M24SR%20Series/Flat.aspx?RootFolder=/public/STe2ecommunities/memories/Lists/M24SR%20Series/M24SR%20-%20mistake%20in%20table%2067%20Datasheet&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000ED3A9C6410AD9C49B9619F3BDE3D015F&currentviews=84]somebody commented, there is a mistake in the M24SR's datasheet. In Figure ''NDEF tag Application Select Command'' a 0x04 is missing between 0xA4 and 0x00. In addition, there is another one in the last byte of the time flow. Last bytes have to be 0xF1 0x09. These two errors are present at least in my version of M24SR02-Y. Have a nice day. #m24sr #an4433 #datasheet-error #ds #m24sr

Posted on January 23, 2014 at 11:23Hi, I'm trying to achieve the maximum reading range from my demoboard CR95HF-A with a ISO 15693 tag (LRi2K). Until now I've obtained best results with modulation-index 10% and gain 34dB by writing 0x50 to ARC_B register: only 5 cm. Can I improve this result? How Can I increse the antenna current? Thanks in advance. #range #lri2k #lri2k #lri2k #lri2k #lri2k #demo-cr95hf-a #cr95hf-firmware #cr95hf

Posted on March 17, 2014 at 12:24Hi all, I'm looking for an indication of worst-case time-to-ready: i.e. from power-up - assume external VCC, not induced power - to fully commandable from I2C. I've searched the datasheet (DocID022208 rev 8) from end to end, and probably missed the obvious, but can't find the number I'm after. What did I miss? Anyone got a figure for it? Thanks in advance, Jon #m24lr04e-r #por #por #m24lr04 #m24lr #i2c #power-up #i2c-access #time

Posted on March 20, 2014 at 10:58Hi everybody!It's my first post here and it's my first time working with STMicroElectronics stuff so please be aware I will probably ask very simple or even stupid questions. Please have some patience with me! :)By the way, I just received my M24SR antenna suite. It is nice :) In their initial state, I can write and read all M24SR tags in there by using the NXP TagWriter Android Application. No problem, several times, everything is ok.However, when I solder some headers to the boards. I can only write it down once, and then when trying to read it says ''this item is used, blocked, or not supported and cannot contain an NFC data set''. I feel strange about this, since I have not even messed with passwords and so on. The soldering is nice and this happened with two different boards.So, what I'm not taking into account? My plans are to interface a M24SR to an external MCU (microcontroller) so for first steps I need to wire some of this headers.Ok, let me

Posted on March 19, 2014 at 13:44First of all: I really like the software for DEMO-CR95HF-A. But there is an issue with the scripting tool: The command CR95HF_ISO14443-A_SEND_APDU, 00A4040007a0000000030000 should be translated intoCR95HFDLL_SENDRECV, 0200A4040007a0000000030000CE2008 (or 0200A4040007a000000003000028). But the scripting tool translates it intoCR95HFDLL_SENDRECV, 0200A4040007a000000003000008 with the CRC missing! Please fix this within version 1.7. Thank you! #cr95hf #software #bug #demo-cr95hf-a #crc #cr95hf

Posted on March 10, 2014 at 17:29Hi,I am sending this message because I am facing an issue using the M24LR16E-R.My i2c communication between my microcontroller and the M24LR16 chip works perfectly (I am able to read and write the entire memory multiple times with no problem) when no RF field are present.But when a reader becomes in range of the M24LR16 during a write, the M24LR is continuously answering NAK to all the message (even if I remove the reader !)The functioning of the write procedure is a polling on the device with only Start (no STOP until I get a ACK) (As specified in this documentation �3.1 (http://www.st.com/web/en/resource/technical/document/application_note/CD00247968.pdf%29)Note :-          No RF command is apply, the only fact of approaching the reader creates the issue-          Reducing the i2c speed doesn�t change anything-        &nbs

Posted on March 06, 2014 at 14:50Hi, We have a custom board made using M64LR64E. Using an android phone, without powering up, will the EEPROM work directly as a NFC tag? Or should it be programmed/ configured first using I2C? We are unable to detect as NFC Tag. We are using smd inductor for antenna and don't have 4.7uH inductors presently and are using a 6.8uH. Is this the reason why it is not working? How do you check the functioning of the memory over RF for the first time? Thanks Murali #m24lr #m24lr #rf #inductor #memory #antenna

Posted on March 05, 2014 at 21:04Hi. I am using CR95HF. I need to identify the presence of multiple  iso15693 tags ( placed on the same time ). I need to know how the amount of tags only. Is ther a command or algorithm ?. Please Advise. Ephraim Oved #cr95hf-iso15693 #m24lr #cr95hf #multi-tag #collision

Posted on February 25, 2014 at 21:26 Update: It looks like you do have to send the write password with the verify command before calling the enable or disable verification commands when modifying either the read or write permissions. You can then change the password with the change reference data command for either permission after verifying the write password again. If I understand correctly, the only time you would need to send the read password via the verify command is when accessing a NDEF file that has the read permission verification enabled. Hopefully someone can clarify this. The only other issue I am experiencing is that even when read and write verification is disabled (CC file reports 0x00 for both), the M24SR Demo android application says that a password is required when trying to lock read or write access under tools within the application, but not when actually reading or writing to the NFC tag. Strangely, when trying this with another M24SR that has never had file p

Posted on February 17, 2014 at 09:54hi , 1.what is the page size in M24SR-16  ?  in the datasheet its declared  that    write time for page in I2C = 5ms , write time for up to 264 bytes =150ms 2.Is it normal after writing 5 bytes to the  M24SR , i am getting Frame extension of               2*9.6ms ?3.when authenticating using password in order to gain Read / Write Access , does it much    time as writing 16 bytes ? #fwi #m24sr #i2c #m24sr #ndef