Hi,
There is a bug on the hard choice eb063 atmega324p chanel 1 does not work
Choice software it’s works very well.
bruno
bug eb063 atmega 324p
Moderator: Benj
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: bug eb063 atmega 324p
Hi Bruno,
Please can you attach your Flowcode project file with the problem. Are you getting compile errors or does it simply not work as expected on the hardware?
Please can you attach your Flowcode project file with the problem. Are you getting compile errors or does it simply not work as expected on the hardware?
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Re: bug eb063 atmega 324p
hi,
no compilation problem but can not transfer the program error on link hard spi bruno
no compilation problem but can not transfer the program error on link hard spi bruno
- Attachments
-
- EB063-reception_buffer.fcfx
- (10.66 KiB) Downloaded 331 times
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: bug eb063 atmega 324p
Hello Bruno,
I wonder if the problem could be the hardware SPI speed. To test this you can edit the speed by doing the following.
First set the RF component property to use the hardware channel.
Next click View -> Component Debugger
In the window that appears click the "Expose full component tree" checkbox.
In the properties window click the down arrow at the top of the window and select the CAL_SPI component just underneath the v5__rf0 component.
Change the Prescale property from Fosc/4 (5MHz) to something more reasonable e.g. /32 (625KHz) or /64 (312.5KHz)
Click compile to chip.
Let me know if this makes any difference. If it does then we probably need to bring the hardware SPI clock speed property through so it is available to the user via the RF component properties.
When your done remember to uncheck the "Expose full component tree" checkbox.
I wonder if the problem could be the hardware SPI speed. To test this you can edit the speed by doing the following.
First set the RF component property to use the hardware channel.
Next click View -> Component Debugger
In the window that appears click the "Expose full component tree" checkbox.
In the properties window click the down arrow at the top of the window and select the CAL_SPI component just underneath the v5__rf0 component.
Change the Prescale property from Fosc/4 (5MHz) to something more reasonable e.g. /32 (625KHz) or /64 (312.5KHz)
Click compile to chip.
Let me know if this makes any difference. If it does then we probably need to bring the hardware SPI clock speed property through so it is available to the user via the RF component properties.
When your done remember to uncheck the "Expose full component tree" checkbox.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Re: bug eb063 atmega 324p
hi,
Your solution does not work(/64)
Catastrophe, I grilled a module with your solution, the module is dead
The connection is good, I do not understand !!!
choice chanel 1 bug
I put another module sofward,it works
bruno
Your solution does not work(/64)
Catastrophe, I grilled a module with your solution, the module is dead
The connection is good, I do not understand !!!
choice chanel 1 bug
I put another module sofward,it works
bruno
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: bug eb063 atmega 324p
Hi Bruno,
I'm just catching up with Leigh, seems strange that a slower SPI prescaler would cause issues. Did you power down for a few secs/mins to see if the module had just gone into a stuck state? Maybe halfway through a command when the program was changed meaning every SPI transaction was split into two incorrect bytes? Depends if the CS signal acts as a sync or not.
I'm just catching up with Leigh, seems strange that a slower SPI prescaler would cause issues. Did you power down for a few secs/mins to see if the module had just gone into a stuck state? Maybe halfway through a command when the program was changed meaning every SPI transaction was split into two incorrect bytes? Depends if the CS signal acts as a sync or not.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Re: bug eb063 atmega 324p
hi,
By cutting the power eb063 several seconds, it works again.
Choosing hardware bug.
Oscilloscope on the line shows the bug, I sent this mesure(macro init).
A+bruno
By cutting the power eb063 several seconds, it works again.
Choosing hardware bug.
Oscilloscope on the line shows the bug, I sent this mesure(macro init).
A+bruno