Logo107.22.127.78 
  Home  News  Recent  Forums  Search  Contact
  Menu
 Username

 Password


   Register here

 Main menu
   View images
   BBCode test
 
 Content
   Statement of intent
   Terms Of Service
   IRC Channel
   List Content

 In cooperation with
  OS4Depot.net
  OpenAmiga.org
  OS4Welt

 Links
  AmigaOS4
  IntuitionBase
  UtilityBase
  Amiga Flame
  Amiga Spirit
  AmiKit
  Aminet
  AmiBay
  AmigaBounty
  AmigaWorld
  Exec
  Amiga.cz
  View comments
Title  
  Forums
    Software
      AmigaOS 4  
Trevsii3114ide.device.kmod NVRAM Options20110220 22:39
From another thread:

Just out of curiosity, though, what are the possible values for sii3114ide_verbose, and where does it send its output? I assumed a value of 1 and output via kprintf. Nothing.
Navigate: 1-15 
elwoodRe: sii3114ide.device.kmod NVRAM Options20110220 23:18  #2287
@Trev

Hum I never seen a Uboot variable called sii*_verbose and also never needed one, even during the beta process. :-/
TrevRe: sii3114ide.device.kmod NVRAM Options20110220 23:31  #2288
@elwood

These are the variables the driver appears to reference:

sii3114ide_verbose
sii3114ide_timeout
sii3114ide_conf
sii3114ide_xfer
sii3114ide_irq

Of those, I've found sii3114ide_xfer to be the only necessary option. There are definitely verbose messages in the driver, and it would be nice to see them while configuring the system for benchmarking. The s4sii_* variables are referenced by u-boot and not the driver, so I'm not really interested in those. (Although, there is an apparent bug in board/ACube/common/sam_ide.c indirectly related to *_maxbus. The device reset loop ends prematurely on timeout. E.g. If device 2 does not respond or does not exist, the loop breaks and device 3 is not reset. The default environment value of s4sii_maxbus=1 on the Sam440ep-flex just forces what is typically the first hard disk--if you followed the hardware install guide--to be reset.)
tonywRe: sii3114ide.device.kmod NVRAM Options20110221 12:44  #2299
@Trev

Never heard of those other vars. Maybe they are private, for the use of the developer only.
ZeroGRe: sii3114ide.device.kmod NVRAM Options20110221 21:33  #2325
@Trev

Maybe it is a good idea to read the file SYS:Documentation/IDE/sii3114ide_dev.doc ?

Have you checked the debugbuffer with C:DumpDebugBuffer?
TrevRe: sii3114ide.device.kmod NVRAM Options20110221 22:00  #2330
@ZeroG

:-) Thanks for that. I've redirected debug output to the serial port. Now I just need to figure out why I don't get serial output after the OS starts. (See my other thread.) Edit: Interesting. Everything works fine until the first time I try to use the SER: device. After that, serial output is garbage.
elwoodRe: sii3114ide.device.kmod NVRAM Options20110221 22:11  #2332
@Trev

Serial output works only using the debug version of "kernel". Available only to betatesters.

BTw, what do you want to achieve in the first place?
hansRe: sii3114ide.device.kmod NVRAM Options20110221 22:12  #2333
@Trev

If you want debug output to be directed to serial right from the moment that the OS starts, add "serial" (minus the quotes) to the boot arguments in UBoot. You can change from outputting debug to memory and serial at any time with the kdebug command (e.g., kdebug "console serial").

Trying to use SER: when it is directed to the same serial port as the debug output is just asking for trouble.

Hans
TrevRe: sii3114ide.device.kmod NVRAM Options20110221 22:29  #2336
@elwood

It works fine after adding serial to os4_commandline as Hans (and the documentation) suggested, e.g.:

os4_commandline=debuglevel=10 serial

@hans


Trying to use SER: when it is directed to the same serial port as the debug output is just asking for trouble.


That makes sense; however, neither SER: nor AUX: work for me, regardless. All I ever see is garbage. Something is broken somewhere. Output from u-boot and the kernel is fine, so it's something between Port-Handler and ppc440ep_serial.device? Does the kernel bypass the device driver?
hansRe: sii3114ide.device.kmod NVRAM Options20110221 22:38  #2337
@Trev

That makes sense; however, neither SER: nor AUX: work for me, regardless. All I ever see is garbage. Something is broken somewhere. Output from u-boot and the kernel is fine, so it's something between Port-Handler and ppc440ep_serial.device? Does the kernel bypass the device driver?


I have absolutely no idea how it works internally. You could try setting SER: to the same settings as the debug output (i.e., whatever baud rate, stop bits, etc., you are using for debug).

Hans
TrevRe: sii3114ide.device.kmod NVRAM Options20110221 22:44  #2338
@hans

I've done that. I've even gone through various settings in the terminal (PuTTY) to see if OS4 is ignoring my settings and using something else. I haven't gone through every permutation, though. That's a bit tedious. :-) I guess I could peek at the hardware regs.
tonywRe: sii3114ide.device.kmod NVRAM Options20110221 23:05  #2340
@Trev

Are you trying to use AUX: with a remote console? If so, the serial settings are tooltypes in the AUX driver in Devs/DOSDrivers, not in SER.

If you still get garbage, try altering the speed settings of the remote machine until you find the right speed. Character length isn't important if you only send one or two chars at a time.

[edit]
Come to think of it, I seem to remember that using SER: changes the speed of the port from the default U-Boot "baudrate" to the speed setting of "SER:", but leaves it set to that, so all subsequent debug output is at SER: speed.
[/edit]
TrevRe: sii3114ide.device.kmod NVRAM Options20110221 23:16  #2341
@tonyw

I've tried both SER: and AUX:, adhering to the settings defined by the mount file (or used in my descriptor).

I did say I'd fiddled with the terminal settings. :-) I think ppc440ep_serial.device is doing something wonky to the on-chip serial bits.
TrevRe: sii3114ide.device.kmod NVRAM Options20110221 23:38  #2342
@Trev

I have a Sam440ep-flex 733 MHz, which has a processor local bus clock of 146 MHz. Perhaps ppc440ep_serial.device doesn't know how to set up UART regs for that clock speed. It might be assuming a specific clock or incorrectly detecting the current clock.
TrevRe: sii3114ide.device.kmod NVRAM Options20110222 04:17  #2349
@Trev

Moving the serial port discussion to the ppc440ep_serial.device thread....
AlexCRe: sii3114ide.device.kmod NVRAM Options20110223 13:30  #2395
@Trev

According to the documentation, setting the 3114ide_verbose uboot var to *any* value will make the ide driver print verbose output.

Don't expect too much though, here the only output I get is when booting/rebooting, it gives a detailed log of the drive scanning/init procedure and that's it. After that (at least as long as there's no error) it doesn't print anything.
Navigate: 1-15 
Home
Snack! forum website engine, Created in 2008 by Björn Hagström