Solved

Posted on June 27, 2016 at 22:53So I've spent two entire days trying to figure out why STM32CubeMX v4.15.1 would not generate my project properly (which had been working under v4.14).  It would totally mess up an existing project, would not create the startup assembly file, and my TrueStudio project would no longer compile any of my application-specific code. I finally figured it out (sort of), but have no explanation for why this worked.  I already sent this information to Atollic (although it is ST's problem), and I will repeat it here:I finally figured out what was wrong (sort of) by comparing two different .ioc files.  One was from a project that worked, and the other was from my non-working project. There was no Toolchain Location specified in the non-working .ioc file, although it was properly shown in the Settings dialog (go figure).  So I copied the information from the working project to the non-working project.The working project had a line in this form

Posted on October 19, 2016 at 06:03Hi!Attached stm32f4xx_hal_i2c.c is from stm32cube_fw_f4_v1131.zip. line 657,       if((__HAL_I2C_GET_FLAG(hi2c, I2C_FLAG_BTF) == SET) && (Size != 0U)) It looks better to be hi2c->XferCount or hi2c->XferSize, than Size.regards, ---------------------------       /* Write data to DR */       hi2c->Instance->DR = (*hi2c->pBuffPtr++);       hi2c->XferCount--;       hi2c->XferSize--;      if((__HAL_I2C_GET_FLAG(hi2c, I2C_FLAG_BTF) == SET) && (Size != 0U))       {         /* Write data to DR */         hi2c->Instance->DR = (*hi2c->pBuffPtr++);         hi2c->XferCount--;         hi2c->XferSize

Posted on October 28, 2016 at 15:26Hey, I have some trouble configuring my camera interface. I am using an analog NTSC camera with differential data lines. For decoding it into digital YCbCr 4:2:2 I am using the Intersil TW9990. I think I configured it more or less right because I am receiving VSYNC, HSYNC and data. Only I am not sure because I have the possibility to crop the image with the TW9990 too. And also I don't know if the vsync and hsync lines must be active all the time during transmitting active lines/pixels. Does anybody of you know it? Because I can't find any good description for the DCMI interface. So now configuring my STM32F746 Discovery Board to continue with these received data. I want store the data via dma in the external sdram. I know I am receiving 8 bit data by each pixel clock. Can I configure the dma as followed? /*** Configure the DMA ***/   /* Set the parameters to be configured */   hdma_handler.Init.Channel      &n

Posted on October 05, 2016 at 12:54Hi Can someone advise me what the ERP (Radiated power) produced from the M24SR64 device through its antenna. I know it will be very low as it is a passive device but if ST or someone has some figures that would be great.ThanksAndrew #thanks

Posted on August 13, 2016 at 17:00HAL_DMA_RegisterCallback(DMA_HandleTypeDef *hdma, HAL_DMA_CallbackIDTypeDef CallbackID, void (* pCallback)(DMA_HandleTypeDef *_hdma))These are the parameters I am using in my code:HAL_DMA_RegisterCallback(&hdma_dac1, HAL_DMA_XFER_HALFCPLT_CB_ID, MyDmaDac1Callback)Getting errors on this line no matter how many times I try to alter the parameters.Does a practical real-world code example exist to guide me on the proper syntax for this function? Can anyone offer some assistance?Thanks,Christopher #hal-callback-dma-register

Posted on March 23, 2016 at 11:57I test with 24LR04e-discovery board..Use CR95HF demo board to set EH enable-03,and EH Config-F3. Put board near wire and the board can display message. But if I set F0 and mean max 7mA. It is very difficult to drive the board message display. I measure the VDD output and always about 0.5V. Why set max current higher not better ? How can i set to output more current to 7mA?  thanks #m24lr04e

Posted on October 11, 2016 at 15:14Hello,I am having problems with UL-C authentication command (0x1A 0x00). CR95HF always responds with 0x87 (timeout) instead of 0xAF. Beside that everything else works fine.Does anyone have working code for authenticating UL-C?Sanjin

Posted on October 10, 2016 at 12:42Hello, I am trying to create an application SW using M24LR-DISCOVERY using RF transceiver board to read devices containing M24LR dual eeprom, but I am struggling to get the documentation to implement functions like the M24LR-DISCOVERY SW has like auto-detect, read memory from - to.... etc. The only documentation I've found are AN3375  Application note and AN3163 Application note. Is there any docs explaining which function and which parameters I need to use to get any result. example: detect and read from EEPROM address 0x15  - CR95HFDLL_USBconnect()  - CR95HFDll_SELECT()  -  CR95HFDll_SendRec() Thanks, Sasa

Posted on October 04, 2016 at 22:01I have been struggling to set up CubeMX to be able to read and write to a USB memory stick for STM32F4-Discovery board, similarly to what is done in the example from the repository (Repository\STM32Cube_FW_F4_V1.13.0\Projects\STM32F4-Discovery\Applications\FatFs\FatFs_USBDisk). This example from ST is working perfectly.My setup procedure is as follows: Set RCC to High Speed Clock (HSE) with Crystal/Ceramic resonatorChange the clock configuration to HSE, M=4,N=x168,P=2, Q=7, so that PLL clock is 48 MHzSet USB_OTG_FS to Host_Only with Activate_VBUSSet USB_Host to Mass Storage Host ClassSet FATFS to USB DiscSet USB_Host configuration, Platform settings MSC_FS, Drive_VBUS_FS to GPIO:Output through PC0.After generating the code I &sharpinclude the fatfs.h in usb_host.c in order to be able to use the functions defined, similarly to what is done in main.c for the original example. Next the private variables (FATFS USBDISKFatFs etc) and the ''MSC_Ap

Posted on October 05, 2016 at 06:28Hi Sir / Madam,I receive error code from ST95HF :  0x87  0x01  0x90  ,   may I know what does this means  ?There is no explanation on the above code.  The explained code in ST95HF datasheet DoclD025630 Rev4  is only 0x87 0x00.  Which means timeout or no tag, meaning no acknowledge or No Acknowledge being send back.    Please help soon.Thank you very much.Cheers,kf #nfc

Posted on October 12, 2016 at 10:23Hello, Found mistakes for SYSCFG_MEMRMP register in many stm32f4 headers using last Cube F4 1.13.0 /******************  Bit definition for SYSCFG_MEMRMP register  ***************/   #define SYSCFG_MEMRMP_MEM_MODE          0x00000007U /*!< SYSCFG_Memory Remap Config */ #define SYSCFG_MEMRMP_MEM_MODE_0        0x00000001U #define SYSCFG_MEMRMP_MEM_MODE_1        0x00000002U #define SYSCFG_MEMRMP_MEM_MODE_2        0x00000004U SYSCFG_MEMRMP register should be aligned and updated as defined in RM0090, like this : /*** Bit definition for SYSCFG_MEMRMP register ***/ #define SYSCFG_MEMRMP_MEM_MODE 0x00000003U /*!< SYSCFG_Memory Remap Config */ #define SYSCFG_MEMRMP_MEM_MODE_0 0x00000001U #define SYSCFG_MEMRMP_MEM_MODE_1 0x00000002U ********************* Thanks

Posted on June 24, 2016 at 16:28 Hi there, I have some troubles with initializing my LCD with a HX8347-Controller. I have my Environment and all Settings generated with the actual Cube. I use FreeRTOS on a STM32F4 The LCD is with FMC on BANK1, NOR/.../LCD 2 connected and configered. I added also the additional Reset-Pin. The Background-LED is turned on, so that I should see everything. The Clocking is active. Because of wish to later use emWin, the Configs (Templates) for STemWin are used. Mostly all of the simple Stuff is taken from the Templates and addapted. The CRC for emWin is also active. in the GUIConf.c I changed #define GUI_NUMBYTES XSIZE_PHYS * YSIZE_PHYS * 2 in LCDConf.h I added #define XSIZE_PHYS 240 // To be adapted to x-screen size #define YSIZE_PHYS 320 // To be adapted to y-screen size In GUIConf.h I reduced to 1 Layer and removed Support for Touch+Mouse. And now the real Thing, which should be also there in a similar Way without emWin: in

Posted on September 22, 2016 at 20:33I have the development board for the STM32L073 and have been testing the functionality of the board regarding waking up from STANDBY mode. I have been able to get it to wakeup only use the IWTG funcitonality. I have NOT been able to get it to wakeup from a WKUP pin rising edge or an RTC wakeup event. I believe that I have it configured properly: - System Wakeup 1 is being used (pin PA0) - RTC Wakeup clock is set to RTCCLK / 16 (using 37k LSI oscillator) --> Wakeup counter set to 11563 (approx. 5 seconds) --> RTC global interrupt enabled Am I missing something in the configuration using CubeMX? Is there some code that I need to write in addition to what is generated? The only code the I have in the USER CODE BEGIN 2 section is the following: HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, GPIO_PIN_SET); HAL_Delay(2000u); HAL_PWR_EnterSTANDBYMode(); So I am expecting the green LED to come on for 2 seconds, off for 3 seconds, and keep repeating, but the gr

Posted on September 26, 2016 at 12:38Hi,we are using ST95 HF NFC transceiver with XRCGB27M120F3M00R0 27.12 MHz crystal. So far, we manuufactured about 30 modules and all works well. However, we are planning a bit larger series in a close future (10k+) so we would like to be sure everything will work fine in whole operating range. Currently, we have concerns regarding a crystal specification.In datasheet (p 59) it is stated that with a crystal of ESR equal to 30 ohms, rated load capacitance should be 6pF, and also that used load capacitors should be in 10 to 20 pF range.If a crystal ESR is 5 times larger (150 ohms), does that mean that rated load capacitance should also be larger (and how much) in order to keep compatibility with embedded oscillator?We are using mentioned crystal that has 150 ohms ESR and load capacitance of 6pF. We are expecting about 5 pF of stray capacitance (including pin and PCB stray capacitance), so we are using 6.8pF load capacitors. Could this also be a p

Posted on September 01, 2016 at 11:52Hi, Putting the CR95HF into sleep mode I note that the current reduces to 1.001mA.  Putting it into hibernate mode 0.998 mA.  This is a factor of ten higher than the spec sheet quotes. I'm using the example instructions given in the spec sheet eg. 0x07 0E 08 01 00 38 00 18 00 60 00 00 00 00 00 00 and regardless of which instruction (there are examples for Sleep/Hibernate / IRQ_IN wake up SS wake up, timed wake up) it definitely seems to reduce the power considerably, but only to around 1mA. Tried this on two prototypes and both the same.  After much head scratching, now considering the possibility of out of spec devices / counterfeits etc. I'd be grateful for any better ideas. Regards Bernard McIntosh

Posted on September 22, 2016 at 12:17Hello,Can nfc03a1 read/write the tag m24lr. In the datasheet of CR95Hf; it says that ISO15693 tags are supproted and forum tag types 1,2,3,4 as well. M24LR belongs to Forum tag type V and it supports ISO15693. So I could not make sure that can I use CR95hf as transciever for m24lr tag.Thanks in advance.Kawthar 

Posted on September 16, 2016 at 13:44Hello,I'm trying to communicate with a Mifare classic card but I can't.I'm following the example described on the datasheet (page 60) and when it comes to auth, I'm sending the command:0x04 0x09 0x60 0x00 0x04 0x00 0xd1 0x00 0x3d 0x00 0x18But the answer is alway the same: 0x87 0x00I've tried modifying the frame waiting values, but the error persists.Any idea?Thanks in advance! #cr95hf-st95hf

Posted on September 22, 2016 at 12:51Hi all; I am trying to comunicate with an external flash memory with my STM32F429. I can see my signals in the oscilloscope . I see how my microcontroler starts the clock and write to the bus but the NSS signal do not change. It is always at LOW level. This is a problem with this flash beacuse it uses NSS signal to sincronice data. I have configure the SPI5 chanel with the following code:   hspi5.Instance = SPI5;   hspi5.Init.Mode = SPI_MODE_MASTER;   hspi5.Init.Direction = SPI_DIRECTION_2LINES;   hspi5.Init.DataSize = SPI_DATASIZE_8BIT;   hspi5.Init.CLKPolarity = SPI_POLARITY_LOW;   hspi5.Init.CLKPhase = SPI_PHASE_1EDGE;   hspi5.Init.NSS = SPI_NSS_HARD_OUTPUT;   hspi5.Init.BaudRatePrescaler = SPI_BAUDRATEPRESCALER_128;   hspi5.Init.FirstBit = SPI_FIRSTBIT_MSB;   hspi5.Init.TIMode = SPI_TIMODE_DISABLE;   hspi5.Init.CRCCalculation = SPI_CRCCALCULATION_ENABLE;   hspi5.Init.CRCPolynomial = 7

Posted on September 20, 2016 at 00:41 I am trying to change the sector security status of my RF sectors in I2C mode using the provided m24lr drivers, but it’s not working. Below is my code: M24LR_SECTOR_SEC sss_write; M24LR_SECTOR_SEC sss_read; // unlock sector sss_write.SectorLock = 0; // use first password sss_write.PassCtrl = 1; // cannot write without password sss_write.RW_Protection = 0; NFCTAG_StatusTypeDef status = NDEF_OK; uint32_t password = 0; // present password status = BSP_NFCTAG_GetExtended_Drv()->PresentI2CPassword(password); wait_ms(1000); for (int i = 0; i < 4 ; i++) { status = BSP_NFCTAG_GetExtended_Drv ()->WriteSSSx((uint8_t)i, &sss_write); BSP_NFCTAG_GetExtended_Drv()->ReadSSSx((uint8_t) i, &sss_read); } I first present the I2C password, which should be 0 because I haven’t changed it since receiving it. Afterward, I use the m24lr functions to write/read each sector’s SSS. However, even though the code runs and the status is alwa

Posted on September 16, 2016 at 22:11Hello, I really need the STM32F746G-DISCO display (RK043FN48H-CT672B) datasheet. (Not only source code of CubeMX firmware) I contact ROCKTECH and ST without success. Can someone send me this datasheet ? Thanks in advance #rocketeck-rk043fn48h-ct672b-lcd #stm32f746g-disco-rocktech

Posted on August 18, 2016 at 07:58Hi, we're using the MB1054A board for reading ISO 15693 tags and it works OK.the problem occurs after immediate power down- we are facing problems with initiation.The OS on the PC is Win-10 and we're not sure the CR95HF.dll is the same used on the application SW. how come when shut down the PC and power up again, and then open again the application SW everything is working OK?Do ST supply source code example for the PC side? 

Posted on August 25, 2016 at 15:59I am guessing that the HAL lock and unlock mechanism prevents this from happening.Does anybody have any ideas or suggestions to make simple writes to peripheral registers work again like they did in SPL? (example - GPIOA->ODR = 1;) #synth-usb-midi-nucleo-144 #synthesizer-nucleo-144-f7 #hal-direct-write-peripheral-regs

Posted on August 11, 2015 at 12:12Hi, I'm using the M24SR Discovery Board and I'm having some trouble when I want to communicate with the board via NFC. I'm trying to open a RF session with my Smartphone so that the GPO of the M24SR is driven low. Then I want to read some values out of the EEPROM and after that I want to close the session again (Deselect). Sounds easy, but I really do not get it how to send the right command for open session and deselect. My other code looks like this: //Select NFC T4 application                     iso.transceive(global.getT4select());                     //Select NDEF file                     iso.transceive(global.getNDEFselect());       

Posted on April 25, 2016 at 09:05Hi,  Is there any sample Android code for anti Collision for 24LR mult-bank design ? I want to use multi bank increase memory size for the tag(one 64k bit is not enough) and read/write from my Apps and can't found any reference code in all ST apps program. Please advise and thanks. #24lr

Posted on July 26, 2016 at 12:31Hi,in my project I'm using a CR95HF to read some M24LR memories. Communication between my microcontroller and the CR95HF is UART. I cannot find on the device's datasheet the description of how to read multiple block.Protocol used is 15693. Has anyone tried something similar?Regards,Mattia Dell'Oca #cr95hf-iso15693-multiple-block