ATZB-A24-ULF hardware issue

Go To Last Post
11 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi !

I have one/or more hardware issues.

I'm using ATZB-A24-ULF modules. I've done my own PCB design similar to Meshnetics MeshBean AMP board (TPS63001DRC DC-DC).

In past few weeks I've "damaged" 3 modules. I use USB power supply 5.15 V, I measure voltage on module 3.31 V.

I think problem happens whan I plug in USB power supply.
I'm able to recognize(read signature) and program module via JTAG correctly, I uploaded my own app(not using Zigbee network) to trigger some ports and read RTC and send RTC data over USART, everything works, but I can't start network. I think problem is with RF chip AT86RF230.

I through 1 module away, but guess what, other two modules started started to work !

Did anyone have similar problem?

Regards Mesko.

Last Edited: Fri. Oct 16, 2015 - 02:31 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

mesko wrote:
Did anyone have similar problem?
If you are not using BitCloud then what software do you use? If is is some self-made software then describe it in more details, like what frequency is used to communicate to the RF chip and other?

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

alexru wrote:
mesko wrote:
Did anyone have similar problem?
If you are not using BitCloud then what software do you use? If is is some self-made software then describe it in more details, like what frequency is used to communicate to the RF chip and other?

Sorry, I forgot to mention it's BitCloud.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

mesko wrote:
Sorry, I forgot to mention it's BitCloud.
Then what exactly "I can't start network" means? What status code is returned?

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

alexru wrote:
Then what exactly "I can't start network" means? What status code is returned?

I don't receive any status code, that's the problem.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

mesko wrote:
I don't receive any status code, that's the problem.
And it is only one module out of 3 with the same firmware that has this problem? Do they have the same fuse settings? What pins of the module are connected?

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

alexru wrote:
And it is only one module out of 3 with the same firmware that has this problem?

This one (Meshnetics is manufac.) I replaced with new module (Atmel). It was totaly quit, but I could recognize it and program it, but nothing worked (USART, GPIO..).

With other 2 modules I had similar problem; I couldn't start network(didn't receive any status code), USART, GPIO... worked fine. Now everything works with these 2 modules.

With all 3 modules I also had problem that I couldn't recognize them (Read Signature).

alexru wrote:
Do they have the same fuse settings?

Fuse settings are (for all of them, I've never changed fuse bits):

Ext : 0xFF
High : 0x9C
Low : 0x62

alexru wrote:
What pins of the module are connected?

Most of pins are "free".
I use I2C, USART, JTAG, RESET button.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So in the end 2 modules are working and one not with the same firmware, or what?

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

alexru wrote:
So in the end 2 modules are working and one not with the same firmware, or what?

Yes.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Can't really suggest something meaningful here. If you have an oscilloscope then try to check RF SPI lines (should be on the module's pins).

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK, that's hardware problem, it's not repeatable like software issue.

I just wanted to know if anyone had similar experience.

Anyway, thank You Alexru, for trying.