Menu ▾ ▴

um/mod problem in FF3.4 on PIC18F

Open Discussion
Simon
2010-03-04
2012-11-19

  • Simon

    Simon - 2010-03-04

    Hi,

    Am I doing something wrong here?

    hex  ok<$,ram>
    ram  ok<$,ram>
    111 111 um* ok<$,ram>2321 1
    11 um/mod  ok<$,ram>0 0

    I expected to get the result 1120 1

    Regards,

    Simon

     

  • Pete Zawasky

    Pete Zawasky - 2010-03-04

    You appear to be correct, Simon.
    I get the same result also using  u*/mod.

    FF3.4  PIC18F6527

    Pete

     

  • Simon

    Simon - 2010-03-04

    I think the problem is that :

    rlcf  Abank, F ,A

    does not seem to set the carry bit

    Simon

     

  • Simon

    Simon - 2010-03-04

    Done some more checking…

    Abank relies on FSR2 - a 12 bit register.

    This is why it doesn't work.

    Simon

     

  • Pete Zawasky

    Pete Zawasky - 2010-03-04

    Hopefully we will hear soon from Mikael describing the division code.
    … unless he is on Winter vacation in a sauna or cross-country skiing…

    Thanks for reporting this one.

    Pete

     

  • Mikael Nordman

    Mikael Nordman - 2010-03-04

    Thanks for reporting it. I will fix it in FF 3.5.
    It will probably come out this  week.

    FF 3.5 also contains some new functionality.

    - HW flow control

    - A HOLD area for each task.

    That is needed for number formatting in background tasks.
    Started to write to a LCD display with a deferred EMIT
    from a BG task and discovered the problem with the HOLD area.

    Cheers /Mikael

     

Log in to post a comment.