Weird. R6 and R7 still off & crystal not connected?
I put them back on since it seemed like the oscillator was not at fault. I made this assertion because using an internal oscillator made not change in behavior.
Concerning the boot mode, I'd like to be sure I understand the expected behavior when debugging the code. Boot mode is selected at about the fourth or fifth clock cycle after power on. This should mean that I should be able to step through mode code until after the system clock is initialized. Then maybe execute a few lines of code after that depending on the amount of clock cycles are required for each operation, correct?
If this is the case then what I'm observing seems to be the STM32 being thrown into a different boot mode even though I have BOOT0 pulled down with a 10k and BOOT1 wired to ground.
BUT, if it should throw the chip immediately into the different boot mode when debugging this is not the case.
I did hand assembled these, maybe I damaged these somehow. Although I can program the chip the entirety of the chip is not functional. I will admit that I had originally soldered these in backwards. They have two divets at opposing corners and I had it in backwards. I corrected this by using a hot air gun set to 280C and reseated the chip. I've done this with other chips in the past with no issue, but there's always the chance I did some damage.
I had thought that this wouldn't be the case since it does in fact program properly, but you never know. I've ordered some replacement chips and hopefully they'll be in by Monday.