Force rebuild when memory.x changes

[e-Debussy]

I use app-template for my STM32F103C8T6 project. I found after you change the memory.x file (from wrong memory range to right settings), use the command:

❯ cargo rb hello
    Finished `dev` profile [optimized + debuginfo] target(s) in 0.08s
     Running `probe-rs run --chip STM32F103C8 --log-format=oneline target/thumbv7m-none-eabi/debug/hello`
Error: An error with the flashing procedure has occurred.

Caused by:
    No flash memory contains the entire requested memory range 0x00000000..0x00000130.

but in the memory.x (right version):

MEMORY
{
    FLASH : ORIGIN = 0x08000000, LENGTH = 64K
    RAM   : ORIGIN = 0x20000000, LENGTH = 20K
}

I found you should running the cargo clean first to clean the last building files, then run the command:

❯ cargo rb hello
    Finished `dev` profile [optimized + debuginfo] target(s) in 0.09s
     Running `probe-rs run --chip STM32F103C8 --log-format=oneline target/thumbv7m-none-eabi/debug/hello`
      Erasing ✔ 100% [####################]   8.00 KiB @  28.82 KiB/s (took 0s)
  Programming ✔ 100% [####################]   8.00 KiB @  18.21 KiB/s (took 0s)                                                             Finished in 0.72s
Hello, world!
Firmware exited successfully

I think this is not convenient for programming. Hope to fix it in the next version.

[jonathanpallant]

Fair point. We should mark that file as needing a rebuild using the build.rs file.