开云体育

Dave and Ohan,

Thanks. I'm going to try to use the ST-Link V2.0 units I bought so I can gain some experience with using them and the various C development environments. I've got quite a few STM32 discovery boards, "blue pills" etc.

In the past I've used st-flash on *nix to flash Mecrisp forth on to the STM32:



At the moment I can't even remember what hard drive I was using for that work as it was several years ago. The downside of having 2 dozen drives in caddies and swapping drives in a single computer, but a great use for old drives. And a safe way to play with odd ball stuff like Plan 9.

I'm rather tempted to load Mecrisp on the nanoVNA and try my hand at serious work in forth for the first time in almost 40 years.

Have Fun!
Reg

On Fri, 20 Sep 2019 at 16:18, Reginald Beardsley via Groups.Io <pulaskite=
[email protected]> wrote:

Dave and Ohan,
I'm rather tempted to load Mecrisp on the nanoVNA and try my hand at
serious work in forth for the first time in almost 40 years.

Have Fun!
Reg

The problem with forth is that nobody else is likely to want or be able to
contribute. There are many languages that have niche areas - Lisp, Haskell
etc. But the number of people knowledgeable in these languages is a small
proportion of the people able to write software.

Dave

--
Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales.
Company number 08914892.
Registered office:
Stokes Hall Lodge,
Burnham Rd,
Althorne,
Chelmsford,
Essex,
CM3 6DT,
United Kingdom

Yeah, Reg - Python is the future....!

Actually, Python is close to becoming the #1 programming language - educators, engineers and scientists have all created extensions.
Talk to forum member Rune about Python.

Also from today's news, Microsoft has a YouTube series for beginners:


From the article:
"A new video series, titled 'Python for Beginners', hosted by Microsoft Senior Program Manager, Christopher Harrison, and Business Development Manager at AI Gaming, Susan Ibach, has been launched by the firm. Comprising of a total of 44 videos, this series - as indicated by the name - isn't an in-depth study of Python, but rather, it just provides a foundation for the programming language. The course material is noted to be quick and concise, in order to encourage learners to start specifically looking into the areas that interest them as soon as possible."

Cheers,
Larry

On Thu, Sep 19, 2019 at 02:43 AM, <hugen@...> wrote:

I am discussing with the AA6KL9 to build a new firmware using the
STM32F303CCT6. If all goes well, it can be provided later. To replace the mcu
directly on the current hardware, you need to add a 1.5K resistor to the VCC
on the USBDP Pin. The DFU mode of the STM32F303 requires an external 8M
crystal to use USB, but STM32F072 does not need it, so you need to use SWD to
update the firmware. You need to prepare an ST-Link or DAP-Link.
BTW: The new STM32F072-based NanoVNA firmware already supports TDR.

Thank you!

ok, 8M crystal is normally not a problem for me, but for most nanovna owners F303 is then not real 1:1 replacement. We should probably, if we need more memory, stick on crystal-less USB STM32 (AN4879) , with pullup support, with DFU support (AN3155), LQFP48 package and ChibiOS support. Afaik STM32L433CCT6 should be good replacement, only pullup for USB necessary, and some ADC / clock / I2S changes to code, but it does need newer ChibiOS, which then does not compile with nanovna. Anyway, for myself i will probably solder crystal and use F303 (ADC/clock changes necessary), if i not manage to fix newer ChibiOS compile Errors with STM32L4x series.

tinhead

Forth is a niche language created for writing embedded software on very limited, bare HW. In particular, it is intended to allow you to write and test peripheral control software interactively. The STM32F072CBT6 is 2-4x the memory size of the machine Chuck Moore created it on to control the Kitt Peak radio telescope dishes and many times faster.

With so many people working on variations of the original C code. I'm not sure there is much point to my getting involved with that. Also, I think the use of threads is a major mistake from a software engineering perspective.

I have major issues with bugs and even more with code crashing, ever. Once you allow multiple independent processes to operate in the same address space, unless you use a segmented architecture al la Multics and the Intel x86 and 432, you leave yourself open to one process corrupting another.

In any case, I'm just an old man amusing himself. I've been fooling around comparing the TDR response of my 11801/SD-24 using a bare 3.5 mm connector and the nanoVNA open. There is as much difference between the two channels in both cases as there is between the bare 3.5 mm and the open.

Not quite sure how to interpret it yet. The trace calculated differences are much larger than the display suggests. That's symptomatic of small phase differences, but it's been a long time since I dealt with that and I don't remember yet how you handle it.

Have Fun!
Reg

Hello Erik,
Thank you for adding your extension to the Hugen nanoVNA version 0.1.1.

It would be nice to fill out in the "version window" the version number,
e.g.: 0.1.1 + scan, 1500MHz

It can be done in file ui.c line 385
#define VERSION "0.1.1 + scan, 1500MHz"
void
show_version(void)
{
...

See the screenshot nanoVNA_version-screen_0.1.1_DSC08138.jpg

73, Rudi DL5FA

Indeed, thanks

n Tue, 24 Sep 2019 at 10:28, <reuterr@...> wrote:

Hello Erik,
Thank you for adding your extension to the Hugen nanoVNA version 0.1.1.

It would be nice to fill out in the "version window" the version number,
e.g.: 0.1.1 + scan, 1500MHz

It can be done in file ui.c line 385
#define VERSION "0.1.1 + scan, 1500MHz"
void
show_version(void)

In the version of firmware in mine, which I don't know what it is, a

screen similar to that does display. But it is for such a short period, I
can't read it. I guess if I used a phone to video it, I could probably work
it out, but it is too quick for my eyes and brain to process.

Dr David Kirkby Ph.D C.Eng MIET
Kirkby Microwave Ltd
Registered office: Stokes Hall Lodge, Burnham Rd, Althorne, CHELMSFORD,
Essex, CM3 6DT, United Kingdom.
Registered in England and Wales as company number 08914892

Tel 01621-680100 / +44 1621-680100

A little confused on the firmware versions.

Is the source code available for the nanoVNA_900_AA ? Or is that already in the hugen-modified 0.1.1 ?

What I really want is the best of all worlds for using the nanoVNA while hanging from my tower at 110 feet. Being able to measure Z at the feedpoint with large font and display of R + jX. I'm perfectly willing to tweak the code to do that, but I need the large font version as the starting point.

Thanks,
Steve, N2IC

On Thu, Sep 26, 2019 at 07:12 AM, Steve London wrote:

A little confused on the firmware versions.

Is the source code available for the nanoVNA_900_AA ? Or is that already in
the hugen-modified 0.1.1 ?

What I really want is the best of all worlds for using the nanoVNA while
hanging from my tower at 110 feet. Being able to measure Z at the feedpoint
with large font and display of R + jX. I'm perfectly willing to tweak the code
to do that, but I need the large font version as the starting point.

Thanks,
Steve, N2IC

I created the AA version to better display Chinese. Since the TDR function does not have enough ROM to store Chinese fonts, I need to separate the AA version from the Chinese version and merge it with NanoVNA-H. If all goes well I will update on github.

hugen