HOW TO RECOVER FROM MISSING Web GUI ON BDA3 AFTER
UPDATING OLD UNIT TO NEW 2020+ FIRMWARE
------------------------------------------------------------------

The higher number of source files included in the new firmware releases
(made for new BDA3.14 streaming DAC) crash the file system of older
firmware releases resulting in non-functional web interface for the
controller (but not for the PI).  The works correctly but the only
web interface of the controller is the hard-coded upload page that
can never be deleted, for example
192.168.xx.xx/upload.htm    (an actual IP address may be different)

The new firmware releases in 2020+ handle the higher number of source
files correctly.  The solution is to upgrade the older BDA3 unit to an
INTERMEDIATE test firmware release 2020.04A which will load correctly
but will have the higher file number limit, that will allow updating to
the recent firmware without crashing.

What to do:

1) Put unit in Standby (red power LED) (*)

2) Upload the intermediate version BDA3_2020.04A let it reprogram
then reboot.  Wait a minute after it repowers itself, in case if tit
would try to reprogram internal logic circuit.  If the power LED keeps
blinking or stays yellow let it finish.  Do not use this release but
upload the final one.

3) Put the unit in standby (red LED)(*) then upload the final firmware
revision, for example  2020.06C or later

Note 1: firmware revisions issued in 2020 or later, destimed for the
BDA3 with the older mainboard (pre 2020, NOT PI-capable) need firmware
with revision number that ends with a capital letter.
BDA3.14 and BDA3 sold in 2020 equipped with new mainboards required
firmware ending with a lower-case letter.

The firmware release issued before 2020 for the BDA3 do not distinguish
between lower case or upper case letter suffix and are meant to work only
on the old units with old mainboards.

Note 2 (*):
  It is possible to upload the firmware in Power ON state and it works
just the same.  However an INTERMEDIATE firmware 2020.04A may be
sluggish in Power ON state that's why it is better to do it from the standby
state.

However if Ethernet is disabled in standby (this is to meet the low
standby power <0.5W regulatory requirement when sold in Europe) then it is
possible to re-enable it by re-defaulting the user configuration by
executing the following command from the Web GUI terminal tab:

%2330INIT222.
%2330INITfa.

(wait ~30 seconds until you see the feedback response #30INIT... )

Stan Bleszynski
Bryston
17/06/2020
updated
19/06/2020