Search found 32 matches

by resset
Mon Jul 05, 2021 12:01 pm
Forum: Bug Reports
Topic: hal_sio_lld.c source directory confusion Topic is solved
Replies: 2
Views: 1721

hal_sio_lld.c source directory confusion Topic is solved

Hi, My setup: - ChibiOS version or subversion revision number: 21.6.0 - Compiler: GCC 10.3.0 - Platform and board: STM32H743VI, but NUCLEO144 with STM32H743ZI is also affected I am trying to use SIO with FIFO on H7 platform. os/hal/ports/STM32/STM32H7xx/platform.mk says that this MCU family uses USA...
by resset
Fri Dec 06, 2013 12:25 am
Forum: STM32 Support
Topic: STM32F4DIS-BB anyone? at least SD card...
Replies: 11
Views: 8713

Re: STM32F4DIS-BB anyone? at least SD card...

Here you have not-so-complete board files for Embest board, although SDIO pins are configured there, along with sdc_lld_is_card_inserted() and stuff. Please diff those files to ST_STM32F4_DISCOVERY's ones to find out what's going on there. Kudos also go to Tectu:) With all this sample code (tests/de...
by resset
Fri Sep 20, 2013 3:02 pm
Forum: STM32 Support
Topic: [DONE] SDC read fails.
Replies: 30
Views: 16194

Re: [TODO] SDC read fails.

Have a look here: http://forum.chibios.org/phpbb/viewtopic.php?f=3&t=519&hilit=pito+sdio#p4807 There is a working example attached within the posts somewhere for SDIO card speed measurements, maybe it helps you somehow. Unfortunately this works the same way, sometimes it mounts card immedia...
by resset
Thu Sep 19, 2013 8:08 pm
Forum: STM32 Support
Topic: [DONE] SDC read fails.
Replies: 30
Views: 16194

Re: [TODO] SDC read fails.

Hi, I think it is hardware problem. Check carefully the board with a magnifying glass - possibly a cold solder joints! Also check contacts of the reader. I checked every line between discovery board and card socket and they are continous. Also solder joints look ok. I also tried another STM32F4-DIS...
by resset
Tue Sep 17, 2013 11:21 pm
Forum: STM32 Support
Topic: [DONE] SDC read fails.
Replies: 30
Views: 16194

Re: [TODO] SDC read fails.

@alexblack, @Giovanni, can you tell if you have any other information on this? I use STM32F407-DISCOVERY with Embest board and SDIO interface. ChibiOS/RT is 2.7.0unstable (most recent). My four cards, as turned out below, are most likely all V2.0. And I have quite related problem with them. I have a...
by resset
Tue Sep 17, 2013 7:58 pm
Forum: STM32 Support
Topic: STM32F407 - change pinout of driver
Replies: 5
Views: 4024

Re: STM32F407 - change pinout of driver

tronicgr wrote:So we can use the PD5 pin for an LCD screen for example without having to physically alter the STM32F4-Discovery board then?


You can, at least it works if you use it as an output: I use PD5 as WR line in 8080 16-bit display (FSMC_NWE).
by resset
Mon Sep 16, 2013 5:35 pm
Forum: STM32 Support
Topic: MMC Over SPI Troubles With Embest Board
Replies: 4
Views: 2993

Re: MMC Over SPI Troubles With Embest Board

Tectu wrote:Can you please upload a .zip of your code containing your board files? There are different versions of Tectu's board files out there. I will try to get a final one together this weekend.

If you asked about mine, I attach them below. :-)
by resset
Mon Sep 16, 2013 8:55 am
Forum: STM32 Support
Topic: MMC Over SPI Troubles With Embest Board
Replies: 4
Views: 2993

Re: MMC Over SPI Troubles With Embest Board

On Embest board there is a GPIOB_PIN15 that is connected to ~CD of the card, so it should work as a card detect, only negated. It is not configured in Tectu's board files, however. Should be sth like this: GPIOB_SD_DETECT.
by resset
Mon Sep 09, 2013 9:45 pm
Forum: Development and Feedback
Topic: [DONE] The New STM32F429/F439
Replies: 134
Views: 64964

Re: [TODO] The New STM32F429/F439

Tectu, maybe I could, but I have no hardware to test code on. Also, I am not going to be able to order this board in very short time :(
by resset
Fri Aug 09, 2013 1:32 pm
Forum: STM32 Support
Topic: Problem compiling project
Replies: 11
Views: 6587

Re: Problem compiling project

That warning is known ad accepted, you can suppress that by putting a "return 0" at the end but doing so the Keil and IAR compiler would start complaining about unreachable code. Being 2 compilers vs 1 compiler Keil and IAR win and the warning using GCC has to stay. ...so this is the reas...

Go to advanced search