mean00
Clone FNIRSI replace with ST32F103C8
mean00 can you compile me the firmware for the fnirsi clone which has been replaced with st32f103c8 so that it has all the features in InDSO150, at first I wanted to compile it myself, but I don't know what configurations to change, thank you...
Please read carefully :
- The attached bin file is for a STM32F103C with FNIRSI button layout and WITH 128 kB of flash (~ all of them do)
- You NEED to also flash the bootloader first (to check it works power on the device with the OK button pressed ; you should see a usb logo on screen)
absolutely not tested
sorry I didn't give the result for a long time, it seems I got a STM32f103C8T6 clone from the 5 bluepills that I bought (high density 0x414 256Kb flash revision Z), so it only shows a white screen, I tried moving the STM32 again from the Fnirsi pcb to the DSO150 pcb and it only shows a white screen with InDSO150 v2.2, When using DSO_STM32Duino v1.7 it only shows a splash screen then a black screen, but strangely with DSO_STM32Duino v1.6 it can run normally. I have a feeling maybe this STM32 can't perfectly emulate the USB because I tried to flash it with the ST-Link firmware, but the message USB device is not recognized appears.
Just checking : did you flash the lnDSO bootloader first ?
If you boot with "OK" pressed do you see a usb logo ? If so, do you see a spinning circle ?
yes I've tried flashing bootloader v2.2 elf/bin with st-link first, and when turning it on while holding down the OK button it just shows a white screen.
My old STM32 runs perfectly on all versions of InDSO150 and DSO_STM32Duino
\
My new STM32 failed to run properly, and can only run with DSO_STM32Duino V1.6 and below, other than that it's just a white screen
Thanks for the pics, it helps. I noticed the 2nd says 256kB of flash ? While they are both C8T6 ? That's strange
yes, it's true that there is 256kB because I tried to maximize the file that I uploaded, and downloaded it again, the result is the same, it's not corrupt. I have tried the serial output of InDS0150 and DS0_STM32Duino, but it only writes "main". and I've also tried gdb with black magic probe, but the result target chips 0x00 and target can't be attached. I think I give up with this stm32 clone, I'd better buy a bluepill with the original stm32 first
I see 2 options : Size
One difference between stm32duino 1.6 & 1.7 is the former is <64kB the later is not. If you try the normal lnDSO 2.2 fnirsi version do you have something on the screen ? (! there is no bootloader for that version!) That version has 2 flags activated :
- Small footprint so it fits within 64 kB (no font anti alising, no usb, ...)
- Fnirsi PCB changes (button wiring)
If you have the wrong PCB, it will make the buttons not working but you should see something on screen
Screen ID
It may be the screen is different / not wired the same and not recognized
Maybe older stm32Dso fws were falling back in a nicer way to ILI9341 while more recent ones
dont work well in that case.
That would be "RD" signal that goes to the screen
At first I also thought like that, because I have a stock of CKS32 64kB and APM32 128kB.. but when I use CKS32 with option -DUSE_SMALLFOOTPRINT=True, it can run normally. Likewise with APM32 using lnDSO_FNIRSI_2.2.bin release, it works normally like STM32. I think my STM32 clone is really very poor quality
