|
Re: tinySA.ino for Nano compiles fine, but is 'too large' to upload...
Gary,
After a little bit of cockpit errors (mostly selecting the right board support package and getting the Nano programmed) I got the Nano set up. In my case I had to use the following settings to get things working (see screenshot attached to this message). I also had to select just 'Upload' because upload with programmer must mean that I'm using an external programmer instead of the onboard USB. One more, I made sure I'm using the Chinese CH341SER.exe to load the COM driver - at one point that was an issue (I thought) and I used ZADIG to reprogram to another driver...THAT was not the way to go.? So I have the Nano loaded and it's ready to play. This afternoon I'll build the filter and the adapter card that will hold the Receive and LO boards so I can just plug them into my setup. I also have to build the filter assembly and get that completed, too. I may set my Nano up for 3.3V first by doing the regulator exchange and cut the required traces, too. More on that as I have it. Can you share your wiring scheme with me so I know what pins do what on the Nano? I know you did a slightly different way to make it a lot easier to hook up but I'm not sure I ran across that in all the threads - so when you have a chance today please share that with me. More to follow - stay tuned... 73 de Marty, KN0CK |
|
Re: TinySA.ino GUI testing
#tinysa
On Sun, Feb 16, 2020 at 02:16 AM, Jerry Ponko AC9NM wrote:
ESP32 & 2.4" touchscreen (320x240) SPI displayGlenn (VK3PE) and I have been cogitating building the SA using an ESP32. I might suggest?for that processor, try the for the ILI9341 display. It supports both the display and touch screen. I haven't tried the?touch screen capability yet, but we used that library in the we recently completed and the display part works great. The library also supports a number of other display types and can be used on the ESP32, the ESP8266 and STM32. EDIT: The Arduino IDE can handle using both cores on the ESP32. Look at the code for the above mentioned VFO project to see how that works. In that software, one core handles updating the display and the other does most of the other work. ? -- John P. WA2FZW |
|
Re: tinySA.ino for Nano compiles fine, but is 'too large' to upload...
Gary,
WOW..! Thank you posting that sketch..! This will give me the ability to construct and test my hardware until I can use the 'Blue Pill' board to add a local display. What I've come to learn on this project is that it's not as 'prefab' as I first thought - which is fine. I wasn't aware that the original codebase was tailored for a Protoneer board - I learned that from Jerry last night. I also learned that once I got a clean complie once all the resources were present it would outstrip the memory capabilities of the Nano by a long way. So the upshot to all this is I got a wonderful education on the codebase and boards it's likely to work with depending on what display and other resources are present...All that is great stuff..! So I am going to install the code you uploaded and get my setup running today so the hardware part is done and known working with the PC program - your upload will REALLY help me get things developed today. I greatly appreciate you doing that, otherwise I'd be tearing out the display and rotary control code myself and have that complication slow me down from building hardware. I will do the 3.3V Nano trick today to see how it'll play with the hardware - not having the ILI9341 display to contend with will REALLY help with the hardware build checkout. MANY THANKS for the upload, Gary - more as I have it later today... 73 de Marty, KN0CK? |
|
TinySA.ino GUI testing
#tinysa
Jerry Ponko AC9NM
Since I haven't gotten all my hardware to build Erik's TinySA, I thought I'd start testing the GUI/touchscreen with different MCUs and Touchscreens to make a stand-alone SA using the Arduino IDE.
ESP32 & 2.4" touchscreen (320x240) SPI display Yesterday I tried using a DOIT ESP32 DevkitV1 and the standard ILI9341 2.4" touchscreen. The display works fine but the touchscreen library, XPT2046_TouchScreen, needs to be modified: The touchscreen y-coordinate is reversed in when display is in landscape mode. The solution is to add another case to void XPT2046_Touchscreen::update() in XPT2046_Touchscreen.cpp atter line 170 such as: case 3: xraw = x; yraw = 4095 - y; break; And then modify XPT2046_Touchscreen.h line 53 to be: void setRotation(uint8_t n) { rotation = n % 5; } -------- I filed this as a bug report with the author, Paul Stroffregen, on Github but I don't know if or when he'll make the changes. From looking at the Espressif esp32 forum, it looks like nobody thinks this driver works with the esp32. I would expect other esp32 variants to also work such as the esp32S as long as they have enough GPIO pins. The program storage and SRAM usage is less than 15%. As a plus, the esp32 has two cores @240MHz clock and you should be able to disable the wifi/bluetooth to cut down on the noise generated buy these components. I know you can run threads tied to a specific core with the esp-idf but I doubt the Arduino IDE will have any support for this feature. Arduino Mega2560 and 3.95" (480x320) ST7796S touchscreen shield (photo attached) What's nice about this display is its size and that it's a shield that plugs directly into a Arduino Mega2560 or standard UNO R3 board. It's a 8-bit parallel display with a SD card slot so using it on a MCU witch doesn't have enough GPIO for all your devices will be a problem. The Mega2560 while bigger than an UNO has a lot more memory than a Nano and lots more GPIO. Even so, the TinySA.ino sketch uses about 18% of storage and 77% of SRAM so it's still a tight fit. (In reality, 100% usage is the goal but not practical). The graphics uses the MCUFRIEND_kbv and Adafruit_GFX libraries so not much was changed since functionally it's the same as the ILI9341 driver. The touchscreen library, TouchScreen, which is based on the Adafruit_TouchScreen library, on the otherhand, isn't working properly yet. It's a four wire touchscreen. There's a Mini Mega out there that's much smaller but for a 16MHz MCU it seems a bit pricey ($7-$12). Arduino Mega2560 and 2.4" SPI display Not tested but I will give it a try after I finish testing with the 3.95" touchscreen. ESP8266 and 2.4" SPI touchscreen display Works fine, plenty of memory, speed but not enough GPIO pins left any else.. STM32 Maple leaf Still waiting for them to arrive. But I suspect it has enough memory to do the job. I haven't tried to compile it in the Arduino IDE to see what libraries will be rejected, etc. My first choice would have been an Arduino Pro Mini for the MCU because it doesn't have USB or Wifi which can generate noise but the memory is just too limited. My next choice would have been an esp8266. They're inexpensive but don't have enough I/O. I do look forward to testing with the STM32 Maple Leaf. FYI: The serial command-line interface menu system continued to work in all cases. Jerry Ponko, AC9NM |
|
Re: tinySA.ino for Nano compiles fine, but is 'too large' to upload...
Jerry,
What's rfeally odd about this is that the .ino file I'm using is the same one from the file area on this forum for the tinySA (tinySA.ino) and just by compiling it with the required display header file (Adafruit_1306.h) the sketch gets bloated enough that it can't even fit on a Nano - - yet others are using the same code and are able to load it on a Nano. So I wonder why I'm having the issue..? Guess I'll wait until morning to see if anyone else can shed some light on this.? I took your suggestion and tried programming the 'Blue Pill' using my ST-Link V2. There's a compiler issue that appears to be tied to the pinout: Arduino: 1.8.10 (Windows 10), Board: "Generic STM32F103C series, STM32F103C8 (20k RAM. 64k Flash), STLink, 72Mhz (Normal), Smallest (default)"
?
tinySA:69:16: error: 'A4' was not declared in this scope
?
?#define TFT_CS A4
?
..... ...this also goes for the A5 and A3 pins, too. Apparently, the Nano uses those, but those pins may be different for the 'Blue Pill'...that's my only correlation on that (maybe). Joreg has compiled the code for the 'Blue Pill' board and has he local display working - I recalled that he mentioned there could be pinout differences between the Nano and 'Blue Pill'. Again, guess I'll see what your opinion is along with any others on this...Not making the headway I thought I'd have today getting a board ready for the rest of the hardware... :-/ 73 de Marty, KN0CK |
|
tinySA.ino for Nano compiles fine, but is 'too large' to upload...
Well...Since I am having no luck getting the Windows drivers working with my 'Blue Pill' board, I switched over to the Nano and attempted to compile and upload the tinySA.ino sketch into my Nano (prior to doing the hardware fix for 3.3V). Compiles fine when I installed the Adafruit_1306 libraries and the header file (Adafruit_1306.h) into the project. Compiles clean, but it won't upload to my Nano because it says the following:
Arduino: 1.8.10 (Windows 10), Board: "Arduino Nano, ATmega328P"
?
Sketch uses 31462 bytes (102%) of program storage space. Maximum is 30720 bytes.
?
Global variables use 1974 bytes (96%) of dynamic memory, leaving 74 bytes for local variables. Maximum is 2048 bytes.
Sketch too big; see http://www.arduino.cc/en/Guide/Troubleshooting#size for tips on reducing it.
Error compiling for board Arduino Nano.
?
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
...And I have tried other Nano variants of the board support package (ATMega328P (Old Bootloader)) with similar results - can't upload. So I tried commenting out the display in the following line: // #define USE_DISPLAY 1 ...and it gives me a compiler error later in the compile that I don't think I should have to fix.? Is there a way to get this compiled so it'll make the upload happy? Is there a variant to the code that everyone else is using with their Nanos that will compile better than what I thought? Until I can get the 'Blue Pill' issue fixed, I would like to get the Nano going around the hardware and then use the PC Windows program to play with the tinySA just to get 'stick time'...But so far the stick is beating me to a pulp with getting either the Nano or the 'Blue Pill' going... :=/ Any help with this will be GREATLY appreciated - let me know where I'm going wrong... 73 de Marty, KN0CK |
|
Re: Hit a wall in compile...What am I doing wrong..?
Joerg,
I was able to use my ST-LINK V2 programmer to get the 'generic_boot20_pc13.bin' into the 'Blue Pill' board - that went fine. However, I'm stuck with the Windows drivers for the USB port. I did a search for how to load those drivers and I came to a procedure that installed the USB and Serial drivers for the 'Blue Pill' (wdi-simple.exe) but my board is still not recognized with a COM port - it shows up as an unrecognized USB device. In the meantime, I did load the correct board support packages for the Generic STM32F103 series and that installed fine, too, So I'm stuck at that place where I cannot get a COM port for the 'Blue Pill' board when I try to use the USB on the 'Blue Pill' board. However, I read that I can use the ST Link to upload my sketch to the 'Blue Pill' board directly, so maybe that's the best alternative for now. If you have your code in the form of a .bin file (or even if it's the .ino file format) I will try uploading it to my 'Blue Pill' board that way. At the same time, please let me know what I/Os you're using for your project so I know how the hardware will hook up to the 'Blue Pill' board. Keep me advised, Joerg - thanks..! 73 de Marty, KN0CK |
|
Re: my schematic diagram
On Sat, Feb 15, 2020 at 04:05 PM, Glenn wrote:
the specified filter appears to be obsolete and hard to get in VK at least. I wound up ordering these: ?(the seller kindly added the matching network performance data in an image also with an image of the module he tested also of the single filter design) ?(decided to go with the dual since can jumper with a 0 ohm resistor to study effect of using one SAW filter and maybe other matching network or filter design) ?(will have way more than I'll ever use, so for postage and maybe one dollar I can send anyone who needs some) ?(mdflyelectronics sold out after I ordered, so was cancelled regarding the 52 values 1300 pieces kit, so found this one since I don't have any inductors and have resistor and capacitor 0603 kits) also sells single SAW Filter PCB's and cases as well as other parts too.? Any thoughts, questions, comments and/or suggestions regarding this model filter? |
|
Re: Hit a wall in compile...What am I doing wrong..?
Marty,
it is quite some time ago, that I bought my blue pills. But as far as I remember, they do NOT come with the Arduino bootloader. Initially you can only upload programs using either a separate USB-serial interface or an ST-LINK adapter. With those, you can flash the Arduino bootloader into it. You can find a description of that here?. BTW: I with my board no modifications of the USB interface were required. After that you can use this board setting in the IDE (you have to install support for those boards before): -- Joerg, ex-DB2OO |
|
Re: Hit a wall in compile...What am I doing wrong..?
Joerg,
While I'm at it, the Blue Pill board is programmable through the USB port to upload a sketch, isn't It? Mine is fresh from Amazon. In the IDE environment, which board settings do you use to upload the sketch? Let me know that, too. Many thanks in advance -? 73 de Marty, KN0CK |
Marty Wittrock
John P
jafinch78 .