prof-braino / propforth

Automatically exported from code.google.com/p/propforth
3 stars 0 forks source link

Loading EEprom 1430 bytes - different on windows and linux #198

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

From this post:

http://forums.parallax.com/showthread.php/146693-Propforth-v5.5-is-available-for
-download?p=1191368&viewfull=1#post1191368

Okay, here is a knotty problem. I am fastloading 1430 bytes of a lookup table 
to EEprom 63000-=64330, and I get good results in Linux and Minicom... But this 
does NOT work in a Windows and TeraTerm solution.

Any suggestions on the Best... not just any old .. way to resolve it. I decided 
it was just easiest to lower the Baud rate of the PropForth as it appears when 
the jump from 57600 baud to 228200 was made.. large EEprom writes may not have 
been considered.

I have asked the fellow with the Windows/TeraTerm to drop his baud rate to 
19200 and see it it all clears up.

****** WARNING ******
If you run a test, this file will overwrite addresses 63000-64430 of the 
EEprom. This will NOT conflict with with the PF file system if existing files 
are not written to that area. But if existing files existed the that area, they 
will be lost. 

Original issue reported on code.google.com by prof.bra...@gmail.com on 22 Jun 2013 at 3:41

GoogleCodeExporter commented 8 years ago
The error is noticed by his client, so this third person might just be doing 
something wrong.

Propforth should not behave differently between Minicom and Teraterm, should it?

Original comment by prof.bra...@gmail.com on 22 Jun 2013 at 3:43

GoogleCodeExporter commented 8 years ago
The file as posted has a lot of spaces, and overflows the fl buffer, change the 
multiple spaces to a singled space and it load fine in 5.5 DevKernel.

Original comment by salsa...@gmail.com on 22 Jun 2013 at 4:10

GoogleCodeExporter commented 8 years ago
Issue was too much whitespace, buffer was over filled. 

There is no bug to fix here. 

Original comment by prof.bra...@gmail.com on 7 Jul 2013 at 3:04