Search options (Page 35 of 137)

This could be a good idea. Suggestion of the rules:

+keep it on-topic and keep discussion at a minimum. Ready to do this almost on the spot,

Alright. It's all about reading the manuals and noticing little things. Those fuse bits are what's actually recommended by the build manual. But that's not what made me change it. The crucial setting is what the fue calculator describes as "Ext. Clock/RC Osc./Low-freq. Crystal: enable internal Capacitors (36 pF) Internal R/C Osc.: leave unchecked! External Crystal: enable full swing (neccessary for >8 MHz)" The important part is "enable full swing" which makes the oscillator circuit go between 0 V and 5 V instead of running on a lower voltage, presumably to save power. This reminded me of something from the FT232BM datasheet.

So without that fuse bit set, the clock line will not reach the switching threshold and the FTDI chip will not be properly clocked, and USB will not work.

So, now I want to know, is one of the Atmega chips actually broken?

Probably an avrdude quirk. Try reading the fuses individually with the following switches, rather than just looking at the summary.

-U lfuse:r:-:h -U hfuse:r:-:h -U efuse:r:-:h

This is normal. Burning the EE fuse value tells the chip to disable the internal RC oscillator and use an external crystal. The chip needs a clock signal to be programmed, so the chip won't work while in the AVR programmer, since it has no crystal or other clock source. I should have thought of this before recommending that fuse value, given that I saw your AVR programmer. (If you had programmed the flash memory and high fuse first, the chip would be usable now.)

The quick'n'dirty way to solve this would be to add a crystal between the same two pins as in the actual circuit. The value shouldn't be too critical for just programming the chip. Any crystal >=1 MHz that doesn't exceed the rating for the chip should work well enough for the purpose.

You MAY be able to program the chip adding the -B 1.0 switch to avrdude, but if it works it will be slow as a dog's butt.

The less quick'n'dirty way of solving this is to add some form of programming header to the board, so the AVR chip can be programmed in circuit. If you had sent it to me, I probably would have done this just for my own convenience.

However, with this in mind you should be able to plug the chip back in to the GB programmer and notice an improvement. There's no code on the chip, so it won't work as a flasher, but now that the crystal should be oscillating at 6 MHz, the FTDI chip should be identified since it should be able to communicate over USB.

If this thread wasn't related to music creation, I would consider editing the title. But now I won't.

Actually, the EMS cartridges, even the 64M one, support multiple ROMs, basically as many as the cartridge can fit. This is a lesser known functionality, I guess because LSDj doesn't play well with it. You can normally use this by just dragging multiple ROMs into the EMS software, but...
1) Adding LSDj typically makes the built-in EMS menu fail to work at all.
2) The built-in menu doesn't deal with multiple saves between the games. There are alternative menus that do, but they are not compatible with LSDj's file saving.

So, I've integrated an EMS menu into LittleFM. There's a download link andinstructions on how to use it in the link below. You have to manually produce a ROM file that you burn to the cartridge. However, there's still no save management for other ROMs, so you should only use saveless ROMs.

http://blog.gg8.se/wordpress/2013/03/04 … fects-you/

Since many EMS cartridges are buggy and get stuck on page 2, I suggest producing a ROM like this that you verify is working, and write it to both pages.

As a test, I've made a ROM which features LSD + LittleFM + a number of saveless noise ROMs. I've also added a function where pressing seö+start+B+A in any of the programs will return to the LittleFM menu.

Yes. External clock source is different from using an external crystal. External clock source means you're generating the clock somewhere else on the board and send it to the clock input of the Atmega. (Such as in your (jazz's) flasher and mine, where the clock is generated in the FTDI chip.) If you're using an external crystal connected between the X terminals, choose external crystal in the drop down and the appropriate frequency range.