[help needed] stm32f429i-disc1 won't connect

[SHOf429]

I have the stm32f429i-disc1 board with tft LCD screen I want to use with Frankenso kit. I can get the .bin or .hex files to load to the board and verify but the console and TunerStudio will not connect. Device manager reports a virtual COM port with the mini B connection, the micro B connection does nothing. My board has LEDs for power and USB communication lit up as well as LEDs tied to PG13 and PG14. The PG13 LED is barely on (steady) and the PG14 LED is a bit brighter, also steady. VBUS LED on the back of the board is also on. No other lights available on the board. I'd love to use this, and data being available on the built-in screen would be sweet.

[AndreyB]

different boards are wired differently. I believe 407 discovery and 429 discovery use different pins for usb.

you would need custom firmware compiled with settings matching your board since usb pins are not configurable at runtime.

[AndreyB]

429 would not click into frankenso, discovery boards all have custom pinout I believe. nucleo boards are nicer about this but that's not relevant here

[SHOf429]

Good to know about the differences between the different discovery boards. Looks like I may have to get a 407 board. I was thinking about comparing the differences in the 407 and the 429, possibly moving pins as required. My concern at the present is that the 439 brain board will not boot up and connect to either tuner studio or the console. I did read in the forum where some boards have a weird issue requiring ST firmware to be loaded then rusEFI Will load and run after that.

[AndreyB]

boot and connect are different things

unless you know what you are doing here unfortunately that's a dead end.

[SHOf429]

Ended up getting a 407 Disco board. Loaded the firmware and connected to the console and TS on the first try. Pinout is very different compared to the 429. 429 has probably 30 additional pins as well as the tft lcd. Maybe a board can be spun up if I can get the code working first, maybe I'll use it to manage the dash.

[Dron_Gus]

I think you can solder 429 on 407 discovery. If you really want 429. Chips pinout should be same.

[AndreyB]

I think you can solder 429 on 407 discovery. If you really want 429. Chips pinout should be same.

429discovery uses 144LQFP version of the chip, 407 uses 100 pin footprint. Pin count matters

[Dron_Gus]

429discovery uses 144LQFP version of the chip, 407 uses 100 pin footprint. Pin count matters

STM32F429VIT6 is in LQFP100 package.
So if you want 429 chip on 407 discovery it is doable. Not sure about reasons. More memory?

[AndreyB]

This thread is about stm32f429-discovery not just stm32f429 - desire was to have more pins and LCD.

[kb1gtt]

Wasn't the pin out shifted by like 1 pin? I recall that was a common concern. If you try it I would say verify the pin out is actually the same. There may be like 1 pin that is not nice. Or that might have been a different chip, I don't fully recall.

[SHOf429]

I'm wondering if the firmware needs some minor adjustments to be compatible with the 429 or if it is the Discovery board that is causing issues. The firmware will load with the ST link utility, but the second comport never shows up on the computer and neither tuner studio or the console will connect to it.

[AndreyB]

Your stm32f429discovery is probably fine but that's not a standard configuration we support.

Unfortunately within the reality of limited resourced I would ask to drop this line of inquiry - that's a distraction we cannot afford. Either you have to figure it out on your own or let's please drop this.

Sorry if that does not sound nice but I hope that it's understandable. I assume you are not interested in 90 USD per hour custom support here.

[SHOf429]

Understood. I was more thinking out loud at this point. This thread can be closed until somebody else decides they want to pick it up and make whatever modification necessary to make it work. Perhaps it will serve as a note for somebody else that goes searching to use a 429 they can find that it's not compatible in current form.