Search found 33 matches

by [email protected]
Tue Jan 01, 2013 10:36 pm
Forum: General Support
Topic: STM32F103 ICU not starting keeping the line low
Replies: 5
Views: 4596

Re: STM32F103 ICU not starting keeping the line low

Thanks a lot Giovanni!

As always you ware right! :)
Everything works well now!

BTW. Happy new year!

Greetings,
Piotr
by [email protected]
Sun Dec 30, 2012 12:26 pm
Forum: General Support
Topic: STM32F103 ICU not starting keeping the line low
Replies: 5
Views: 4596

Re: STM32F103 ICU not starting keeping the line low

I have forgotten to say- I am using latest trunk.

Piotr
by [email protected]
Sun Dec 30, 2012 12:19 pm
Forum: General Support
Topic: STM32F103 ICU not starting keeping the line low
Replies: 5
Views: 4596

Re: STM32F103 ICU not starting keeping the line low

Hi Giovanni!

Thanks for the answer.
The DHT22 needs a little trick to start transmittion.
It needs the line to be set HIGH to LOW for 20ms then back to HIGH.

HIGH to LOW is done by:
palSetPadMode(GPIOB, 6, PAL_MODE_OUTPUT_OPENDRAIN);
palWritePad(GPIOB, 6, PAL_LOW);
chThdSleepMilliseconds(20 ...
by [email protected]
Sun Dec 30, 2012 10:24 am
Forum: General Support
Topic: STM32F103 ICU not starting keeping the line low
Replies: 5
Views: 4596

STM32F103 ICU not starting keeping the line low

Hi,

I have bought very basic board with STM32F103C8T6 uC.
I am trying to make the icu to work w/o success.
The ICU seems not to start as the line is low after starting and enabling the ICU.
Very similar code works well on STM32F4 board.


DHT_icucfg.mode = ICU_INPUT_ACTIVE_HIGH;
DHT_icucfg ...
by [email protected]
Thu Dec 20, 2012 4:28 pm
Forum: General Support
Topic: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%
Replies: 18
Views: 17421

Re: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%

OMG! Shortening the wires did the trick!
I would never guess that 25cm wires are way too long.

Code: Select all

--- 192.168.1.10 ping statistics ---
332 packets transmitted, 332 received, 0% packet loss, time 331002ms


HUGE thanks to all for your help :)

Greetings,
Piotr Klimczak
by [email protected]
Thu Dec 20, 2012 9:57 am
Forum: General Support
Topic: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%
Replies: 18
Views: 17421

Re: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%

25cm. Too long? Will give it a try.
Greetings
Piotr
by [email protected]
Thu Dec 20, 2012 1:26 am
Forum: General Support
Topic: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%
Replies: 18
Views: 17421

Re: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%

Hi Giovanni!

On the ethernet dovelopment post you wrote:

by Giovanni » Mon Mar 26, 2012 3:40 pm

Hardware discussions are absolutely welcome.

BTW, one of the ChibiOS customers created a control board based on the STM32F4-Discovery, it has the DP83848 in RMII mode clocked by a MCO. I should ...
by [email protected]
Wed Dec 19, 2012 10:49 pm
Forum: General Support
Topic: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%
Replies: 18
Views: 17421

Re: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%

One more thing.

Please also note, that for bmsr I am also getting the value 1111111111111111 from time to time.
How can i change the clocks to be sure that it is the hardware problem, not software?

Thanks in advance!
by [email protected]
Wed Dec 19, 2012 10:22 pm
Forum: General Support
Topic: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%
Replies: 18
Views: 17421

Re: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%

I have changed one more thing in comparision to pure svn trunk:

Index: mcuconf.h
===================================================================
--- mcuconf.h (revision 4948)
+++ mcuconf.h (working copy)
@@ -45,7 +45,7 @@
#define STM32_CLOCK48_REQUIRED TRUE
#define STM32_SW ...
by [email protected]
Wed Dec 19, 2012 10:07 pm
Forum: General Support
Topic: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%
Replies: 18
Views: 17421

Re: STM32F4DISCOVERY and DP83848 Pocket loss at ~40%

Hi Giovanni,

Accoring to clocking, question- everything works on defaults just like in LWIP demo example. I was trying to change as little as possible to eliminate possible failure causes- which is me and my code . I just wanted to be sure that that it is not my fault
It has a 50MHz oscillator ...