Do you have a question? Post it now! No Registration Necessary
- Subject
- Posted on
- dsPIC33CH Vs dsPIC33F divide.
- 01-03-2019
- Clive Arthur
January 3, 2019, 11:18 am
I posted this on comp.arch.embedded, but there's little action there,
all the clever people must be here...
The new dsPIC33CH parts have a 6 cycle divide whereas the older dsPIC33F
takes 18 cycles. The number of cycles is not data dependent.
So I guess more Silicon for fewer cycles, but used how?
Cheers
all the clever people must be here...
The new dsPIC33CH parts have a 6 cycle divide whereas the older dsPIC33F
takes 18 cycles. The number of cycles is not data dependent.
So I guess more Silicon for fewer cycles, but used how?
Cheers
--
Clive
Clive
Re: dsPIC33CH Vs dsPIC33F divide.
No, there are plenty of clever people on comp.arch.embedded. But they
tend to stick to on-topic posts, and ones that interest them. I don't
expect there are a great many people using the dsPIC devices, and I
expect very few of these people are interested in how the new versions
do their division. They might be happy that new versions are faster at
division - but why is it of interest /how/ this is implemented?
Division hardware can be implemented in a variety of ways - wikipedia
will give you some suggestions. And if you are really interested in the
details, comp.arch is a better newsgroup.
Re: dsPIC33CH Vs dsPIC33F divide.
I know some ways of doing division in hardware, and I know where to look
for more details. (I've pointed you at a couple of good starting points
- one website, and one newsgroup.)
I haven't the faintest idea what method is used in the dsPIC devices,
and I don't expect anyone outside the inner circle of Microchip's design
team know either.
Does that help?
Another possible choice would be comp.arch.fpga. Those folks don't make
chips like the dsPIC, but they make algorithms in FPGAs.
Re: dsPIC33CH Vs dsPIC33F divide.
I am looking at the datasheet, and indeed it says on page 1
But searching for 'cycles' in the pdf finds this on page 45:
3.1.8.2 Divider
The divide block supports 32-bit/16-bit and 16-bit/16-bit
signed and unsigned integer divide operations with the
following data sizes:
The 16-bit signed and unsigned DIV instructions can
specify any W register for both the 16-bit divisor (Wn)
and any W register (aligned) pair (W(m + 1):Wm) for
the 32-bit dividend.
The divide algorithm takes one <-----------------------
cycle per bit of divisor,
so both 32-bit/16-bit and 16-bit/
16-bit instructions take the same number of cycles to
execute. There are additional instructions: DIV2 and
DIVF2. Divide instructions will complete in six cycles.
So, one would expect 16 cycles for a 16 bit divisor????
Could it be a typo (6 being 16?)
Did you measure the delay?
I do not have the chip else I would measure it.
Re: dsPIC33CH Vs dsPIC33F divide.
wrote:
We have gone to The Dark Side and do most embedded-system math in
floats these days. Some of the modest ARMs have hardware vector fp.
We have gone to The Dark Side and do most embedded-system math in
floats these days. Some of the modest ARMs have hardware vector fp.
--
John Larkin Highland Technology, Inc
picosecond timing precision measurement
John Larkin Highland Technology, Inc
picosecond timing precision measurement
We've slightly trimmed the long signature. Click to see the full one.
Site Timeline
- » I was offline for weeks
- — Next thread in » Electronics Design
- » Amusing electric car stats
- — Previous thread in » Electronics Design
- » XNRGI Battery
- — Newest thread in » Electronics Design
- » America's biggest mistake
- — Last Updated thread in » Electronics Design
- » litio low cost
- — The site's Newest Thread. Posted in » Electronics Hobby (Italian)