Prometheus atempt
Prometheus atempt
Hi as many of you know im trying to assemble a Prometheus from @andreika .
Current status is:
- all components on board except for some small caps 2.2uF
- com port is recognized in PC so cp2101 looks OK
- powering from 12v both 5v and 3.3v rails are OK (current is ~50 mA)
- swdio led is always on (around 2.5v) and gets brighter at the moment I hit connect
- replaced smd crystal whith TH and made no difference and yes the smd are well mounted
- all components from bom with references so they are correct
Currently trying to upload the build but I can't even connect via stlink
Current status is:
- all components on board except for some small caps 2.2uF
- com port is recognized in PC so cp2101 looks OK
- powering from 12v both 5v and 3.3v rails are OK (current is ~50 mA)
- swdio led is always on (around 2.5v) and gets brighter at the moment I hit connect
- replaced smd crystal whith TH and made no difference and yes the smd are well mounted
- all components from bom with references so they are correct
Currently trying to upload the build but I can't even connect via stlink
- Attachments
-
- IMG_20190204_211443.jpg (4.55 MiB) Viewed 13943 times
-
- IMG_20190204_205842.jpg (4.08 MiB) Viewed 13943 times
-
- IMG_20190204_205826.jpg (4.63 MiB) Viewed 13943 times
-
- IMG_20190204_205741.jpg (6.57 MiB) Viewed 13943 times
-
- IMG_20190204_205721.jpg (5.14 MiB) Viewed 13943 times
Re: Prometheus atempt
You're right, I was anxious ! They arrive tomorrow. Do you think that's what is wrong with it ? Isn't strange 2.5 v at swdio ?
Re: Prometheus atempt
so caps are on! same behavior, any ideas?
Re: Prometheus atempt
have you disconnected the onboard chip on the discovery board? (there are some jumpers powering the board-native stm chip from stlink)
Re: Prometheus atempt
He has some additional data at this link. The video seems to show how the SWD is wired, but it's not very clear.
https://rusefi.com/forum/viewtopic.php?f=4&t=1215&start=136
https://rusefi.com/forum/viewtopic.php?f=4&t=1215&start=136
Welcome to the friendlier side of internet crazy
Re: Prometheus atempt
I think that's okay
- Attachments
-
- IMG_20190205_184729.jpg (3.75 MiB) Viewed 13894 times
- AndreyB
- Site Admin
- Posts: 14332
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Prometheus atempt
I am sorry i have nothing to offer.
Do we know if anyone ever had 405 working on this board?
Do we know if anyone ever had 405 working on this board?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Prometheus atempt
it was a falty stm.. now back on track ... so connection is stablished (only without nrst wire if with nrst only hotplug mode... if conectod led turns slitly on, nrst pullup is 10k .. ) anyway i think i was able to uplod the hex , and if i hit connect im able to see it.. no connection via usb nor bluetooth to TS or console.
Re: Prometheus atempt
Nice progress! So you can SWD-program the firmware, and the led blinks once (that's good), but no UART connection? Did you compile the firmware for 405? Does it have a correct default pin configuration?atntpt wrote: ↑Thu Mar 07, 2019 3:40 pmit was a falty stm.. now back on track ... so connection is stablished (only without nrst wire if with nrst only hotplug mode... if conectod led turns slitly on, nrst pullup is 10k .. ) anyway i think i was able to uplod the hex , and if i hit connect im able to see it.. no connection via usb nor bluetooth to TS or console.
Re: Prometheus atempt
firmware was compiled by rusian! https://rusefi.com/build_server_prometheus/ this link i guess its okay.
i can obseve some wierd stuff going on on serial monitor.. i thout might be related to cp2101 so solderd some wires to tx rx pads on BT module to a ~ftdi adapter and the resut was the same
i can obseve some wierd stuff going on on serial monitor.. i thout might be related to cp2101 so solderd some wires to tx rx pads on BT module to a ~ftdi adapter and the resut was the same
Re: Prometheus atempt
- Check the diodes on the bottom side of the pcb (D26,D22,D23) for polarity and shorts between.
- Check the resistors R113, R114, R115.
- Check the baudrate and COM port config - the default is 115200 8N1.
- Don't connect to Bluetooth an USB at the same time - both are using the same UART.
Re: Prometheus atempt
And remember that the Bluetooth module has to be initialized first before using!
Re: Prometheus atempt
video trying to explain
bluetooth module was configured previosly. but i was hopping that a ftdi adapter on tx and rx pads of BT might connect because i was afraid of cp2101 . tried to connect a osciloscope to tx and rx but comunication stops serial stops showing that stuff
bluetooth module was configured previosly. but i was hopping that a ftdi adapter on tx and rx pads of BT might connect because i was afraid of cp2101 . tried to connect a osciloscope to tx and rx but comunication stops serial stops showing that stuff
Re: Prometheus atempt
So it seems that Prometheus is constantly sending some info to UART? Maybe the reason is in wrong firmware configuration, when UART is used as debug console and not as tunerstudio controller? Can you record the data that you're receiving?
Re: Prometheus atempt
you mean the console data? with TS off
Re: Prometheus atempt
it looks like you should play with baud rate
Re: Prometheus atempt
Sooo , after back long Time I got the board to work , I mean Andreika did many thanks to him who spend his time to take a look at my board !
The problem was firmware compilation . Plus some bad soldering he found!
After receiving the board I noticed that setting wasn't saving so, again thanks to him, found that the problem was related to recent changes in the way board restores default configs .
Currently it's reading RPM ,sensors and some outputs , haven't fully tested tho.
Board is meant to run a old CRX with a B16A2 engine.
Any advices ? I reader something about Max9926 don't like Honda low tooth trigger , I was planning to use original distributor just for sensor and conversation to Bike COP since board has igniters .
The problem was firmware compilation . Plus some bad soldering he found!
After receiving the board I noticed that setting wasn't saving so, again thanks to him, found that the problem was related to recent changes in the way board restores default configs .
Currently it's reading RPM ,sensors and some outputs , haven't fully tested tho.
Board is meant to run a old CRX with a B16A2 engine.
Any advices ? I reader something about Max9926 don't like Honda low tooth trigger , I was planning to use original distributor just for sensor and conversation to Bike COP since board has igniters .