[Amforth] [Solved] @ vs c@ (was: rshift not zero padded)

2020-09-19 Thread Erich Wälde
Hello Mark, so you found the subtle difference between @ and c@, congrats! :-) Mark Roth writes: > So because of grabbing a word it seems that I was bringing in the PINB > register as well that had a value in it. So that is where the extra bits > came from. > > : cylon >> $ff ddra c! 1 porta

Re: [Amforth] Ref Card Generation quo vadis?

2020-09-19 Thread Mark Roth
Hello Tristan, Erich and AmForthers around the world. Tristan, I really like the direction you have gone in. Coupling the build process with the local refcard really is a solution that I can put my support behind. When push comes to shove what really matters to the end user? The words that have be

Re: [Amforth] Ref Card Generation quo vadis?

2020-09-19 Thread Tristan Williams
Hello Mark, Erich, AmForthers, I made some more modifications to the perl reference card script so that it will write out an AVR8 build specific reference card in html. Below are example outputs for the stock UNO build and a custom build https://tjnw.co.uk//amforth-6.92/appl/arduino/uno.html http

Re: [Amforth] rshift not zero padded

2020-09-19 Thread Mark Roth
So because of grabbing a word it seems that I was bringing in the PINB register as well that had a value in it. So that is where the extra bits came from. : cylon > $ff ddra c! 1 porta c! > begin 40 ms > 7 0 do porta c@ 2* porta c! 40 ms loop > 7 0 do porta c@ 2/ porta c! 4

Re: [Amforth] rshift not zero padded

2020-09-19 Thread Mark Roth
Okay, hmm. It seems to be because even when I store a value of $80 in PORTA, if I read it right back like that I'm getting a word. Which is actually what I'm asking it for by using @. So I would read back $ED80. Changing it to use the byte size c* and c! was the problem there. Thanks, Mark On Sa