-
Notifications
You must be signed in to change notification settings - Fork 189
FAQ and Errata 0.5 Boards
-
Q: Does the 0.4 firmware run on the 0.5 boards?
A: Yes.
-
Q: If I connect the touchscreen according to the 0.5 schematics (R30-R34), will it work?
A: Yes, but not with the firmware for 0.3/0.4 boards. You should connect the wires according to the instructions for 0.4 MCU pinwise (see below). More details are on the Modifications page in this wiki.
To use v0.4 firmware on v0.5 boards with touch enabled:
-
fit 0R R30-R32, since these are connected to the right Touch Panel MISO,MOSI,SCK on v0.5. This was not the case on v0.4.
-
Do not fit R33/R34, use the PA4/PA9 pins of the MCU to link IRQ and CS. PA9 is available on the ESP8266 header.
-
Q: What if I connected the touchscreen as shown in the 0.5 schematics, is there a way to get this to work?
A: Yes, but you have to compile the firmware by yourself with the right switch set in the build configuration, see below. Drawback: Since the 0.5 touchscreen pins (PA13/14) are the live debugging pins, no live debugging will be possible if the touchscreen connections for CS and IRQ are fitted as intended in 0.5 schematic. This makes it not very attractive for the developers to develop support for this touchscreen configuration, since this means loosing a real time and pain saver.
If you use "make EXTRACFLAGS=-DMCHF_BOARD_0P5 clean all" to create the mchf.bin for 0.5 board with the 0.5 touchscreen wiring . See pull request #582 for more infomation.
-
Q: Does the firmware support the Wifi ESP8266-01 option?
A: No.
-
Q: Will it be supported in future?
A: If someone contributes software for talking to the ESP8266 module, yes. Challenge is here that the ESP8266 module uses the some pins of the STM32F4 which are used in 0.4 boards for touchscreen operation (PA9).
-
Q: Will you integrate my Wifi code?
A: As long as it is cool and does not break firmware usability for others without the module, why not?
-
Q: I heard, that there is no ST-Link port on the 0.5 revision.
-
A: This is true. P8 on 0.4 and 0.6 are a debug port, P8 on 0.5 is next to useless and contains no SWD debug port.
-
Q: Is there a way to still a debug access?
-
A: Yes but it is not trivial. PA13 (SWDIO) and PA14 (SWDCLK) are on R33 and R34 (CPU side). If you followed the instruction to modified for touchscreen operation for the standard firmware, then these are free to use. But nRST is only on Pin 14 of the processor, it is not routed. Debugging and flashing should work without nRST, but if not, it is worth trying to connect nRST.
Issues found with the 0.5 PCB etc.
On the RF board R92 silkscreen is duplicated. PA bias should have R82 instead. Found by US7IGN
- Supported SDR Hardware
- UHSDR: Manuals
- mcHF: Building your own SDR
- OVI40: Building your own SDR
- UHSDR: SW Installation on SDR
- UHSDR: Theory of Operation
- UHSDR: SW Development
- UHSDR: Supported Hardware
- UHSDR: Manuals
- Building a mcHF SDR
-
Building a OVI40 SDR
- UHSDR SW Installation
- Theory of Operation
- UHSDR SW Development