Just a heads up and also inquiring if anyone else has seen this.
Ordered 5 more Can Bridges with the blue PCB, all with F105s, They look legit, at least the dies are marked from either China or Philippines,
Cube programmer can write to them, clear, etc. and show up as 0x418 device code.
My working codebase doesn’t show any life on these other units.
Took a firmware dump of my working unit, confirmed the new units have identical code via firmware comparison.
Both have the 25 mhz crystal.
Haven’t dug too deep into it yet, most likely a counterfeit chip, but just need to figure out what’s required to get it running effectively.
Writing application for Stm32F105 @ 25 MHz
Re: Writing application for Stm32F105 @ 25 MHz
Just to report back,
Seems the last batch I received have a weak pulldown on the BOOT0 circuit, or else there's some leakage somewhere.
1 out of 5 of the units worked out of the box... That's to say, one worked maybe with some added resistance with a finger or such.
I figured I'd try to ground the BOOT0 pin, and sure enough, all of them fired to life.
Copied over the picture from the reverse engineering site: https://dangerouspayload.com/2020/03/10 ... er-device/
Seems the last batch I received have a weak pulldown on the BOOT0 circuit, or else there's some leakage somewhere.
1 out of 5 of the units worked out of the box... That's to say, one worked maybe with some added resistance with a finger or such.
I figured I'd try to ground the BOOT0 pin, and sure enough, all of them fired to life.
Copied over the picture from the reverse engineering site: https://dangerouspayload.com/2020/03/10 ... er-device/
Re: Writing application for Stm32F105 @ 25 MHz
I have the same, haven't found a way around needing to power cycle other than a push-to-break switch on powerline for testing.One query I have is after programming/flashing, I need to fully power cycle things before SDO/CAN come back.
Likely some Init is missing, but if anyone noticed a similar issue and has a fix, would save me some time in trial and error.
I've found that can2 doesn't work very well for sending multiple messages. I was planning on filtering messages from can1 & propagating modified messages to can2, but can2 doesn't seem to be able to keep up with the rate of messages and drops, so I've reverted to just using can1.