| ??? 03/22/01 12:45 Read: times |
#10273 - RE: Too many falg bits in the code |
Hi Gil,
these are 2 fully different problems: 1. The bit space was limited to 128 bits. The minimal count of bits depends, how many different states you want to distinguish. So 128 bits can divide about 3 * 1E38 states. If you exceed the 128 available bits, you can also use other RAM with ANDing and ORing to separate the bits of any byte. 2. To compress the code size, I see no other way as looking on the code. Try first this routine, which consume the most Flash. Peter |
| Topic | Author | Date |
| Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many flag bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
RE: Too many falg bits in the code | 01/01/70 00:00 |