Skip to main content
jasonp4113
Associate III
September 22, 2014
Question

STORAGE_IsReady_HS() function contains garbage

  • September 22, 2014
  • 3 replies
  • 852 views
Posted on September 23, 2014 at 01:55

Hi All

Cube 4.3.1/Keil/F4:

When generating a cube project that includes a USB(HS) mass storage driver, if the file ''USBD_Storage_if.c'' already exists in your project AND has been modified within *USER CODE BEGIN* for the hooks, when you re-generate the project, the ''STORAGE_IsReady_HS()'' function ends up as the following:

int8_t  STORAGE_IsReady_HS (uint8_t lun)

{

  /* USER CODE BEGIN 11 */ 

/* USB Mass storage Standard Inquiry Data */

int8_t  STORAGE_Inquirydata_HS[] = {//36

  

  /* LUN 0 */

  0x00,

  0x80,

  0x02,

  0x02,

  (STANDARD_INQUIRY_DATA_LEN - 5),

  0x00,

  0x00,

  0x00,

  'S', 'T', 'M', ' ', ' ', ' ', ' ', ' ', /* Manufacturer : 8 bytes */

  'P', 'r', 'o', 'd', 'u', 'c', 't', ' ', /* Product      : 16 Bytes */

  ' ', ' ', ' ', ' ', ' ', ' ', ' ', ' ',

  '0', '.', '0' ,'1',                     /* Version      : 4 Bytes */

};

  /* USER CODE END 11 */ 

}

If this file is manually deleted before re-creating the cube project - it is created OK.

Any ideas?
    This topic has been closed for replies.

    3 replies

    Montassar BEN ROMDHANE_O
    Visitor II
    October 8, 2014
    Posted on October 08, 2014 at 10:21

    Hi JasonP,

    Thank you for bringing this issue to our attention. We’ll pass it along to our STM32CubeMX team. Keep an eye out for the next update!

    Regards,

    Heisenberg.

    stm32cube-t
    ST Employee
    November 7, 2014
    Posted on November 07, 2014 at 11:41

    Dear user,

    we do not reproduce your issue. Thanks in advance for providing us with your ioc file and the code that was added to the user section.

    Note, user section tags should not be modified (in your extract we should see section 1 and not section 11).

    Best regards

    jasonp4113
    Associate III
    November 9, 2014
    Posted on November 10, 2014 at 00:20

    Hi

    Updating to cubeMX 4.4 seems to have fixed this issue.

    Thx.