Skip to main content
Rogers.Gary
Senior II
December 9, 2018
Solved

NUCLEO-L476RG Input Capture Is Not Capturing

  • December 9, 2018
  • 4 replies
  • 1847 views

Hello:

Using IAR EWARM 7.8 for these tests. IAR provides working HAL examples for the STM32F4 Discovery boards. They have a specific example for both input capture, and PWM capture on the STM32F4 Discovery. Both examples work....both capture a 2KHz square wave in to the pins (PA9,PC7) for each example.

Over to the NUCLEO-L476RG. IAR provides an example for that, both timer input capture and PWM capture. Supposed to be ready to go and "tested". Ditto for CubeMX examples, under cube's folder version "STM32Cube_FW_L4_V1.13.0". Neither of those sources work on the Nucleo board...and I have two boards that are new.

I put a LED toggle in the interrupt TIMx_IRQHandler. Never lights it.

What gives....anyone tried these "tested" examples? Why would HAL work on the old Discovery board, and not on the Nucleo board?

Thanks....

This topic has been closed for replies.
Best answer by waclawek.jan

My crystal cube is completely hazy on this, but here are a few tips:

  • make a basic loopdelay-based blinky with the LED. Blinks?
  • write a simple copy from the input pin to the LED pin. Works?
  • write a blinky with the timer/interrupt. Works?
  • if by now the original example still does not work, read out and check the relevant TIM and GPIO registers content.

JW

4 replies

Tesla DeLorean
Guru
December 10, 2018

Sure you've got it connected to the right pin? PA9 D8 on the Shield header.

Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
waclawek.jan
waclawek.janBest answer
Super User
December 10, 2018

My crystal cube is completely hazy on this, but here are a few tips:

  • make a basic loopdelay-based blinky with the LED. Blinks?
  • write a simple copy from the input pin to the LED pin. Works?
  • write a blinky with the timer/interrupt. Works?
  • if by now the original example still does not work, read out and check the relevant TIM and GPIO registers content.

JW

Rogers.Gary
Senior II
December 13, 2018

Gee, you wouldn't happen to have one of those Teas instrument crystal balls, would you? I heard they impair vision really bad. 8=)

Rogers.Gary
Senior II
December 11, 2018

Hi Clive, Jan:

Thanks for taking the time to respond. It was me....guilty. The sig gen was adding a DC offset and causing convulsions on the capture. Once I discovered this, all is well.

Last night I tried reposting on another topic (cubeMX) it kept messaging something like "Check your internet connection"....apparently, every time I clicked "OK", it checked my connection by reposting the same thing, 6 times. Then I got locked out....something about search pages getting re-indexed. After some searching, looks like ST has some work to do on this new website.

Gary

Amel NASRI
Technical Moderator
December 13, 2018

Hi @Rogers.Gary​ ,

Thanks for coming back to update us on the status of your question.

Please submit any feedback you have regarding the Community platform in @About this community​  space.

-Amel

To give better visibility on the answered topics, please click on "Best Answer" on the reply which solved your issue or answered your question.
Rogers.Gary
Senior II
December 13, 2018

Hi, what is "@About this community" space. Some kind of twitter feed or email? Anyhow...I replied to Brian. BTW - Still gettin that "Check your internet connection message right now even.......3 times in 2 mins

Rogers.Gary
Senior II
December 13, 2018

Thanks for asking....

it was Firefox Quantum 62.0.3 (64-bit) - yes, cache was flushed.

However, thinking it might be the issue, I had similar results on IE.

Gary

Brian Kling
Senior
December 14, 2018

We have been able to duplicate the issue for Firefox, when logged in, with multiple tabs open. Can you provide more details on the IE experience that is similar, is also logged in, multiple tabs open, (more details to consistently reproduce) ?

Rogers.Gary
Senior II
December 15, 2018

when it occured in Firefox, I opened up IE, and it happened with one tab open. Seeing the same reuslt, I closed it and went back to Firefox.