SequentMicrosystems / megabas-rpi

Command Line, Python lib, Node-Red and CODESYS driver for Building Automation Card
https://www.sequentmicrosystems.com
MIT License
8 stars 1 forks source link

Write fail during firmware update #11

Closed ddyer8 closed 2 years ago

ddyer8 commented 2 years ago

I recently (~1 week ago) updated the firmware on the board but am having trouble using RS485 comm, so decided to try another firmware update. Now I'm getting the following error:

pi@poolpi:~/megabas-rpi/update $ ./update 0 You are ready to update the firmware on your board. Your Raspberry Pi must be connected to the internet. We strongly recommend to disconnect all outputs from the board since they can change state unpredictably. Type "yes" (without quotes) to continue or anything else to quit: yes CPUID: 190025000357415636313320 Downloading firmware... Board version < 4.0 Done Programming the board... 2% Write fail! FAIL to write!

I have gotten anywhere between 2% and 5% complete before failure.

Sometimes I also get: read cmd NACK ret 0x00 !!! Bootloader no answer!!!

alexburcea2877 commented 2 years ago

Hi, Make sure nobody tries to access the card during the update.

ddyer8 commented 2 years ago

There are no connections to the card, but there are 2 other sequent boards and an Atlas Scientific whitebox T3 stacked on the pi. Do I need to unstack everything?

Thank you, Dustin

On May 28, 2022, at 12:56 PM, Alexandru Burcea @.***> wrote:

 Hi, Make sure nobody tries to access the card during the update.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

alexburcea2877 commented 2 years ago

Normally is not a problem to have more cards on the bus but is better to remove them. Make sure no resident program on the raspberry pi try to access I2C port during the update (NodeRED or running python or shell scripts).

On Sat, May 28, 2022, 19:00 ddyer8 @.***> wrote:

There are no connections to the card, but there are 2 other sequent boards and an Atlas Scientific whitebox T3 stacked on the pi. Do I need to unstack everything?

Thank you, Dustin

On May 28, 2022, at 12:56 PM, Alexandru Burcea @.***> wrote:

 Hi, Make sure nobody tries to access the card during the update.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

— Reply to this email directly, view it on GitHub https://github.com/SequentMicrosystems/megabas-rpi/issues/11#issuecomment-1140297378, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3ZCWWXO7U73BTTU3QJ26DVMJGKBANCNFSM5XG3DLLQ . You are receiving this because you commented.Message ID: @.***>

ddyer8 commented 2 years ago

there were no issues with the cards on the stack. I had a background process accessing the board.