0 Members and 1 Guest are viewing this topic.
Boot Loader Stage 1 (126.96.36.199)Build: 2015/7/20, 14:47:25Copyright (c) 2006-2015 Texas Instruments IncorporatedUsing production keysLast boot progress: 0Available system memory: 28072Checking for NAND: NAND Flash ID: Generic 1 GBit (0xA1)SDRAM size: 64 MBWakeup Event: ON.SDRAM memory test: PassClearing SDRAM...Done.Clocks: CPU = 156MHz AHB = 78MHz APB = 39MHz Clearing SDRAM...Done.Boot option: NormalLoading from BOOT2 partition...100%BOOT1: loading complete (168 ticks), launching <BOOT2> image.
New screen, with a new buffer geometry.The new buffer is 90° rotated making it 240x320 instead of 320x240, and mirrored.To give you an idea, if you run on a CR4 some code which does not support the new screen it looks like this :Therefore, TI just completely broke the compatibility with all existing Ndless programs - diabolically brilliant. So either we will have to rebuild all existing Ndless programs, most authors having moved on, and for some of which the source code is not available...Either a future CR4 Ndless could have some kind of a compatibility layer...But even in the latter case, it would imply writing the screen buffer two times (normal writing of the original program + fix writing), and so it would have a high performance cost for programs constantly refreshing the screen (nDoom, nQuake, emulators...) - we can expect a halving of the fps if there is no CR4 update.
Interesting, especially the screen. Does it mean that the calc uses the same screen as the TI-84 Plus C Silver Edition, but larger? On the CSE, you can notice vertical scanlines if you stare at the screen, which are normally horizontal on other calcs.
This sucks for all Ndless programs, though. I hope that TI did that mainly to improve performances, to save on production costs or to replace a no-longer-produced part, and not as another attempt to block Ndless programs. A compatibility layer will definitively have to be written, even if it means that all programs run much slower (in which case, people might as well switch to Lua or HP PPL). Casio did that with the SH4 calcs, which broke compatibility with many ASM programs.
Clocks: CPU = 156MHz AHB = 78MHz APB = 39MHz
Oh goodness. That's horrible. Is there any other reason they might have made the switch, or is it solely to screw Ndless?
And wow, if even the OS uses a compatibility layer, then does that mean that the new calc will actually run slower despite the overclocking?
What was the default clock speeds in hardware J? I forgot. Wasn't it 132 or 120 MHz CPU speed?
Quote from: DJ Omnimaga on February 24, 2016, 09:35:21 pmWhat was the default clock speeds in hardware J? I forgot. Wasn't it 132 or 120 MHz CPU speed? 132MHz for all CX up to hardware V.120MHz was on older TouchPad/ClickPad.
Isn't the first of april still like a month away?
Quote from: critor on February 24, 2016, 09:47:40 pmQuote from: DJ Omnimaga on February 24, 2016, 09:35:21 pmWhat was the default clock speeds in hardware J? I forgot. Wasn't it 132 or 120 MHz CPU speed? 132MHz for all CX up to hardware V.120MHz was on older TouchPad/ClickPad.I thought that ClickPad calcs were 90 MHz? Or was it just for OS 1.1 through 1.7?
Remember that "CR4" stands for "Cost Reduction" (phase 4).
50% speed loss for some games, only if they don't get updated with CR4 screen support.
Page created in 0.153 seconds with 55 queries.