 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : About time the ArmmiteH7 got some TLC: V5.07.01 betas
  Page 3 of 4   |
|||||
| Author | Message | ||||
disco4now Guru  Joined: 18/12/2014 Location: AustraliaPosts: 844 |
It may be worth trying 5.05.11 as John had some boards (his own design) that would not run MMBasic on the later version. Not a solution but may be worth eliminating whether its a similar situation. Regards Gerry Latest F4 Latest H7 |
||||
KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
Hi Gerry, Downloaded and tried, but no difference. There is just no communications with these two newer units, it's as though there is no MMBasic programmed or the MMBasic console is not routed to the port. Memory verification is 100% and it looks the same as the older units on read in STM Cube. The only thing different in the Device properties in Cube is the Bootloader version and obviously the Revision ID. It's all too hard. Mike. |
||||
| disco4now Guru Joined: 18/12/2014 Location: AustraliaPosts: 844 |
The info below was derived from one of Peter's posts somewhere. Might cast some suspicion on the ST-Link firmware version. Do you have one of Peters backpack V3 with provision for an external crstal you could try? Can you see if the STLINk V3 have a 8MHz or 8.33 Mhz cystal? ST-LINK V2/V3 Details and Update The NUCLEOH743ZI has an ST-LINK V2 connected. The NUCLEOH743ZI2 has an ST-LINK V3 connected. You should be aware with the ZI2 of one possible issue. There is a design flaw on the ZI2 that doesn't exist on the ZI. The ST-LINK in both cases generates the 8MHz system clock for the H743. In the case of the ZI this is derived directly from the crystal clocking the ST-LINK V2 circuit. In the case of the ZI2 it is derived from the internal RC oscillator on the ST-LINK V3 processor. i.e. not very accurate. There is now new firmware for the V3 which has the option of using a crystal derived clock but it isn't at 8MHZ but rather 8.33MHZ. This seems to be a setup option when updating the firmware in the ST-LINK. DO NOT choose this option if presented with it. Latest F4 Latest H7 |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
I remember that conversation now. This is ST-link V3, the Xtal on the Link part is marked 25.000 which would normally be 25MHz, then divided down for whatever is needed, so likely 8.33MHz. I have updated the ST-Link firmware on only ONE unit. I have Peters V1.3 Backpack but can't see a xtal location. I'll look into this more when I get back. I've forgotten most of it. Thanks. It's all too hard. Mike. |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
BTW you can change the ST-LINK clock between 8.33 and 8 and back again. Default is 8Mhz when updating. Don't think this is the problem I'm having. Something is seriously not right. Just looks like MMBasic is not starting or running. Adding a com port to the normally allocated Console port makes no difference, just silence. Zero access to MMBasic, only thing that talks to the two devices is STM Cube. It's all too hard. Mike. |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 8578 |
I would suspect the RTC oscillator not starting. Have you got a scope to look at the clock inputs? |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
Yes have Digital scope, I'll have a closer look, the LSE crystal osc 32.768 kHz was running when I checked one of the boards. The boards are STM32H7 Nucleo-144 boards (MB1364), so far all links and connections look the same. Just the VDD_MCU and 1.8v-3v3 jumpers swapped around. It's all too hard. Mike. |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
I can't seem to find the Clock pins for the RTC, anyone remember what they are? It's late and I'm tired, I'll have another look tomorrow. Thanks in advance for any help. It's all too hard. Mike. |
||||
| disco4now Guru Joined: 18/12/2014 Location: AustraliaPosts: 844 |
Pin 8 and 9 I think Pin and Connector Capabilities STM32H743ZI/STM32H743ZI2 144 Pin function and connector positions The capabilities and allocation of each pin are detailed in this table. MMBasic can address the pins via their pin number. Pin Features 1-PE2 DIGITAL_IN DIGITAL_OUT SSD1963-DB2 2-PE3 DIGITAL_IN DIGITAL_OUT SSD1963-DB3 3-PE4 DIGITAL_IN DIGITAL_OUT SSD1963-DB4 4-PE5 DIGITAL_IN DIGITAL_OUT SSD1963-DB5 5-PE6 DIGITAL_IN DIGITAL_OUT SSD1963-DB6 6 VBAT Backup Battery 7-PC13 DIGITAL_IN DIGITAL_OUT NUCLEO-B1 (K1) BLUE KEY MMBasic Reset 8 32KHz Xtal 9 32KHz Xtal 10-PF0 DIGITAL_IN DIGITAL_OUT COUNT1 11-PF1 DIGITAL_IN DIGITAL_OUT COUNT2 12-PF2 DIGITAL_IN DIGITAL_OUT COUNT3 13-PF3* ANALOG_C DIGITAL_IN DIGITAL_OUT COUNT4 14-PF4* ANALOG_C DIGITAL_IN DIGITAL_OUT IR 15-PF5* ANALOG_C DIGITAL_IN DIGITAL_OUT 16 GND 17 VDD 18-PF6* ANALOG_C DIGITAL_IN DIGITAL_OUT SD-CS 19-PF7* ANALOG_C DIGITAL_IN DIGITAL_OUT SPI5-CLK SYSTEM SPI 20*-PF8 ANALOG_C DIGITAL_IN DIGITAL_OUT SPI5-IN “ 21-PF9* ANALOG_C DIGITAL_IN DIGITAL_OUT SPI5-OUT “ 22-PF10* ANALOG_C DIGITAL_IN DIGITAL_OUT 23-PH0 8MHz OSC 24-PH1 N/C 25 NRST RESET 26-PC0 ANALOG_C DIGITAL_IN DIGITAL_OUT OV7670-D0 27-PC1 ANALOG_C DIGITAL_IN DIGITAL_OUT OV7670-D1 SPI2-OUT 28-PC2 ANALOG_C DIGITAL_IN DIGITAL_OUT OV7670-D2 SPI2-IN 29-PC3 ANALOG_C DIGITAL_IN DIGITAL_OUT OV7670-D3 30 VDD 31 ANALOG-GND 32 VREF+ 33 ANALOG-VDD 34-PA0 ANALOG_A DIGITAL_IN DIGITAL_OUT PWM-2A 35-PA1 ANALOG_A DIGITAL_IN DIGITAL_OUT PWM-2B 36-PA2 ANALOG_A DIGITAL_IN DIGITAL_OUT PWM-2C 37-PA3 ANALOG_A DIGITAL_IN DIGITAL_OUT PWM-2D 38 GND 39 VDD 40-PA4 DAC1 AUDIO-L 41-PA5 DAC2 AUDIO-R 42-PA6 ANALOG_A DIGITAL_IN DIGITAL_OUT SPI-IN 43-PA7 ANALOG_A DIGITAL_IN DIGITAL_OUT SPI-OUT 44-PC4 ANALOG_A DIGITAL_IN DIGITAL_OUT OV7670-D4 45-PC5 ANALOG_A DIGITAL_IN DIGITAL_OUT OV7670-D5 46-PB0 LCD-BL NUCLEO-GREEN BACKLIGHT 47-PB1 ANALOG_A DIGITAL_IN DIGITAL_OUT 48-PB2 DIGITAL_A DIGITAL_OUT SPI3-OUT 49-PF11 ANALOG_A DIGITAL_IN DIGITAL_OUT 50-PF12 ANALOG_A DIGITAL_IN DIGITAL_OUT 51 GND 52 VDD 53-PF13 ANALOG_B DIGITAL_IN DIGITAL_OUT 54-PF14 ANALOG_B DIGITAL_IN DIGITAL_OUT 55-PF15 DIGITAL_IN DIGITAL_OUT 56-PG0 DIGITAL_IN DIGITAL_OUT 57-PG1 DIGITAL_IN DIGITAL_OUT SSD1963-RS 58-PE7 DIGITAL_IN DIGITAL_OUT SSD1963-DB7 59-PE8 DIGITAL_IN DIGITAL_OUT SSD1963-DB8 60-PE9 DIGITAL_IN DIGITAL_OUT SSD1963-DB9 61 GND 62 VSS 63-PE10 DIGITAL_IN DIGITAL_OUT SSD1963-DB10 64-PE11 DIGITAL_IN DIGITAL_OUT SSD1963-DB11 65-PE12 DIGITAL_IN DIGITAL_OUT SSD1963-DB12 66-PE13 DIGITAL_IN DIGITAL_OUT SSD1963-DB13 67-PE14 DIGITAL_IN DIGITAL_OUT SSD1963-DB14 68-PE15 DIGITAL_IN DIGITAL_OUT SSD1963-DB15 69-PB10 DIGITAL_IN DIGITAL_OUT I2C2-SCL 70-PB11 DIGITAL_IN DIGITAL_OUT I2C2-SDA 71 VCAP 72 VDD 73-PB12 DIGITAL_IN DIGITAL_OUT COM3-RX 74-PB13 DIGITAL_IN DIGITAL_OUT COM3-TX 75-PB14 DIGITAL_IN DIGITAL_OUT NUCLEO-RED 76-PB15 DIGITAL_IN DIGITAL_OUT COM1-RX 77-PD8 CONSOLE-TX 78-PD9 CONSOLE-RX 79-PD10 DIGITAL_IN DIGITAL_OUT Keyboard Power V2 Nucleo USB Power 80-PD11 DIGITAL_IN DIGITAL_OUT 81-PD12 DIGITAL_IN DIGITAL_OUT PWM-1A 82-PD13 DIGITAL_IN DIGITAL_OUT PWM-1B 83 GND 84 VDD 85-PD14 DIGITAL_IN DIGITAL_OUT PWM-1C 86-PD15 DIGITAL_IN DIGITAL_OUT PWM-1D 87-PG2 DIGITAL_IN DIGITAL_OUT 88-PG3 DIGITAL_IN DIGITAL_OUT OV7670_PCLK 89-PG4 DIGITAL_IN DIGITAL_OUT OV7670_VSYNC 90-PG5 DIGITAL_IN DIGITAL_OUT OV7670_HREF 91-PG6 DIGITAL_IN DIGITAL_OUT Keyboard Power V1 Nucleo USB Power 92-PG7 DIGITAL_IN DIGITAL_OUT 93-PG8 DIGITAL_IN DIGITAL_OUT COUNT5-HS 94 GND 95 VDDUSB 96-PC6 DIGITAL_IN DIGITAL_OUT OV7670-D6 97-PC7 DIGITAL_IN DIGITAL_OUT OV7670-D7 98-PC8 DIGITAL_IN DIGITAL_OUT 99-PC9 DIGITAL_IN DIGITAL_OUT 100-PA8 DIGITAL_IN DIGITAL_OUT OV7670_XCLK 101-PA9 DIGITAL_IN DIGITAL_OUT 102-PA10 DIGITAL_IN DIGITAL_OUT 103-PA11 USB-D+ 104-PA12 USB-D- 105-PA13 SWDIO 106 VCAP 107 GND 108 VDD 109-PA14 SWCLK 110-PA15 DIGITAL_IN DIGITAL_OUT SD-CS (backpack) 111-PC10 DIGITAL_IN DIGITAL_OUT 112-PC11 DIGITAL_IN DIGITAL_OUT 113-PC12 DIGITAL_IN DIGITAL_OUT 114-PD0 DIGITAL_IN DIGITAL_OUT 115-PD1 DIGITAL_IN DIGITAL_OUT 116-PD2 DIGITAL_IN DIGITAL_OUT 117-PD3 DIGITAL_IN DIGITAL_OUT SPI2-CLK 118-PD4 DIGITAL_IN DIGITAL_OUT COM2-DE 119-PD5 DIGITAL_IN DIGITAL_OUT COM2-TX 120 GND 121 VDD 122-PD6 DIGITAL_IN DIGITAL_OUT COM2-RX 123-PD7 DIGITAL_IN DIGITAL_OUT 124-PG9 DIGITAL_IN DIGITAL_OUT COM4-RX 125-PG10 DIGITAL_IN DIGITAL_OUT SSD1963_WR 126-PG11 DIGITAL_IN DIGITAL_OUT SPI-CLK 127-PG12 DIGITAL_IN DIGITAL_OUT SSD1963_RESET 128-PG13 DIGITAL_IN DIGITAL_OUT SSD1963_RD 129-PG14 DIGITAL_IN DIGITAL_OUT COM4-TX 130 GND 131 VSS 132-PG15 DIGITAL_IN DIGITAL_OUT 133-PB3 DIGITAL_IN DIGITAL_OUT SPI3-CLK 134-PB4 DIGITAL_IN DIGITAL_OUT SPI3-IN 135-PB5 DIGITAL_IN DIGITAL_OUT 136-PB6 DIGITAL_IN DIGITAL_OUT COM1-TX 137-PB7 DIGITAL_IN DIGITAL_OUT NUCLEO-BLUE 138 BOOT0 139-PB8 DIGITAL_IN DIGITAL_OUT I2C-SCL 140-PB9 DIGITAL_IN DIGITAL_OUT I2C-SDA 141-PE0 DIGITAL_IN DIGITAL_OUT SSD1963-DB0 142-PE1 DIGITAL_IN DIGITAL_OUT SSD1963-DB1 143 PDR-ON 144 VDD Latest F4 Latest H7 |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
The clock signals don't appear on the connector pins unless links are inserted for external OSC options. Links SB40, SB41, SB44, SB46 - likely just clock leakage showing up on the pins if measuring. The 32kHz crystal is running. I assume that means the RTC is running ?? The STLNK_MCO is feeding the CPU at around 8.13Mhz. It's all too hard. Mike. |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
I reloaded Ver 5.05.11 and I noticed that the User USB OVCR led had a faint glow, and it went out when RESET was pressed. Set the Baud rate to 34000 and I got MMBasic response when Reset Pressed. So disco4now was right - And these Newer boards that I have do not like the latest MMBasic. Looks Like I will have to roll back all my code for the changes made in the latest version, that now error when run. Do we know exactly what is causing this? Surely it can't just be Clock running a bit above 8Mhz? If it is then I will find a crystal and fit to the spot on the H7 Board made for a Crystal. It's all too hard. Mike. |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
OK Crazy stuff. After getting the older version to Run, I used drag and drop to install the latest version 5.07.01b0 and it now runs ?????? F#$@%* It's all too hard. Mike. |
||||
phil99 Guru Joined: 11/02/2018 Location: AustraliaPosts: 1781 |
Just a guess. Perhaps the latest firmware is missing something that sets the chip up for use by MMBasic. So upgrading from an older version works if that something is retained through the re-flash. |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
Just did the 2nd board with Links removed and running on a 9" display, backpack, SD card etc. Works like a dream, full code running no errors. One full day wasted  It's all too hard. Mike. |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
Both boards draw 90 mA from Vbat pin ????, battery goes flat pretty fast. Yes Vbat Link is disconnected and verified as the correct link. Why does MMBasic with options set disappear if the battery is flat. I can power on and off without battery and MMbasic on its own holds. If I set options and cycle power MMbasic is gone. I seem to recall something about settings saved in RTC memory ? I also have to load version 5.05.11 before loading 5.07.01b otherwise the later version will not communicate over console. It's all too hard. Mike. |
||||
| disco4now Guru Joined: 18/12/2014 Location: AustraliaPosts: 844 |
Does 'gone' mean you can't talk to it anymore, presumably the firmware is still in the flash, just not talking. Latest F4 Latest H7 |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
Yes it appears you can't talk to it. However, this high current on the Vbat battery is only there under certain conditions where MBasic has hung or the options are corrupted. I have to figure out which. It means that a good battery will go flat in a matter of minutes in this high drain condition, once everything is running the current is Vbat virtually nothing. I proved this by powering the Vbat with a small flat Li-ion rechargeable and a 470 ohm in series to limit current, it allowed me to get this thing running without flattening a tiny battery in the process and causing no end of stupid symptoms. Once running it's happy. Note: I must program the old version of MMBasic First, otherwise there is no way to get a console connection with the later version installed. Works 100% every time. It's all too hard. Mike. |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
A further test has reveled the vbat current rises to 90ma when the Power (5V) is removed. It drops back to almost zero once the H7 powers up and is running. No wonder it stops working when powered off for a few minutes on a coin battery. Again YES SB52 has been removed and I confirmed that one side is connected to the vbat pin and SB52 is completely open and isolated from the normal System vbat supply. It's all too hard. Mike. |
||||
| JohnS Guru Joined: 18/11/2011 Location: United KingdomPosts: 3656 |
Sounds like a clear-all-the-flash process would be worthwhile. For the picomite we have Clear_Flash.uf2 - is there an equivalent for your board? Or you can do it via tools such as STLink / OpenOCD. The disappearing MMBasic: a floating input on a critical pin? (Possible?) John |
||||
| KeepIS Guru Joined: 13/10/2014 Location: AustraliaPosts: 1357 |
Hi John, I've done that a few times but I'm going to try it all again today. This high current Vbat under certain conditions is puzzling, want to do more test on that as well. Could this still be part of the problem with the New boards and the reason for the high Vbat current? There are no caps connected to the 32.768KHz xtal. Circuit says DNF. It's all too hard. Mike. |
||||
| Page 3 of 4 |
|||||
 Print this page |
