Messages

I tried using another psu I had around. Same result, no video signal

Do you have another graphics card that you could try? Your symptoms sound vaguely like what happened in my early tests with the 7970 though that card is now working perfectly.

What do You think about this case?
http://www.codegenworld.com/showDetails.asp?max_id_search=20&min_id_search=&pro_id_search=203
Will the motherboard fit in this case if I remove the internal stuffs and mount the PSU somewhere on the front side?

The motherboard won't fit, it's quite a bit larger than the maximum size quoted in the linked advert.

Hi Raymond. Yes it's safe to have multiple Gpio declarations. You can have them anywhere in your code and the pin configuration will persist even after the Gpio object has gone out of scope.

Although PA3 is required for MII it should be free when using RMII so you don't have an obvious pin clash. The stack trace does look line a memory issue. Are you trying to process more data than you can fit in SRAM?

Despite my own advice to the contrary I've been buying too-cheap-to-be-true ICs from China again. Check out my blog entry to see how I got on with an investigation into whether I'd been sold counterfeits or not.

Hello,

I'm having really bad issues with a Z800 mobo. It's taken out of a working system so I'm sure the parts are ok.
Board revision is A02, it has 24Gb in 6x4gb modules. CPUs are X5550s. I've bought the adapter cable from the chinese guys
PSU is a 485W Enermax. I know it's low but I wanted to see it go into BIOS before investing in a new PSU.

My problem is that after connecting everything and starting the PSU, the board powers up(by itself, no pins or buttons), psu fans start spinning and it just hangs. No signal on video. Heatsinks, gpu, memory start to get warm but nothing else happens.

I've tried using only one cpu, one ram stick, with gpu, without gpu, nothing. I really don't know if it's the low power of the psu or it's the adapter cable or something else.

I suspect the power supply. The total wattage is far too low and how are the amp limits distributed across the rails? I reprinted HPs minimum limits for amps on each V12 line in my main article.

The PSU should not come on at all unless the ATX PS_ON_L signal is grounded and the front panel power switch normally does that. You say, "no pins or buttons". Does that include the front panel power switch?

I don't think you're going to get anywhere until you've got a PSU that's well within the minimum spec.

Hello there! Does anybody got Speedfan working with the Z800 Motherboard?

Yes I got speedfan working in so much as I was able to disconnect the CPU fans from automatic control and could ramp them up and down using the controls on the main screen. You have to go into the advanced tab and disconnect the fans from automatic sensor control. It was quite easy to guess the sensor names from the list. Apologies for the vague description but I'm away from my PC at the moment but can post replies here.

I'm going to prepare a release of the ATtiny85 source code for the long range IR emitter shortly. For now though, here's the compiled hex file ready for flashing to the ATtiny85 attached to this post.

Great news and sorry I couldn't offer any useful help. The SSD1963 is the most flexible panel driver I've seen and the settings for one are unlikely to work for another without modification.

I'm afraid I don't understand the question. All 16 lines are always used because it's a 16-bit bus between the MCU and the panel. What is 12-bit packed mode? If the panel is in 16-bit colour mode then the 5-6-5 pixel is transferred in one transaction. Higher colour depths require multiple transactions per pixel.

Pinout link.

If you still have no backlight then there's every possibility that the panel is working and you can't see it. Without the backlight the panel data is completely invisible even if it is actually there - you will see nothing at all. You must get the backlight working according to the schematic in your panel's datasheet.

Do you have a link to the panel's datasheet (not the SSD1963 controller)?

The calculations to derive the address/data setup timings are given in AN2790 but to be honest I usually just guess and then tweak the values up and down if I get it wrong. My logic analyser is invaluable when doing this.

Reading pixels from these types of controllers is possible but it's very much slower than writing. Firstly you'll need to look up the read-cycle timings in the controller's datasheet for the i80 bus. For example the popular ILI9325 has a minimum write cycle of 100ns and a minimum read cycle of 300ns.

Next you need to declare the LCD to have different FSMC timings in its constructor. For example you might change this:

Code Select Expand


      Fsmc8080LcdTiming fsmcTiming(0,2);

      // set up the FSMC with RS=A16 (PD11)

      _accessMode=new LcdAccessMode(fsmcTiming,16,pe[1]);


to this (fictitious timings):

Code Select Expand


      Fsmc8080LcdTiming fsmcReadTiming(0,4);
      Fsmc8080LcdTiming fsmcWriteTiming(0,2);

      // set up the FSMC with RS=A16 (PD11)

      _accessMode=new LcdAccessMode(fsmcReadTiming,fsmcWriteTiming,16,pe[1]);


You can then use any of the 'move' methods in the LCD's implementation class to set the display window and then use the readData method to sequentially read back pixels from the window.

Note that some controllers waste even more cycles by requiring a dummy read before you get back the real data - check the datasheet for details. If you get the timing wrong then the data will appear corrupted.

Since this is a raw data read then if the LCD is in 16-bit mode you'll get back one complete pixel per read. If the panel is in 18 or 24 bit mode then more reads will be required to get back a complete pixel. The datasheet for the controller will tell you what the pixel packing format is.

Thanks very much Kyle, I appreciate that. It's now been integrated into the library and released in version 4.0.2.

I've just released version 4.0.2 of stm32plus. This release collects together a number of bug fixes and small features that have been made since 4.0.0.

There was, briefly, a 4.0.1 release but since I forgot to update the build version number in stm32plus.h it was quickly abandoned so 4.0.2 is the latest release as of today.

The ZET6 should be fine - it's just like the VET6 but with more features due to the 144 pin package. If your screen remains black then there's something wrong with the backlight. Please check that your board supports the backlight being driven by the PWM signal on PD13 and if it doesn't then don't use it.

Hi Mike,

You've done everything correctly as far as generating the source and header files go. It looks like the .cpp file is either not being compiled or it's not being linked. I don't see it in your linker command line which implies that you've compiled it into the library. Is that the case and can you check that?