I deleted all the code and defines
did everything from blank sheet, and now it works properly....
I deleted all the code and defines
did everything from blank sheet, and now it works properly....
once again a failure to produce a compliable example that demonstrates the problem
proof again in the pointlessness of snippets
a complete waste of effort
well done .... not
Warning I'm not a teacher
Well, if you're into scrolling thru 500+ lines of code.....
I'm just trying to make things simpler![]()
who wants that . 500 lines of chicken scratching's, no way i would even look at itWell, if you're into scrolling thru 500+ lines of code.....
I'm just trying to make things simpler
post the simplest compliable program that shows the problem. [if you can 99.99% odds you cannot ]
code snippets generally don't cut it, we need to see the config settings, osc speed var declarations , port settings etc....
[use code tags] please
its not hard
just going through the process of making a provable example will help you confirm that the problem
is elsewhere
you keep trying to claim compiler errors , i have not seen one in core code for at least 10 years
Warning I'm not a teacher
Compiler errors?
try to write or read past available eeprom - no errors will be given
I know, this may be called not a bug, but a feature, but even on ancient ZX Spectrum there was an error code "Index out of range"![]()
Yes, because - as we've discussed before - your beloved old ZX Spectrum (RIP Sr.Clive) ran a BASIC interpreter so it COULD check such things at runtime.
With PBP there is no interpreter running, it's COMPILED code so there is no way for the compiler to know, before hand, that value n that you just read from an external EEPROM points outside of an array.
Bookmarks