CC2530: cc2530: Error in HEX file verification

Do you use CC2530F128 or CC2530F256? What hex file do you try to download it into your CC2530 and which example does your hex file is built from?

In addition:
You wrote: "Using IAR it showing "XDATASatck is currently outside of the stack range." This sounds like the hex file has not been generated correctly. Was a file produced when you got this error message? It could sound like YK is on to something, basically that your settings are off.

You wrote: "While we were able to read flash data from chip. We compare it with original it doesn't match." Are the file you want to upload equal in some parts with the file you read back or are they completely different? If the later it sounds like you haven't been able to flash the device at all.

Yes, we use CC2530F256.
Hex that i try to writeis read from one of my other board in which it works correctly.

I have flashed that chip on custom board using IAR for which we have bootlaoder and application code.
Then i read hex from this custom board in which it works correctly, and
now using it to another boards.

Meaning that you have solved the issue?

No, as i said this problem happens in 10 out of 5 piece not always...

Try to to erase all to your CC2530 chip before you do download hex into your CC2530.

TER said:

In addition:
You wrote: "Using IAR it showing "XDATASatck is currently outside of the stack range." This sounds like the hex file has not been generated correctly. Was a file produced when you got this error message? It could sound like YK is on to something, basically that your settings are off.

You wrote: "While we were able to read flash data from chip. We compare it with original it doesn't match." Are the file you want to upload equal in some parts with the file you read back or are they completely different? If the later it sounds like you haven't been able to flash the device at all.

This is screenshot for when i try load bootloader code.  

TER said:

In addition:
You wrote: "Using IAR it showing "XDATASatck is currently outside of the stack range." This sounds like the hex file has not been generated correctly. Was a file produced when you got this error message? It could sound like YK is on to something, basically that your settings are off.

You wrote: "While we were able to read flash data from chip. We compare it with original it doesn't match." Are the file you want to upload equal in some parts with the file you read back or are they completely different? If the later it sounds like you haven't been able to flash the device at all.

   

BTW, we also try to put chip which is working on other board, but in this board it still not working.
We are mounting it to 240 degree in Owen. Also, we have many capacitors on board as well for overcome fluctuations in signals.

We are also thinking that lot of CC2530 could have bad chips with faulty flash inside. Is it could be possible?
We bought it from mouser.com some of from Taobao. We also use same ref crystals of Epson that is provided from ti.com ref design.

I'm still trying to understand this case:
You wrote "BTW, we also try to put chip which is working on other board, but in this board it still not working."

If I understand you correctly here this error follows the board and not the chip, is that correct?

Meaning if you take a chip from a non working board to a known good board it will work but if you take a chip from a known good board and place it on a failing board it will still fail?

We dont understand root of the problem. Either board is faulty or chip. But more or less debugger detect it and write data. But data in flash when we read back it is not match with original at every row values are changed only at beginning some of line written correctly then all are bad.

we have several non working boards. we also have several working boards of the same type that are working very reliably. In fact design is proven for some time already, only thing is that we have dead on arrival cc2530 ICs in some %. If cc is fine from start then board works quite ok.

on non working boards we tried to exchange IC around 7-8 times. we used new ic and ic from boards that are working. no luck.

we replaced crystals. we re soldered crystals. no luck. we don`t see any problem in traces (as explained we have more then one working boards of the same types).

My first guess will be a marginal hardware issue. Meaning that something on the board is borderline and hence works in some cases and in some cases not.

I can start by doing a schematic and layout review of your board to see if I can see something that looks strange (send me a friend request if you don't want to share the design publicly. Schematic as pdf, layout as gerber)

I assume that you have checked for assembly errors (typically mounted a cap instead on a resistor etc or wrong values)

Just sent you request.

If possible pls share your email id so i can share files.

Dhaval

Any updates? Still waiting...!!!

I offered you to send boards, my assumption was that I was waiting for you.

Hi Torstein,

Sorry for misunderstanding of ours.

But, We need 50k for sensors, and 100k for ventilators CC2530s so it is quite a risk or us to produce something that we have problem knowing that complete series of pcb can be bad.. If you see there are als0 other TI-ICs in design.

We need to make it sure it is a mistake of chips inside flash or our boards issue not really to debug our boards.

What we are suspecting is some batch of CC2530 is suspicious of being bad. What do you think about it? Are you aware of such problem?

we have few working board and some bad ones but we can prepare. We can also send batch of bad IC that we suspect. We also reorder some fresh from Mouser so would like to assemble few more boards in few days.

Awaiting for your kind reply,

Warm Regards,
Dhaval

We haven't seen a problem like this before as far as I know so I doubt that the chip is the issue. Please send the material you think is relevant.

Ok, We are going to send it to you soon.

Thx!

Thanks for letting us know.