68HC1 | 812A4 | 9S12DP256 | Bootloader | CodeWarrior | D60A | Debugger | DP256 | ECT | EEPROM | EVB | Flash | HC1 | HCS12 | I2C | IAR | ICC1 | Interrupts | LCD | M68KIT912DP256 | MC9S12DP256 | MC9S12DP256B | Metrowerks | Motor | MSCAN | Multilink | PLL | Quadrature | SDI | SPI | Transceiver | XFC

Uh, I must not be up to speed on how to remap memory.

The 2K EEPROM of the MC9S12DG128B is [0..0x07ff] on powerup. I was
going to quicly remap it to [0x0800..0x0fff] for compatibility, but I
had not noticed something before about INITEE (see 9S12DT128BDGV1.pdf).

I could supposedly remap it to "any 2K boundary", but with INITEE I
can only set [EE15..EE12]. I would need to set EE11 that does not
exist! That means I can only bump it up to 0x1000.

So I just pretended that bit 3 of INITEE was EE11, and it worked. Go
figure. Is all Freescale docs wrong?



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

--- In 6...@yahoogroups.com, "Jefferson Smith"
wrote:
>
> Uh, I must not be up to speed on how to remap memory.
>
> The 2K EEPROM of the MC9S12DG128B is [0..0x07ff] on powerup. I was
> going to quicly remap it to [0x0800..0x0fff] for compatibility, but
I
> had not noticed something before about INITEE (see 9S12DT128BDGV1.
pdf).
>
> I could supposedly remap it to "any 2K boundary", but with INITEE I
> can only set [EE15..EE12]. I would need to set EE11 that does not
> exist! That means I can only bump it up to 0x1000.
>
> So I just pretended that bit 3 of INITEE was EE11, and it worked. Go
> figure. Is all Freescale docs wrong?
>
I haven't checked the manual, but I'm sure you can set "EE11" on
DG128. I'm using the same mapping myself.

INITEE = 0x09;

should do the trick.

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

--- In 6...@yahoogroups.com, "Daniel Lundin"
wrote:
> I haven't checked the manual, but I'm sure you can set "EE11" on
> DG128. I'm using the same mapping myself.
>
> INITEE = 0x09;
>
> should do the trick.

Well my point is that I did do that, and it did work, so I was asking
if the documentation was right anywhere else. I see now that "V2" docs
for DG128 are corrected. Too bad the DG128B is not making any
reference to that.

See
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC9S12DG128B



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

Jefferson Smith wrote:

[...]

> So I just pretended that bit 3 of INITEE was EE11, and it worked. Go
> figure. Is all Freescale docs wrong?

certainly. It is nearly impossible to find all errors, at least it is
too expensive.

But Freescale should reduce the number of errors in the docs!

For example, the communication between support people and literature
people could be improved.

I simply can't accept if a new version of a document contains still
an error I reported several months before in a "support request".

Oliver
--
Oliver Betz, Muenchen

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

--- In 6...@yahoogroups.com, "Oliver Betz" wrote:
> certainly. It is nearly impossible to find all errors, at least it
> is too expensive.

Ugh, don't even IMPLY that they didn't "find" the errors. Customers
are continually flooding them with error notices. FSL seems to be too
disorganized and missing any sort of internal communication. I'm
disgusted with their ignorance! At the moment I am merely trapped into
using their product.
> I simply can't accept if a new version of a document contains still
> an error I reported several months before in a "support request".

I see that you realize the problem is communication, not just missing
some of the errors. I feel that the person that happens to get my
message merely disregards it as unimportant. For at least a year, my
request was ignored while the website insisted that one MCU, I think
the C32, had 2 gig of internal RAM. It is so stupid because it would
supposedly be so simple to remove the extra zeros, if only they were
organized to do so.

And yes, I have seen new revisions with the reported errors not fixed.
That's why I feel that some FSL contact said, "oh that's no biggie"
and discarded my note. I observe that they are only trying to appear
to be improving things constantly, NOT make it the best possible product.

That was the final straw for me... that there is never a final product
that I can just settle on. Many of you will say, "that's business". My
response: "that's why this world is doomed"



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

Hello All,
I need a lot ( ~2 Meg) of data storage and I was just planning
on bit-banging four 512k SRAMs with an HC12. It seems, however,
from my searching that Asynchronous SRAM is dying out. ST Micro
says they are discontinuing all of their SRAM products. On Toshiba's
Web site it says all of their SRAM products are end-of-life. Also
Samsung has all of their 5V SRAMs listed as end-of-life. Has anyone
else found this to be the case ? Is their another source that I'm missing ?

I'm starting to think my best option may be to go to a higher-end micro
and use SDRAM. Would anyone have any comments or advice ?
Thanks,
Jeff

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

--- In 6...@yahoogroups.com, "Jefferson Smith"
wrote:
>
> --- In 6...@yahoogroups.com, "Oliver Betz" wrote:
> > certainly. It is nearly impossible to find all errors, at least it
> > is too expensive.
>
> Ugh, don't even IMPLY that they didn't "find" the errors. Customers
> are continually flooding them with error notices. FSL seems to be
too
> disorganized and missing any sort of internal communication. I'm
> disgusted with their ignorance! At the moment I am merely trapped
into
> using their product.
> > I simply can't accept if a new version of a document contains
still
> > an error I reported several months before in a "support request".
>
> I see that you realize the problem is communication, not just
missing
> some of the errors. I feel that the person that happens to get my
> message merely disregards it as unimportant. For at least a year, my
> request was ignored while the website insisted that one MCU, I think
> the C32, had 2 gig of internal RAM. It is so stupid because it would
> supposedly be so simple to remove the extra zeros, if only they were
> organized to do so.
>
> And yes, I have seen new revisions with the reported errors not
fixed.
> That's why I feel that some FSL contact said, "oh that's no biggie"
> and discarded my note. I observe that they are only trying to appear
> to be improving things constantly, NOT make it the best possible
product.
>
> That was the final straw for me... that there is never a final
product
> that I can just settle on. Many of you will say, "that's business".
My
> response: "that's why this world is doomed"
>
They can build a 0.25um MCU but they can't handle the documentation
and website. For example they sent me their fancy newsletter, telling
me there was a new app note regarding the HCS12B family. What is the
B-family?? No documentation to be found on the website nor in their
roadmap.



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

--- In 6...@yahoogroups.com, Jeff McKnight wrote:
> Web site it says all of their SRAM products are end-of-life. Also
> Samsung has all of their 5V SRAMs listed as end-of-life. Has anyone
> else found this to be the case ? Is their another source that
> I'm missing ?

Maybe it has to do with RoHS. I'd ask sources or manufacturers about
it, or just try a fresh search on "SRAM memory"



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

--- In 6...@yahoogroups.com, "Daniel Lundin"
wrote:
> They can build a 0.25um MCU but they can't handle the documentation
> and website

Typical, really. Look at Microsoft in contrast.
MS can make an OS APPEAR real powerful, secure, neat, yet they cannot
make one that works.

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

--- In 6...@yahoogroups.com, Jeff McKnight wrote:
> and use SDRAM. Would anyone have any comments or advice ?
> Thanks,
> Jeff
>

idunno how or what you looked up specifically, but I see no trouble here:

http://www.samsung.com/Products/Semiconductor/LowPowerSRAM/index.htm

I just don't know if these families will cause trouble interfacing
with 9S12. Anybody know if 9S12X could use these without adding
interface logic?

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

Jeff McKnight wrote:
> Hello All,
> I need a lot ( ~2 Meg) of data storage and I was just planning
> on bit-banging four 512k SRAMs with an HC12. It seems, however,
> from my searching that Asynchronous SRAM is dying out. ST Micro
> says they are discontinuing all of their SRAM products. On Toshiba's
> Web site it says all of their SRAM products are end-of-life. Also
> Samsung has all of their 5V SRAMs listed as end-of-life. Has anyone
> else found this to be the case ? Is their another source that I'm missing ?
>
> I'm starting to think my best option may be to go to a higher-end micro
> and use SDRAM. Would anyone have any comments or advice ?
> Thanks,
> Jeff
>
Hi Jeff,

Have you considered using Serial Flash instead, especially if you are
going to bit bash a parallel interface. This is what we now use for data
storage:
http://www.sst.com/products.xhtml/serial_flash/25/SST25VF016B
Bigger / smaller versions available, all in an 8 pin SOIC. Interfaces to
the 5V SPI with a few level translators, and no need for backup battery.

David



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

Jefferson Smith wrote:
>
> --- In 6...@yahoogroups.com , Jeff
> McKnight wrote:
> > and use SDRAM. Would anyone have any comments or advice ?
> > Thanks,
> > Jeff
> > idunno how or what you looked up specifically, but I see no trouble here:
>
> http://www.samsung.com/Products/Semiconductor/LowPowerSRAM/index.htm
>
You didn't look good enough. Go to that link and at the bottom of the
page under "Product Line-up"
click on any of the 5V density categories. Then click on the Production
Status of any part. They all
say EOL.
>
> I just don't know if these families will cause trouble interfacing
> with 9S12. Anybody know if 9S12X could use these without adding
> interface logic?
>

I was just planning on bit-banging with the parallel I/O ports. I don't
need a lot of speed
just a lot of storage space. I know that the multiplexed bus on the
9s12 is a nightmare
to use.

>
>

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

David Simpson wrote:
>
> Jeff McKnight wrote:
> > Hello All,
> > I need a lot ( ~2 Meg) of data storage and I was just planning
> > on bit-banging four 512k SRAMs with an HC12. It seems, however,
> > from my searching that Asynchronous SRAM is dying out. ST Micro
> > says they are discontinuing all of their SRAM products. On Toshiba's
> > Web site it says all of their SRAM products are end-of-life. Also
> > Samsung has all of their 5V SRAMs listed as end-of-life. Has anyone
> > else found this to be the case ? Is their another source that I'm
> missing ?
> >
> > I'm starting to think my best option may be to go to a higher-end micro
> > and use SDRAM. Would anyone have any comments or advice ?
> > Thanks,
> > Jeff
> >
> Hi Jeff,
>
> Have you considered using Serial Flash instead, especially if you are
> going to bit bash a parallel interface. This is what we now use for data
> storage:
> http://www.sst.com/products.xhtml/serial_flash/25/SST25VF016B
>
> Bigger / smaller versions available, all in an 8 pin SOIC. Interfaces to
> the 5V SPI with a few level translators, and no need for backup battery.
>

Flash memory doesn't have enough write/erase cycles. I will be writing
data hundreds
of times per second continuously. I did however, find out about "Pseudo
Static Ram (PSRAM)
also called "Cellular-RAM". This is high-density memory that uses a
DRAM cell but has the
refresh circuitry built-in. The interface works just like SRAM. These
are available from Micron,
Samsung, Toshiba, and ST Micro. And they are cheap. From my research it
does appear that
SRAM is a declining market due largely to the increasing popularity of
PSRAM.

> David
>
>



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

Jefferson Smith wrote:
>
> --- In 6...@yahoogroups.com , Jeff
> McKnight wrote:
> > and use SDRAM. Would anyone have any comments or advice ?
> > Thanks,
> > Jeff
> > idunno how or what you looked up specifically, but I see no trouble here:
>
> http://www.samsung.com/Products/Semiconductor/LowPowerSRAM/index.htm
> You didn't look good enough. Go to that link and at the bottom of the
page under "Product Line-up"
click on any of the 5V density categories. Then click on the Production
Status of any part. They all
say EOL.

>
> I just don't know if these families will cause trouble interfacing
> with 9S12. Anybody know if 9S12X could use these without adding
> interface logic?
>

I was just planning on bit-banging with the parallel I/O ports. I don't
need a lot of speed
just a lot of storage space. I know that the multiplexed bus on the
9s12 is a nightmare to use.

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

--- In 6...@yahoogroups.com, Jeff McKnight wrote:
> You didn't look good enough. Go to that link and at the bottom
> of the
> page under "Product Line-up"
> click on any of the 5V density categories. Then click on the
> Production
> Status of any part. They all
> say EOL.

When I say I found no problem, I do mean that I looked.
Sorry though, I can't find one now that is not EOL, so I don't know
why I saw a different status yesterday.

So it still seems there should be some serial (I would hope I2C) RAM
devices that should save you significant trouble. I think you've found
that they don't have to be called "SRAM" because they might reduce
size by including an internal refreshing system, or some new technology.

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )

Jeff McKnight wrote:
> refresh circuitry built-in. The interface works just like SRAM. These
> are available from Micron,
> Samsung, Toshiba, and ST Micro. And they are cheap. From my research it
> does appear that
> SRAM is a declining market due largely to the increasing popularity of
> PSRAM.

I agree that the volumes are declining; after all, the memory sizes
offered in slow async SRAM are relatively small, and aren't enough
for today's embedded software writers, who seem more likely to want
a "real OS" to run on. However, the market is by no means disappearing;
at this moment I'm using 5V slow async SRAM from Brilliance (found at
http://www.bsi.com.tw/ ) and I'm sure there are plenty of other
manufacturers who are willing to make commodity chips with a smaller
profit margin. Cypress still makes 5V SRAM too.

Sam



(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )