Two Teensy 3.2 and one program

pgu

Member
Can somebody help me: one program give me two different results with two Teensy 3.2 ?
I can understand ...:(
 
pgu:
did you not see this rule at the top of the page?
Forum Rule: Always post complete source code & details to reproduce any issue!

Nobody here can help you with the information you have posted in these 2 messages.

Regards,
Ed
 
Last edited:
Can somebody help me: one program give me two different results with two Teensy 3.2 ?
I can understand ...:(

Ideally yes, someone can help.

But more details and information would be needed.

Are the two T_3.2's identical? Purchased from a good source and not counterfeit? What is the nature of the differing results? Maybe one is damaged, or it is relying on internal information like serial # or EPROM stored data? Id it really the same firmware uploaded and running?

Something is different with the two units, or the same code would give the same results.

More info is needed to have any understanding of the issue ...
 
The two T__3.2 are the same and bought from a legitimate source, the assembly contains a webcam and a Lora transceiver module.
On the gateway side (which is a Raspberry), the image is good and on the other the image is black.
Already tested: the webcam and the Lora module. This is not the origin of the problem.
How can I get the T___3.2 firmware reference? Does anyone know?
Tanks for your help.
 
If not the firmware reference, something which help me to distinguish one from the other one.
 
In the program, there are more than on thousand lines …

Your assignment is to produce the smallest sketch that behaves differently on your T3.2s -- and then post that sketch to this thread so others can try.
 
How can I get the T___3.2 firmware reference?
What do you mean by "firmware reference"? The firmware is your code.

something which help me to distinguish one from the other one
Distinguish which one from which other one? If you mean the T3.2, they should be the same.
If you mean the code in each T3.2, you can't get at it. Once the code has been compiled and uploaded, you can't read it from the T3.2

The two T__3.2 are the same and bought from a legitimate source
OK. What is the legitimate source?

Pete
 
@manitou,
I meet the matter with the current code ...
If I test the blinking program, sure that they are going to give the same results on the the T3.2. We should find a smaller program which give result different on the 2 T3.2, but ...

@el_supremo
Firmware reference = firmware version
One T3.2 from the other T3.2
Legitimate source: Digikey, Mouser or Farnell

pgu
 
It's not clear to me what the hardware setup is like. Do you have two completely separate installations, one works and the other doesn't. When you exchange the T3.2 between the two setups, the problem switches with the processor.
Or you have one hardware setup with a socket for the Teensy 3.2. One T3.2 works but if you replace it with the other T3.2 then it fails?

Since you're asking about firmware versions, it suggests that perhaps you aren't certain that the code in the two T3.2 is exactly the same. Can you upload the same version to both T3.2 and try them?

Pete
 
Two T__3.2 and one hardware setup with aprogram give two different results.
I have one hardware setup with a socket for the Teensy 3.2. One T3.2 works but if I replace it with the other T3.2 then it fails.
I confirm that the same code is uploaded to both, and the hardware setup works with one T_3.2 and fails with the other T_3.2

pgu
 
Photo1.JPG
Photo2.JPG
 
Back
Top