Search found 8 matches
- 08 Jun 2020 16:46
- Forum: mikroBasic PRO for ARM General
- Topic: STM32H743VI and ADC Problem
- Replies: 6
- Views: 2083
STM32H743VI and ADC Problem
Hello, i try to read two ADC's but the program seems to "hang".... My code: ... dim ch1 as integer dim ch2 as integer main: ADC_Set_Input_Channel(_ADC_CHANNEL_5 or _ADC_CHANNEL_9) 'PORTB.0 and PORTB.1 ADC1_Init while TRUE ch1 = ADC1_Read(5) ch2 = ADC1_Read(9) display_menu(10, ch1) 'send to my displa...
- 09 May 2020 14:44
- Forum: mikroBasic PRO for ARM General
- Topic: Nucleo-H743 is not working with PLL1 as clock source
- Replies: 17
- Views: 6325
Re: Nucleo-H743 is not working with PLL1 as clock source
Hi Sergiu,
thanks for the info. I tryed it, but still problems.
I made a new post in mikroProg Forum.
Regards,
Ralf
thanks for the info. I tryed it, but still problems.
I made a new post in mikroProg Forum.
Regards,
Ralf
- 09 May 2020 14:41
- Forum: mikroProg™ programmer and debugger
- Topic: Nucleo H743 and mikroProg for STM32 Problem
- Replies: 2
- Views: 1474
Re: Nucleo H743 and mikroProg for STM32 Problem
Found some things.... 1. Seems the message comes from the ST-Link V3, it is still connected to the Nucleo, the Link Reset is enabled (JP1) 2. mikroProg does not recognice/connect the programmer. I also dont see it in the SW (Pulldown Box?) 3. There is no message (if there is one) that it connected o...
- 09 May 2020 13:36
- Forum: mikroProg™ programmer and debugger
- Topic: Nucleo H743 and mikroProg for STM32 Problem
- Replies: 2
- Views: 1474
Nucleo H743 and mikroProg for STM32 Problem
Hi all, please, i need help using the Nucleo-144 (STM32H743ZI) with the mikroProg for STM32. I use CN5 (MIPI connector) , GND Pin#3, SWDIO Pin#2 and SWCLK Pin#4 to connect to the programmer. The board is powered via USB, than connect the programmer and reset the board as written in the documentation...
- 09 May 2020 13:30
- Forum: mikroC PRO for ARM General
- Topic: Nucleo H743 and mikroProg for STM32
- Replies: 1
- Views: 894
Nucleo H743 and mikroProg for STM32
Hi all, please, i need help using the Nucleo-144 (STM32H743ZI) with the mikroProg for STM32. I use CN5 (MIPI connector) , GND Pin#3, SWDIO Pin#2 and SWCLK Pin#4 to connect to the programmer. The board is powered via USB, than connect the programmer and reset the board as written in the documentation...
- 08 May 2020 15:16
- Forum: mikroBasic PRO for ARM General
- Topic: Nucleo-H743 is not working with PLL1 as clock source
- Replies: 17
- Views: 6325
Re: Nucleo-H743 is not working with PLL1 as clock source
Hi Sergiu,
thanks, found it. I was confused because of the ST Logo on it.....
We also have the MikroProg for STM32 Programmer/Debugger purchased from MikroE.
Does it not support the ST-Link V2? The pinning fits, only some adapter cables needed to CN5 of the Nucleo-H743....
Regards,
Ralf
thanks, found it. I was confused because of the ST Logo on it.....
We also have the MikroProg for STM32 Programmer/Debugger purchased from MikroE.
Does it not support the ST-Link V2? The pinning fits, only some adapter cables needed to CN5 of the Nucleo-H743....
Regards,
Ralf
- 08 May 2020 11:48
- Forum: mikroBasic PRO for ARM General
- Topic: Nucleo-H743 is not working with PLL1 as clock source
- Replies: 17
- Views: 6325
Re: Nucleo-H743 is not working with PLL1 as clock source
Hello Sergiu,
thanks for reply.
The solution with the dongle seem to be best for me, where to get it? From ST? Can't find it.....
Regards,
Ralf
thanks for reply.
The solution with the dongle seem to be best for me, where to get it? From ST? Can't find it.....
Regards,
Ralf
- 07 May 2020 14:19
- Forum: mikroBasic PRO for ARM General
- Topic: Nucleo-H743 is not working with PLL1 as clock source
- Replies: 17
- Views: 6325
Re: Nucleo-H743 is not working with PLL1 as clock source
Hello Stefan,
i have the same problem when trying to connect with MikroProg to a Nucleo-H743ZI (Command not supported...).
I use V1.61.
Is there any workaround?
Regards,
Ralf
i have the same problem when trying to connect with MikroProg to a Nucleo-H743ZI (Command not supported...).
I use V1.61.
Is there any workaround?
Regards,
Ralf