alarmdecoder.com

I bought few ad2pi but 2 of them just don't work.
I'm trying to communicate with those using telnet on port 10000.
The first one is death, no answer at all.
The second one responds this on V command:

Code: Select all

V
!no!sn:ffffffff
!boot....................
!wait
!load

I tried upgrading the firmware on both without success.
Are those bricked? Can I save them somehow?

Boot loader is still good so not bricked. Just got to figure out why you cant flash the firmware.

How are you flashing new firmware?

A CLI utility should be installed on our image but it will expect to connect to /dev/ttyAMA0 and if you have ser2sock running or anything else who has AMA0 open at the same time the flashing can cause this type of failure.

If the firmware is damaged and it still trys to run then it will be much harder to recover on the Ad2Pi because it has no Reset/Reboot.

In this case its good to have a TTY Serial adapter a very handy tool to have around
https://www.sparkfun.com/products/12977 ... fgodwe4Jlw
With this adapter you in effect have an AD2USB when connected to a Pi board.

Again probably not your issue because you see a !load message so you are in the boot loader.

Re
Sean M

Thanks for the answer!
I stopped ser2sock and gunicorn and I finally could flash the firmware successfully!

The same procedure didn't work on my other ad2pi, it just seems dead (the led is blinking right).
Do you thing buying that cable could help in this scenario?

As long as you can see the bootloader, it is possible to reflash the firmware - suggest just keep trying - a ttl cable would eliminate the other software involved on the network appliance and would make it a COM Port on your local machine - either method should work - but if you can't get it, we are happy to do an RMA exchange. For RMA, just email ad2usb@support.nutech.com with a description of the problem and your return address.

I can't see the bootloader on my second ad2pi. I wll write an email, thanks!