It is interesting that flash_info says that size is zero.
BF says your fw not support to logging.
In your flash_erase test did you use the exact Cleanflight GCS and firmware version (V1.10) from successful user pointed at by @f5soh?
(Since you already replaced the flash chip) It seems that one of these is probably true:
- solder blob
- connection not soldered
- bad / broken trace
- incorrect board traces design
- bad CPU chip
- wrong or missing components (such as flash CS pullup or voltage regulator)
- your version of BF does not access the external flash chip
- bad voltage regulator
After using Cleanflight V1.10 I would probably use CC3D schematic and a volt ohm meter to check the CPU to flash connections (or I think you maybe already did) and a few other things like flash CS pullup value (R17 should be 10K) and VCC. CC3D schematic can be found at "hardware/Production/CopterControl 3D/CopterControl 3D Schematic.pdf"
(not saying the following is the problem, just information for you) Some Sparky2 FC boards have a problem with baro chip. It turns out that the reason is that clone board maker used different voltage regulator. That would have been OK, but the different voltage regulator needed a different capacitor for it's precision voltage reference source and made bad power with the incorrect capacitor.