@bharadwajtk - I didn't have a problem using this method with Raspbian, although it was a while ago on a model B. But I did find it a bit flakey when adding it to the NOOBS recovery program in recovery.cmdline when I was trying to overcome my DHCP not working properly from a directly connected laptop connection (timing issues).
Completing more parameters to the ip= parameter often helped. I did wonder if that was a timing issue too.
Do you need to change this static IP address often, or is it just the case that you need to be able to set it once after installation, but you want to set it from a Windows PC?
Are you running headless?
Did you install from NOOBS, or a direct image write?
I'm just trying to identify your use cases, as this is a common problem with various solutions.
I have a solution for a NOOBS installation called noobsconfig - https://github.com/procount/noobsconfig
. That allows you to set up Ethernet or Wifi network connection parameters on the SD card from Windows before you install Raspbian from Noobs and it patches the parameters during installation. It also includes a retro.sh script that allows you to do it retrospectively, i.e. after you have installed the OS. You could adapt that for your needs if you are not using NOOBS. Meltwater has adopted noobsconfig for his PiKitchen recipes https://pihw.wordpress.com/guides/pi-kitchen/
which provide many documented examples.
There is also a solution called rpi_conf from Abishur that does a similar thing, allowing configuration from Windows and copying configurations to the ext4 partition on boot, which doesn't assume noobs. I'm sure there are others as well.
@Joe Schmoe - noobsconfig enables me to set my network connection out of the box from Windows, but it only works with NOOBS because that allows me to hook into the installation process. That is not the case with a standard Raspbian image (say) that is downloaded from the RPF. Maybe what is required is a run-once boot script to be added to the standard distribution (like raspi-config) that can pick up a script or parameters from the boot partition (like Abishur's rpi_conf). Are there other use cases you have in mind that would not be covered by the above? I suppose the main issue is to create a user friendly OS independent tool that can set it up, too.