Hi to all, I am trying to build a USB host application based STM32F105 using USB stack by Keil (RL-ARM 4.13 (USB Host Mass Storage Class Interface). But I can not even run the MSC demo - fopen() always returns NULL. Besides of it, the USB stack does not recognize mass storage devices bigger than 1G! Does anyone have any experience with this software package? Regards Alex
Are you using MCBSTM32C or your custom board? Does original Keil example work?
1. I am using my custom board. It's actually SPI-USB bridge. 2. The original Keil example does not work too.
Are you using same schematic for the USB part as on the Keil board? Do you have Keil MCBSTM32C board?
1. Yes I do, the schematics is in according to application note. Moreover, USB HOST library by ST is working not bad on the same platform, but we want to use Keil library because of support and SW maintenance... 2. No, I have not this evaluation board.
Can you check if schematic of USB part is same as on Keil MCBSTM32C board, here is the schematic: http://www.keil.com/mcbstm32c/mcbstm32c-base-board-schematics.pdf
Looks like this sample does not work. I tried this smaple on two different board. I can read from the USB-Stick once, thats all. On the same board, the STM32 USB-Hostlibrary works fine. K.
I've told to local Keil representative. They demonstrated me MCBSTM32C board working as USB -host: saving/opening piles etc. The only difference that they use RL-ARM library v4.20. I've got RL-ARM v4.13, probably, this is a problem.
It is more likely that your hardware is the problem.
ST library works rather well. Evidently, that there is no hardware problem in our board.
What kind of USB-Stick Keil was using? Hardware should be not the problem. I can read from "some" USB-Sticks.
Was used some disk-on-key 4G. We succeed to run Keil MSC application from RL-ARM v4.20 suite: read USB stick directory, create and write text file, read from this file to Hyper terminal, etc.
So what was the problem?
I suppose, USB-Host library in RL-ARM version 4.13 was not "brewed" well... We are going to purchase v4.20 anyway, hoping it will solve the problem.