Yes indeed it was a simulation. Still very valuable as long as it replaces
nasty debugging...
I've solved the issue. The problem was the length of the ADC procedure.
It's good to know/remember that if use only four ADC channels from 23
available (PIC18F25k50):
- all registers which can be set
Hi guys,
This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot
Build Reason:
Build Source Stamp: HEAD
Blamelist: rob.jansen
Build succeeded!
Logs are attached.
sincerely,
-The Buildbot
--
You received this message because you are
Branch: refs/heads/master
Home: https://github.com/jallib/jallib
Commit: cf2e146811bbba34bbd2c42bfb65328a00ec548d
https://github.com/jallib/jallib/commit/cf2e146811bbba34bbd2c42bfb65328a00ec548d
Author: Rob Jansen <12682653+robjanse...@users.noreply.github.com>
Date:
Am Samstag, 13. November 2021, 12:27:04 MEZ hat vsurducan
Folgendes geschrieben:
"Old jal (Wouter's) had a feature for testing computation at the compile time.
I realized it was very useful even if using constants for testing math
routines."
If that is the case, it's still no
Thanks Rob, I've done this but perhaps I've missed something.
I'm thinking of moving the ADC reading completely in the ISR.
thank you!
On Sat, Nov 13, 2021 at 1:40 PM Rob CJ wrote:
> Hi Vasile,
>
> I am not sure what you are doing but if you read words in a main loop that
> are changed
Hi Vasile,
I am not sure what you are doing but if you read words in a main loop that are
changed (written) in an interrupt routine you can get data corruption since
more cycles are need to write a word (or read it).
The easiest way to fix this is to disable all interrupts (or at least the
Hi Kiste, this is the way I'm debugging right now, not on LCD but on PC via
USB (that's because I'm using the USB ).
Old jal (Wouter's) had a feature for testing computation at the compile
time. I realized it was very useful even if using constants for testing
math routines.
My problem is related
Hi!
_error is meant to produce an error whenever it is compiled. You can only use
it with constants:
if target_clock<1200 then _error "Need at least 12MHz for this program"end
if
If there's a variable in the if statement, the content will have to be
compiled, and so the error is raised.
Hi Vasile,
Thanks for the update. I found something strange. Given the code below.
include 18f4550
var byte i = 0
if (i == 100) then
_error "Is 100"
end if
When I compile this I get:
jal jalv25r6 (compiled Oct 29 2021)
generating p-code
16858 tokens, 151522 chars; 3221 lines; 3 files
