ZBasic Forum

There isn't a board with everything you want. The closest would be something like the MT-DB-4. You would have to attach a USB-TTL Serial converter to the RX/TX. You would also need to program your own ZX bootloader/firmware and figure out the pins to use for everything.

I built a "C" based metronome 12 years ago for my kids who play music based on a Circuit Cellar AVR prize winner from 2004 . It was fine for a while but as they became more accomplished they moved to a more professional Metronome like this one from Korg which only costs <$25. I have the Ea...

Ha! I saw that subject line and immediately thought I'd be reading about a new 64-bit ZBasic product. Yeah! Alas, no. A skilled programmer could create a 64-bit integer and floating point library using all of the constructs that already exist in ZBasic. Wrapping some 64-bit C code in native mode wo...

As no-one has replied to this, I will give you a few hints without actually writing the full code for you. Math is shown in italics and code in bold . I don't know what you are going to do with the 64-bit answer but you will need a way to store it as two 32-bit integers. Assume we have a constant fo...

Save yourself a lot of trouble and use one of the C function libraries that already exists and wrapper the native code. You can do it all from scratch but look out for all of the shortcuts people have used such as DFTs, fixed point arithmetic, dividing by powers of 2 etc. I have only done FFTs on a ...

Have you seen this google project for the ECU? Probably provides a very good start for what you need. You could use the C code from the library in a ZBasic native mode application.

Thank you for the quick fix. It compiles but unfortunately my SD card is not recognized ("di" interactive command returns 1 instead of 0). I will have to investigate further myself.

Probably something very simple, but this source code for this example does not compile. I get a whole set of errors which point to the .H file definitions not making into the ZBasic source compile e.g. <snip> FatFS.bas&#58;112&#58; Error&#58; reference to undefined identifier "f_wri...

I have not heard of this before. Is this coupling an "error" in the ATMega1284P design? It's nothing more than a signal being induced on another conductor, typically by capacitive coupling. It also know as "crosstalk". The effect can be seen using an oscilloscope. Usually, it do...

The following line in your PJT file or on the command line will suppress the warning: Be careful because it suppresses it for every routine.

That does seem to help. Why does OpenPWM not automatically set the port as an output? You would need to either call it twice or set both OCR ports. Worst case add something to the documentation and example code which sets the port as an output, acquires the timer semaphore and then calls OpenPWM. I ...

You may have misunderstood my intent. The original routine contains floating point math. I removed that math from the routine and used it outside only for displaying the output value for humans. For code purposes I suggested returning an integer and then do integer comparisons like this: Private Con...

If your app doesn't use any SW UART channels, you can inform the compiler thus by using: Option ComChannels 0 While I understand the intent of protecting the programmer from self-induced errors, I would also say that the solution is non-obvious. Either some text should be added to the chapter on na...

When the compiler doesn't know the value of the port in DefineCom, it assumes it is always a Software UART which is incorrect. This is only true for DefineCom3. The following code 'Private inputQueue&#40;1 to 100&#41; as Byte Public Sub Main&#40;&#41; Call OpenPWM8&#40;1, 50.0, z...

Application note AN220 is "Interfacing a Parallel LCD". For native mode devices it is possible to eliminate the use of PulseOut() and therefore remove the dependency on a timer, freeing it up for another use. The trick is to use the new library functions recently introduced named DelayMicr...