@Mrodfr & ChrisH

Thanks for the replies - I fixed it almost immediately after posting by selecting the 'auto detect monitor' option and rebooting. It dropped me straight into 1680x1050!

Just installed the 4.1 SDK and tried out writing hello, world, now onto the examples...

@apache64

Posting this using OWB on AmigaOS 4.1 Update 2!!!!

Ah, it's nice to be back...

Had to install the Ethernet driver myself (quite proud I managed to do it correctly first time) but apart from that it's looking good.

Does OS4.1 support monitors with 1680x1050 resolution? I'm currently running at 1280x720 which was the highest I could see in ScreenMode...

@Rigo

Thanks - will do. All these new libraries and C++ interfaces to get used to!

@kas1e

Thanks for the comments. I've already found a PDF of the IBM E Book Specification (which appears to cover the PPC 440EP found on the SAM440EP motherboard) so that's a good start. From a quick flick through it looks quite similar to the MC680x0 series (most silicon does really at the machine code level).

Once I've got hold of my 440ep I'll take at look at the latest SDK and the tools you mention - hopefully that will give me a bit more to go on.

I think improving/finishing gdb might be a little out of my capabilities but I thought I might start with a process profiler (I know there are plenty already) as this will give me a chance to get used to exec and intuition again (most of my previous Amiga coding was direct to the hardware) and I can build from there.

I know this will sound stupid, but I'm guessing a useful debugger would be something which will allow you to launch your application and then step through the code / run to a specific point and also aim to catch exceptions?

Sounds daft I know but, as I say, my previous work had custom debuggers built-in but they were very rudimentary as there was no intuition running!

Hi

I'm not new to the Amiga but I'm completely new to OS4 and the AmigaOne. Back in the day I used to write debugging tools and game disk operating systems for the A500 and A1200. Of course, this was all in 680x0...

In my intro post there was a comment made that OS4 is short of debugging tools - something I'd be really interested in working on, but I have some questions:

1. Is this true or are there good tools available?
2. Is it a case of improving existing tools - eg gdb - or is there a requirement for something amiga specific?
3. Before OS4 things were simple: it was just the 680x0 range to contend with - are things more complicated now or is any PPC processor much like the next one?
4. How easy is it to install low level processor trap handlers now? In my day it was all about patching the various vectors and resetting the VBR...

As you can see, I'm a bit new to the current platform so please go easy with your comments!

Thanks guys!

I'd love to work on some debugging tools for OS4 - presumably I'll need to gen up on the PPC architecture though!

So, some are recommending gcc (which I know from BeOS) but is VBCC better for Amiga dev work?

Just registered so I thought I'd say hello.

My SAM440ep system is currently on it's way to me and I'm looking forward to getting back into Amiga coding. I did a fair bit in the early 90's (mainly debugging tools, game disk operating systems and such) and wrote a few coding articles for LSD.

All of this was in 680x0 so the move to C is going to be interesting! From what I've read on here so far it looks like C (rather than C++) using VBCC is probably the way to go.

Cheers

Chris