Does DO-178C require static code analysis for level A software? Does DO-178C have any guidelines on using static code analysis for level A software?

As per Do-178C:  


  Section 6.3   Software Reviews and Analyses
  Reviews and analyses are applied to the outputs of the software development processes. One distinction between reviews and analyses is that analyses provide repeatable evidence of correctness and reviews provide a qualitative assessment of correctness. A review may consist of an inspection of an output of a process guided by a checklist or similar aid. 
  
  An analysis may examine in detail the functionality, performance,
  traceability, and safety implications of a software component, and its
  relationship to other components within the system or equipment


Can this achieved by Static analysis ? Some of the tools like polyspace which has misra standard checks
DO-178C is a means of compliance, so it sets out what you need to do to show you are meeting your required safety levels in your design.  It does not give advice on what methods you might use along the way.

I have seen static analysis used as part of the process, often with hardware integration and system testing.

DO-178 tools need to be qualified for DO-178 if you are using them to test your software.  I am not aware of anyone successfully using tools qualified for other standards (e.g. MISRA) in avionics.